csswizardry/inuit.css — pull request #28 by OliverJAsh (2012-10-05 10:57:33+00:00)
Title: Encapsulate ready for packaging

I took inspiration from [Nicholas Gallagher’s SUIT utilities](https://github.com/necolas/suit-utils) which is also available for distribution on Bower. The way Nicolas has packaged this up essentially means the developer must install the package from Bower, and then manually reference the package in their own project files.

If you have a play with Bower, you will notice that packages are downloaded to a folder called components. This lives inside of the developer’s project. The developer is not going to want to author their CSS from inside of the components folder, so providing a `your-project.scss` wouldn’t really be right. Rather, as in SUIT utilities, the developer has to manually reference inuit.css in their own project files.

To test this workflow, create a new project, and run the following command:

`bower install git://github.com/OliverJAsh/inuit.css.git`

Create a file in the project at `css/your-project.scss` with the following contents:

``` scss
@charset "UTF-8";
/*------------------------------------*\
YOUR-PROJECT.SCSS
\*------------------------------------*/
/**
*
* cd into the css directory and run this command, or setup a Compass project
* of your own:
* sass --watch your-project.scss:your-project.min.css --style compressed
*
* Here we set up some custom variables, include the inuit.css framework, then
* add our project-specific components afterwards.
*
* For a reference of available variables, please see _vars.scss.
*/
$h1-size: 40;

// She’s all yours, cap’n... Begin importing your stuff here.
@import "../components/inuit.css/inuit"

```

Notice how the developer can easily change variables in their own project files. If inuit.css is updated through Bower, then no changes to these variables will be lost.

Pretty sure all of this is obvious anyway, but you asked me to be thorough ;)