{"_id":"grunt-sassquatch","_rev":"35-6e120f5b5b934a709c8ffd7be4a74808","name":"grunt-sassquatch","description":"SASSquatch, the modular SASS framework.","dist-tags":{"latest":"0.2.9"},"versions":{"0.1.0":{"name":"grunt-sassquatch","description":"SASSquatch, the modular SASS framework.","version":"0.1.0","homepage":"https://github.com/thealscott/sassquatch","author":{"name":"Al Scott","email":"thealscott@gmail.com"},"repository":{"type":"git","url":"git://github.com/thealscott/sassquatch.git"},"bugs":{"url":"https://github.com/thealscott/sassquatch/issues"},"licenses":[{"type":"MIT","url":"https://github.com/thealscott/sassquatch/blob/master/LICENSE-MIT"}],"main":"Gruntfile.js","engines":{"node":">= 0.8.0"},"scripts":{"test":"grunt test"},"devDependencies":{"grunt-contrib-jshint":"~0.6.0","grunt-contrib-clean":"~0.4.0","grunt-contrib-nodeunit":"~0.2.0","grunt":"~0.4.1"},"peerDependencies":{"grunt":"~0.4.1"},"keywords":["gruntplugin"],"readme":"# sassquatch-test\n\n> The best Grunt plugin ever.\n\n## Getting Started\nThis plugin requires Grunt `~0.4.1`\n\nIf you haven't used [Grunt](http://gruntjs.com/) before, be sure to check out the [Getting Started](http://gruntjs.com/getting-started) guide, as it explains how to create a [Gruntfile](http://gruntjs.com/sample-gruntfile) as well as install and use Grunt plugins. Once you're familiar with that process, you may install this plugin with this command:\n\n```shell\nnpm install sassquatch-test --save-dev\n```\n\nOnce the plugin has been installed, it may be enabled inside your Gruntfile with this line of JavaScript:\n\n```js\ngrunt.loadNpmTasks('sassquatch-test');\n```\n\n## The \"sassquatch_test\" task\n\n### Overview\nIn your project's Gruntfile, add a section named `sassquatch_test` to the data object passed into `grunt.initConfig()`.\n\n```js\ngrunt.initConfig({\n  sassquatch_test: {\n    options: {\n      // Task-specific options go here.\n    },\n    your_target: {\n      // Target-specific file lists and/or options go here.\n    },\n  },\n})\n```\n\n### Options\n\n#### options.separator\nType: `String`\nDefault value: `',  '`\n\nA string value that is used to do something with whatever.\n\n#### options.punctuation\nType: `String`\nDefault value: `'.'`\n\nA string value that is used to do something else with whatever else.\n\n### Usage Examples\n\n#### Default Options\nIn this example, the default options are used to do something with whatever. So if the `testing` file has the content `Testing` and the `123` file had the content `1 2 3`, the generated result would be `Testing, 1 2 3.`\n\n```js\ngrunt.initConfig({\n  sassquatch_test: {\n    options: {},\n    files: {\n      'dest/default_options': ['src/testing', 'src/123'],\n    },\n  },\n})\n```\n\n#### Custom Options\nIn this example, custom options are used to do something else with whatever else. So if the `testing` file has the content `Testing` and the `123` file had the content `1 2 3`, the generated result in this case would be `Testing: 1 2 3 !!!`\n\n```js\ngrunt.initConfig({\n  sassquatch_test: {\n    options: {\n      separator: ': ',\n      punctuation: ' !!!',\n    },\n    files: {\n      'dest/default_options': ['src/testing', 'src/123'],\n    },\n  },\n})\n```\n\n## Contributing\nIn lieu of a formal styleguide, take care to maintain the existing coding style. Add unit tests for any new or changed functionality. Lint and test your code using [Grunt](http://gruntjs.com/).\n\n## Release History\n_(Nothing yet)_\n","readmeFilename":"README.md","_id":"grunt-sassquatch@0.1.0","dist":{"shasum":"cbac444dddedc58825e1f7a6d0cf7513f579eb1b","tarball":"https://registry.npmjs.org/grunt-sassquatch/-/grunt-sassquatch-0.1.0.tgz","integrity":"sha512-Ca0Enqu/5IFlXMx4jwJXDZyHu5hGBsDz5muBMJ427S+0owRHYx8Ayi8MRxmIcP3MkEjrowJGewAuPiQz/KMEKw==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIDCgGIWMh0KBNI0APdPn9RZlyQk5poNeV4M1PZNZ9RpUAiEAnzrMHvt/c/JkqoWGC4zWyNn2pc9FKs7wkRFoWwRXNVk="}]},"_from":".","_npmVersion":"1.3.5","_npmUser":{"name":"thealscott","email":"thealscott@gmail.com"},"maintainers":[{"name":"thealscott","email":"thealscott@gmail.com"}]},"0.1.2":{"name":"grunt-sassquatch","description":"SASSquatch, the modular SASS framework.","version":"0.1.2","homepage":"https://github.com/thealscott/sassquatch","author":{"name":"Al Scott","email":"thealscott@gmail.com"},"repository":{"type":"git","url":"git://github.com/thealscott/sassquatch.git"},"bugs":{"url":"https://github.com/thealscott/sassquatch/issues"},"licenses":[{"type":"MIT","url":"https://github.com/thealscott/sassquatch/blob/master/LICENSE-MIT"}],"main":"Gruntfile.js","engines":{"node":">= 0.8.0"},"scripts":{"test":"grunt test"},"devDependencies":{"grunt-contrib-jshint":"~0.6.0","grunt-contrib-clean":"~0.4.0","grunt-contrib-nodeunit":"~0.2.0","grunt":"~0.4.1"},"peerDependencies":{"grunt":"~0.4.1"},"keywords":["gruntplugin"],"readme":"# (grunt) SASSquatch\n\nExperiments with SASS framework, in the form of a grunt plugin.\n","readmeFilename":"README.md","_id":"grunt-sassquatch@0.1.2","dist":{"shasum":"fc5c427729db1382351bea3add334c8cca544163","tarball":"https://registry.npmjs.org/grunt-sassquatch/-/grunt-sassquatch-0.1.2.tgz","integrity":"sha512-Q3NgXPHdTUWv6JusTA8QzP3ghWJUn6kRWThgssxI60lQsE8XyeuLeoI4RFElCHAur15yD5zmwNe5lnyzeODXLg==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCID+8lGAIibkHXhe4nbb2Gm4/j81zhrE2a/iTkFMa7jztAiEAnkVU/ZVYHVqNYjzBbftF/q2K2F0BDfnQMfAh+fKVQkM="}]},"_from":".","_npmVersion":"1.3.5","_npmUser":{"name":"thealscott","email":"thealscott@gmail.com"},"maintainers":[{"name":"thealscott","email":"thealscott@gmail.com"}]},"0.1.3":{"name":"grunt-sassquatch","description":"SASSquatch, the modular SASS framework.","version":"0.1.3","homepage":"https://github.com/thealscott/sassquatch","author":{"name":"Al Scott","email":"thealscott@gmail.com"},"repository":{"type":"git","url":"git://github.com/thealscott/sassquatch.git"},"bugs":{"url":"https://github.com/thealscott/sassquatch/issues"},"licenses":[{"type":"MIT","url":"https://github.com/thealscott/sassquatch/blob/master/LICENSE-MIT"}],"main":"Gruntfile.js","engines":{"node":">= 0.8.0"},"scripts":{"test":"grunt test"},"devDependencies":{"grunt-contrib-jshint":"~0.6.0","grunt-contrib-clean":"~0.4.0","grunt-contrib-nodeunit":"~0.2.0","grunt":"~0.4.1"},"peerDependencies":{"grunt":"~0.4.1"},"keywords":["gruntplugin"],"readme":"# (grunt) SASSquatch\n\nExperiments with SASS framework, in the form of a grunt plugin.\n","readmeFilename":"README.md","_id":"grunt-sassquatch@0.1.3","dist":{"shasum":"a18ac6a35308e9d1bd9f4ee1da9565658b35233a","tarball":"https://registry.npmjs.org/grunt-sassquatch/-/grunt-sassquatch-0.1.3.tgz","integrity":"sha512-C3GnchPhI1zZHAKzhfIiEvZ8qHXUb0KFsKNyWWs3hwjaa4zUBbgAIxI8k/ERTvBozyNZVovpZh7gxiVko1c2pQ==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEQCIDAY7D6LNjNnKMfRTLU5yZXXxXKbw4MHBR1XTQqJRvYYAiAPigXsumbbHlgwmvl5XkkDk4B06y2X/N0j+woNDK29Cg=="}]},"_from":".","_npmVersion":"1.3.5","_npmUser":{"name":"thealscott","email":"thealscott@gmail.com"},"maintainers":[{"name":"thealscott","email":"thealscott@gmail.com"}]},"0.1.4":{"name":"grunt-sassquatch","description":"SASSquatch, the modular SASS framework.","version":"0.1.4","homepage":"https://github.com/thealscott/sassquatch","author":{"name":"Al Scott","email":"thealscott@gmail.com"},"repository":{"type":"git","url":"git://github.com/thealscott/sassquatch.git"},"bugs":{"url":"https://github.com/thealscott/sassquatch/issues"},"licenses":[{"type":"MIT","url":"https://github.com/thealscott/sassquatch/blob/master/LICENSE-MIT"}],"main":"Gruntfile.js","engines":{"node":">= 0.8.0"},"scripts":{"test":"grunt test"},"devDependencies":{"grunt-contrib-jshint":"~0.6.0","grunt-contrib-clean":"~0.4.0","grunt-contrib-nodeunit":"~0.2.0","grunt":"~0.4.1"},"peerDependencies":{"grunt":"~0.4.1"},"keywords":["gruntplugin"],"readme":"# (grunt) SASSquatch\n\nExperiments with SASS framework, in the form of a grunt plugin.\n","readmeFilename":"README.md","_id":"grunt-sassquatch@0.1.4","dist":{"shasum":"cc827aac69b733b9c19b12d365764993009bff41","tarball":"https://registry.npmjs.org/grunt-sassquatch/-/grunt-sassquatch-0.1.4.tgz","integrity":"sha512-xjA1p5l1sc0FALmOfYMLGaCqC6vetBI2qbEEPuzusno7m/nJA8dSTlTM4PTv6Z4mzT5c/vpA9N4nhgQt30h2EA==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEYCIQDB9OYQSBI56zmKnECtOI8MyxDliZ1i8oiC7i+grRpDAgIhAIPwqVQGp5ItY6/QHfjPE3ht/FMHCDCH8wWqCsAsPqva"}]},"_from":".","_npmVersion":"1.3.5","_npmUser":{"name":"thealscott","email":"thealscott@gmail.com"},"maintainers":[{"name":"thealscott","email":"thealscott@gmail.com"}]},"0.1.5":{"name":"grunt-sassquatch","description":"SASSquatch, the modular SASS framework.","version":"0.1.5","homepage":"https://github.com/thealscott/sassquatch","author":{"name":"Al Scott","email":"thealscott@gmail.com"},"repository":{"type":"git","url":"git://github.com/thealscott/sassquatch.git"},"bugs":{"url":"https://github.com/thealscott/sassquatch/issues"},"licenses":[{"type":"MIT","url":"https://github.com/thealscott/sassquatch/blob/master/LICENSE-MIT"}],"main":"Gruntfile.js","engines":{"node":">= 0.8.0"},"scripts":{"test":"grunt test"},"devDependencies":{"grunt-contrib-jshint":"~0.6.0","grunt-contrib-clean":"~0.4.0","grunt-contrib-nodeunit":"~0.2.0","grunt":"~0.4.1"},"peerDependencies":{"grunt":"~0.4.1"},"keywords":["gruntplugin"],"readme":"# (grunt) SASSquatch\n\nExperiments with SASS framework, in the form of a grunt plugin.\n","readmeFilename":"README.md","_id":"grunt-sassquatch@0.1.5","dist":{"shasum":"a18113547785115a0f9c5d9e64d3d98c22cc82ed","tarball":"https://registry.npmjs.org/grunt-sassquatch/-/grunt-sassquatch-0.1.5.tgz","integrity":"sha512-d8w4BhB/2Ie3mGkSkczXIcKSt9AGYPm82Tg5LawnsZAsXW8+396vaZQsX4U1PotseAlHDxn7eT46sfxo/VUOqQ==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEYCIQCiv10snzTbrRQtOtGpR7aVcTQuHxMJ0/pmkAEu1WrK0wIhANiYmbSq9uDBCc+cXVVPQjqiQjw/VrrBE7cFHHX6B/oy"}]},"_from":".","_npmVersion":"1.3.5","_npmUser":{"name":"thealscott","email":"thealscott@gmail.com"},"maintainers":[{"name":"thealscott","email":"thealscott@gmail.com"}]},"0.1.6":{"name":"grunt-sassquatch","description":"SASSquatch, the modular SASS framework.","version":"0.1.6","homepage":"https://github.com/thealscott/sassquatch","author":{"name":"Al Scott","email":"thealscott@gmail.com"},"repository":{"type":"git","url":"git://github.com/thealscott/sassquatch.git"},"bugs":{"url":"https://github.com/thealscott/sassquatch/issues"},"licenses":[{"type":"MIT","url":"https://github.com/thealscott/sassquatch/blob/master/LICENSE-MIT"}],"main":"Gruntfile.js","engines":{"node":">= 0.8.0"},"scripts":{"test":"grunt test"},"devDependencies":{"grunt-contrib-jshint":"~0.6.0","grunt-contrib-clean":"~0.4.0","grunt-contrib-nodeunit":"~0.2.0","grunt":"~0.4.1"},"peerDependencies":{"grunt":"~0.4.1"},"keywords":["gruntplugin"],"readme":"# (grunt) SASSquatch\n\nExperiments with SASS framework, in the form of a grunt plugin.\n","readmeFilename":"README.md","_id":"grunt-sassquatch@0.1.6","dist":{"shasum":"f76ec908ce8304a5b08c4c42eb02e5e8d9fc589c","tarball":"https://registry.npmjs.org/grunt-sassquatch/-/grunt-sassquatch-0.1.6.tgz","integrity":"sha512-9UYJ9xyQkk7YFwYEWMQuJozFSlKerDt6r4tj55sZhBkk6qSlpPAJ54KIUYIHxqK9kJqzacNZSTLLFHvrmXDf/Q==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEYCIQD/mCoWjwooxM6clo/ZoMub8EksGgn/iWLtfMD+OazOUQIhALDy5ppNLLbRizmSsrSVYzde9EnGpi5w2M/Mtb8apUqa"}]},"_from":".","_npmVersion":"1.3.5","_npmUser":{"name":"thealscott","email":"thealscott@gmail.com"},"maintainers":[{"name":"thealscott","email":"thealscott@gmail.com"}]},"0.2.0":{"name":"grunt-sassquatch","description":"SASSquatch, the modular SASS framework.","version":"0.2.0","homepage":"https://github.com/thealscott/sassquatch","author":{"name":"Al Scott","email":"thealscott@gmail.com"},"repository":{"type":"git","url":"git://github.com/thealscott/sassquatch.git"},"bugs":{"url":"https://github.com/thealscott/sassquatch/issues"},"licenses":[{"type":"MIT","url":"https://github.com/thealscott/sassquatch/blob/master/LICENSE-MIT"}],"main":"Gruntfile.js","engines":{"node":">= 0.8.0"},"scripts":{"test":"grunt test"},"devDependencies":{"grunt-contrib-jshint":"~0.6.0","grunt-contrib-clean":"~0.4.0","grunt-contrib-nodeunit":"~0.2.0","grunt":"~0.4.1"},"peerDependencies":{"grunt":"~0.4.1"},"keywords":["gruntplugin"],"readme":"# (grunt) SASSquatch\r\n\r\nExperiments with SASS framework, in the form of a grunt plugin.\r\n","readmeFilename":"README.md","_id":"grunt-sassquatch@0.2.0","dist":{"shasum":"fbfd492b39d9f311ed8f5afcb0c63ec0f51604d5","tarball":"https://registry.npmjs.org/grunt-sassquatch/-/grunt-sassquatch-0.2.0.tgz","integrity":"sha512-9NzLvIfEc1p17eI4AgWhUJAtVt2adn2P1sDqHwSjXXQD0Qm4niheSVN1Nnpj8ZK9D/+yeWHGL/HdlNtu6q9Gww==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIQCYcU7nmEGJrCLzmahAUH4/4+smXE8HBf5wcr/8MB8P0wIgWaSt9uRUhC8QBp7nxzeLsi17SU12TFK77kacwTYjS3M="}]},"_from":".","_npmVersion":"1.3.8","_npmUser":{"name":"thealscott","email":"thealscott@gmail.com"},"maintainers":[{"name":"thealscott","email":"thealscott@gmail.com"}]},"0.2.1":{"name":"grunt-sassquatch","description":"SASSquatch, the modular SASS framework.","version":"0.2.1","homepage":"https://github.com/thealscott/sassquatch","author":{"name":"Al Scott","email":"thealscott@gmail.com"},"repository":{"type":"git","url":"git://github.com/thealscott/sassquatch.git"},"bugs":{"url":"https://github.com/thealscott/sassquatch/issues"},"licenses":[{"type":"MIT","url":"https://github.com/thealscott/sassquatch/blob/master/LICENSE-MIT"}],"main":"Gruntfile.js","engines":{"node":">= 0.8.0"},"scripts":{"test":"grunt test"},"devDependencies":{"grunt-contrib-jshint":"~0.6.0","grunt-contrib-clean":"~0.4.0","grunt-contrib-nodeunit":"~0.2.0","grunt":"~0.4.1"},"peerDependencies":{"grunt":"~0.4.1"},"keywords":["gruntplugin"],"readme":"# (grunt) SASSquatch\r\n\r\nSASSquatch is a SASS framework (in as much as such a thing is possible), built on top of Compass.\r\n\r\nIt splits your SASS code up into a logical groupings, based on the premise of using common modules and page specific layouts/overrides. \r\n\r\nIt encourages the use of placeholders and extending base classes, and tries to keep code as modular and reusable as possible while avoiding the pitfalls of overly presentational markup. \r\n\r\nIt also aims to give you the tools you need to define and work with responsive design. The structure has been largely driven by the desire to have common placeholder classes that can be extended from within media query blocks.\r\n\r\nIt can be used Vanilla, but this requires a lot of manual management of adding files and line to import configs, so I recommend using the Grunt plugin.\r\n\r\nBoth the framework and the Grunt plugin are still in the very early stages, so there is a lot that will probably change, both in terms of the framework approach, and in terms of the functionality of the plugin.\r\n\r\n## Framework guide \r\n\r\n*MORE COMING SOON*\r\n\r\nI will write more on the structure and thinking behind the actual framework, as well as some additional usage documentation in the near future, but for now I have outline some top level information and guidelines below. \r\n\r\n### Breakpoints\r\nBecause of SASS's limitiations regarding extending classes across media blocks, in order to have one common source for extensible classes it is neccessary to have each media query as a separate compiled file. Each breakpoint generates a separate SASS file that will compile to separate CSS files. These should all be included in your HTML.\r\n\r\n*NOTE: I would rather be able to compile everything into a single CSS file, but at present some quirks of SASS seem to preclude that possibilty so long as you want to make use of extensible classes declared outside the media block. I had originally hoped to avoid this by redeclaring those placeholders within each media block by calling the mixin again within the block, but SASS seems to ignore these redeclarations when you try and compile everything together, and so the first declaration still triggers the extend error on compile*\r\n\r\n### Modules\r\nModules are where modular stylesets can be kept. These are styles that will be reused across the design, things like buttons, typography rules and so forth. Ideally you define placeholder classes here, that can be \"instantiated\" by extending them in your main/page styles, attached to semantic classes.  \r\n\r\n### Pages\r\nPage/pagetype specific markup hooks and styling should happen here. This requires the use of page type hooks (I suggest on the body element) in order to \"namespace\" your styles for a specific page or type of page. I find this approach useful, even if you are working on a very uniform page design, but obviously it is most useful when designs vary between pages.\r\n\r\n### Config\r\nGenerally you will be using scoped variables inside all the pages/modules, but if you need universal config variables, here is where to put them. In addition, the system config (import lists) will be in this folder too. As an example of a config, I use a color map where I can assign more memorable names for commonly used colors in the theme, without assigning them semantic var names. \r\n\r\n### Helpers\r\nIf you have general utility mixins or functions over and above compass, this is the place for them to live.\r\n\r\n### The Constructor\r\nThe constructor currently lives in the helpers folder (though I might move it, as it is special) and it serves a role similar to what its name implies. Each breakpoint stylesheet starts by including the construtor. In the constructor we should define any and all modules and helpers that you want to be universally applied/availble. If you don't include them in the constructor, you need to include them manually either in your page styles or in your breakpoint styles.\r\n\r\n\r\n## Plugin Features\r\n\r\n### Initial SASSquatch installation/setup.\r\nThis uses the parameters defined in the SASSquatch config in your Gruntfile to output the base folder and file structure for SASSquatch.\r\n\r\nYou can define your initial modules and pages, as well as your breakpoints and any additional config or helper files you may want.\r\n\r\nThe sample config in the plugin gruntfile includes:\r\n* home page\r\n* contact page\r\n* typography module\r\n* buttons module\r\n* color map config\r\n\r\n*NOTE: At the moment, it seems like you HAVE to explicitly add a SASSquatch config to your top level Gruntfile; the plugin doesnt fall back to what's defined in the plugin gruntfile as default. I am sure there is a way to do this, but I am a novice with grunt, so for now bear with me!*\r\n\r\n### Add Page\r\nYou can add a page to your build, and the plugin will automatically generate the appropraite files, paritals and config include lines, to reduce the manualy dependancy.\r\n\r\n### Add Module\r\nSame as with adding pages, the plugin handles the files and config for you.\r\n\r\n## Future plugin features\r\n\r\n* Removing pages and modules.\r\n* Adding and removing helpers and configs\r\n* Setting default modules to be added to constructor automatically","readmeFilename":"README.md","_id":"grunt-sassquatch@0.2.1","dist":{"shasum":"f0ecdb49b511f5bd79627a63c993b27eda14b854","tarball":"https://registry.npmjs.org/grunt-sassquatch/-/grunt-sassquatch-0.2.1.tgz","integrity":"sha512-RlDMoYFV0ljtYUq/zkRm+sHK3lOGYF+5gy3WF0OPAnyUrSG8BH2gHz0rex/79J/qvr8simRZwR1U0bpljn9suw==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEYCIQCH9eyCLakKWfdvG8tWqq3CfdKu4wY3yyXAlXtnAYhmxgIhAKdJJQLChb3jHW0I2JRrqzX2O8QQzlQz/0tL9qK1bIE6"}]},"_from":".","_npmVersion":"1.3.8","_npmUser":{"name":"thealscott","email":"thealscott@gmail.com"},"maintainers":[{"name":"thealscott","email":"thealscott@gmail.com"}]},"0.2.2":{"name":"grunt-sassquatch","description":"SASSquatch, the modular SASS framework.","version":"0.2.2","homepage":"https://github.com/thealscott/sassquatch","author":{"name":"Al Scott","email":"thealscott@gmail.com"},"repository":{"type":"git","url":"git://github.com/thealscott/sassquatch.git"},"bugs":{"url":"https://github.com/thealscott/sassquatch/issues"},"licenses":[{"type":"MIT","url":"https://github.com/thealscott/sassquatch/blob/master/LICENSE-MIT"}],"main":"Gruntfile.js","engines":{"node":">= 0.8.0"},"scripts":{"test":"grunt test"},"devDependencies":{"grunt-contrib-jshint":"~0.6.0","grunt-contrib-clean":"~0.4.0","grunt-contrib-nodeunit":"~0.2.0","grunt":"~0.4.1"},"peerDependencies":{"grunt":"~0.4.1"},"keywords":["gruntplugin"],"readme":"# (grunt) SASSquatch\r\n\r\n**The grunt plugin branch is now the master branch of this project. If you want to see what SASSquatch looks like when implemented, look at the Implemented branch**\r\n\r\nSASSquatch is a SASS framework (in as much as such a thing is possible), built on top of Compass.\r\n\r\nIt splits your SASS code up into a logical groupings, based on the premise of using common modules and page specific layouts/overrides. \r\n\r\nIt encourages the use of placeholders and extending base classes, and tries to keep code as modular and reusable as possible while avoiding the pitfalls of overly presentational markup. \r\n\r\nIt also aims to give you the tools you need to define and work with responsive design. The structure has been largely driven by the desire to have common placeholder classes that can be extended from within media query blocks.\r\n\r\nIt can be used Vanilla, but this requires a lot of manual management of adding files and line to import configs, so I recommend using the Grunt plugin.\r\n\r\nBoth the framework and the Grunt plugin are still in the very early stages, so there is a lot that will probably change, both in terms of the framework approach, and in terms of the functionality of the plugin.\r\n\r\n## Framework guide \r\n\r\n*MORE COMING SOON*\r\n\r\nI will write more on the structure and thinking behind the actual framework, as well as some additional usage documentation in the near future, but for now I have outline some top level information and guidelines below. \r\n\r\n### Breakpoints\r\nBecause of SASS's limitiations regarding extending classes across media blocks, in order to have one common source for extensible classes it is neccessary to have each media query as a separate compiled file. Each breakpoint generates a separate SASS file that will compile to separate CSS files. These should all be included in your HTML.\r\n\r\n*NOTE: I would rather be able to compile everything into a single CSS file, but at present some quirks of SASS seem to preclude that possibilty so long as you want to make use of extensible classes declared outside the media block. I had originally hoped to avoid this by redeclaring those placeholders within each media block by calling the mixin again within the block, but SASS seems to ignore these redeclarations when you try and compile everything together, and so the first declaration still triggers the extend error on compile*\r\n\r\n### Modules\r\nModules are where modular stylesets can be kept. These are styles that will be reused across the design, things like buttons, typography rules and so forth. Ideally you define placeholder classes here, that can be \"instantiated\" by extending them in your main/page styles, attached to semantic classes.  \r\n\r\n### Pages\r\nPage/pagetype specific markup hooks and styling should happen here. This requires the use of page type hooks (I suggest on the body element) in order to \"namespace\" your styles for a specific page or type of page. I find this approach useful, even if you are working on a very uniform page design, but obviously it is most useful when designs vary between pages.\r\n\r\n### Config\r\nGenerally you will be using scoped variables inside all the pages/modules, but if you need universal config variables, here is where to put them. In addition, the system config (import lists) will be in this folder too. As an example of a config, I use a color map where I can assign more memorable names for commonly used colors in the theme, without assigning them semantic var names. \r\n\r\n### Helpers\r\nIf you have general utility mixins or functions over and above compass, this is the place for them to live.\r\n\r\n### The Constructor\r\nThe constructor currently lives in the helpers folder (though I might move it, as it is special) and it serves a role similar to what its name implies. Each breakpoint stylesheet starts by including the construtor. In the constructor we should define any and all modules and helpers that you want to be universally applied/availble. If you don't include them in the constructor, you need to include them manually either in your page styles or in your breakpoint styles.\r\n\r\n\r\n## Plugin Features and tasks\r\n\r\n*NOTE: 'SASSquatch' is a wicked name, but can be a bugger to type quickly, so 'yeti' can be used as shorthand for all tasks*\r\n\r\n### Initial SASSquatch installation/setup.\r\n\r\n`grunt sassquatch_setup`\r\n\r\n`grunt yeti_setup`\r\n\r\nThis uses the parameters defined in the SASSquatch config in your Gruntfile to output the base folder and file structure for SASSquatch.\r\n\r\nYou can define your initial modules and pages, as well as your breakpoints and any additional config or helper files you may want.\r\n\r\nThe sample config in the plugin gruntfile includes:\r\n* home page\r\n* contact page\r\n* typography module\r\n* buttons module\r\n* color map config\r\n\r\n*NOTE: At the moment, it seems like you HAVE to explicitly add a SASSquatch config to your top level Gruntfile; the plugin doesnt fall back to what's defined in the plugin gruntfile as default. I am sure there is a way to do this, but I am a novice with grunt, so for now bear with me!*\r\n\r\n### Add Page\r\n\r\n`grunt sassquatch_add_page:[page name]`\r\n\r\n`grunt yeti_add_page:[page name]`\r\n\r\nYou can add a page to your build, and the plugin will automatically generate the appropraite files, paritals and config include lines, to reduce the manualy dependancy.\r\n\r\n### Add Module\r\n\r\n`grunt sassquatch_add_module:[module name]`\r\n\r\n`grunt yeti_add_module:[module name]`\r\n\r\nSame as with adding pages, the plugin handles the files and config for you.\r\n\r\n## Future plugin features\r\n\r\n* Removing pages and modules.\r\n* Adding and removing helpers and configs\r\n* Setting default modules to be added to constructor automatically\r\n","readmeFilename":"README.md","_id":"grunt-sassquatch@0.2.2","dist":{"shasum":"0b9594e59f1c5b1deafebb515fffcd85f7b29e97","tarball":"https://registry.npmjs.org/grunt-sassquatch/-/grunt-sassquatch-0.2.2.tgz","integrity":"sha512-o5CNk1/BEyS9aeKfIsK23owxKaWk/8aDxvnToVEpN0LRaISgErXcW9fhqsCC6XxwQyjk/eyyUblVfK0MNwLyWQ==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIB/YD6p7PGuxw9tHdOrQTrnd7sb0O85fjLYKsgaf6+RQAiEAgU5Gp3lntNTEmZVjoBDSfCjxKFgnlffl4tvOMfilyxg="}]},"_from":".","_npmVersion":"1.3.8","_npmUser":{"name":"thealscott","email":"thealscott@gmail.com"},"maintainers":[{"name":"thealscott","email":"thealscott@gmail.com"}]},"0.2.3":{"name":"grunt-sassquatch","description":"SASSquatch, the modular SASS framework.","version":"0.2.3","homepage":"https://github.com/thealscott/sassquatch","author":{"name":"Al Scott","email":"thealscott@gmail.com"},"repository":{"type":"git","url":"git://github.com/thealscott/sassquatch.git"},"bugs":{"url":"https://github.com/thealscott/sassquatch/issues"},"licenses":[{"type":"MIT","url":"https://github.com/thealscott/sassquatch/blob/master/LICENSE-MIT"}],"main":"Gruntfile.js","engines":{"node":">= 0.8.0"},"scripts":{"test":"grunt test"},"devDependencies":{"grunt-contrib-jshint":"~0.6.0","grunt-contrib-clean":"~0.4.0","grunt-contrib-nodeunit":"~0.2.0","grunt":"~0.4.1"},"peerDependencies":{"grunt":"~0.4.1"},"keywords":["gruntplugin"],"readme":"# (grunt) SASSquatch\r\n\r\n**The grunt plugin branch is now the master branch of this project. If you want to see what SASSquatch looks like when implemented, look at the Implemented branch**\r\n\r\nSASSquatch is a SASS framework (in as much as such a thing is possible), built on top of Compass.\r\n\r\nIt splits your SASS code up into a logical groupings, based on the premise of using common modules and page specific layouts/overrides. \r\n\r\nIt encourages the use of placeholders and extending base classes, and tries to keep code as modular and reusable as possible while avoiding the pitfalls of overly presentational markup. \r\n\r\nIt also aims to give you the tools you need to define and work with responsive design. The structure has been largely driven by the desire to have common placeholder classes that can be extended from within media query blocks.\r\n\r\nIt can be used Vanilla, but this requires a lot of manual management of adding files and line to import configs, so I recommend using the Grunt plugin.\r\n\r\nBoth the framework and the Grunt plugin are still in the very early stages, so there is a lot that will probably change, both in terms of the framework approach, and in terms of the functionality of the plugin.\r\n\r\n## Framework guide \r\n\r\n*MORE COMING SOON*\r\n\r\nI will write more on the structure and thinking behind the actual framework, as well as some additional usage documentation in the near future, but for now I have outline some top level information and guidelines below. \r\n\r\n### Breakpoints\r\nBecause of SASS's limitations regarding extending classes across media blocks, in order to have one common source for extensible classes it is neccessary to have each media query as a separate compiled file. Each breakpoint generates a separate SASS file that will compile to separate CSS files. These should all be included in your HTML.\r\n\r\n*NOTE: I would rather be able to compile everything into a single CSS file, but at present some quirks of SASS seem to preclude the possibility so long as you want to make use of extensible classes declared outside the media block. I had originally hoped to avoid this by redeclaring those placeholders within each media block by calling the mixin again within the block, but SASS seems to ignore these declarations when you try and compile everything together, and so the first declaration still triggers the extend error on compile* \r\n\r\n### Modules\r\nModules are where modular style sets can be kept. These are styles that will be reused across the design, things like buttons, typography rules and so forth. Ideally you define placeholder classes here, that can be \"instantiated\" by extending them in your main/page styles, attached to semantic classes.  \r\n\r\n### Pages\r\nPage/pagetype specific markup hooks and styling should happen here. This requires the use of page type hooks (I suggest on the body element) in order to \"namespace\" your styles for a specific page or type of page. I find this approach useful, even if you are working on a very uniform page design, but obviously it is most useful when designs vary between pages.\r\n\r\n### Config\r\nGenerally you will be using scoped variables inside all the pages/modules, but if you need universal config variables, here is where to put them. In addition, the system config (import lists) will be in this folder too. As an example of a config, I use a color map where I can assign more memorable names for commonly used colors in the theme, without assigning them semantic var names. \r\n\r\n### Helpers\r\nIf you have general utility mixins or functions over and above compass, this is the place for them to live.\r\n\r\n### The Constructor\r\nThe constructor currently lives in the helpers folder (though I might move it, as it is special) and it serves a role similar to what its name implies. Each breakpoint stylesheet starts by including the constructor. In the constructor we should define any and all modules and helpers that you want to be universally applied/available. If you don't include them in the constructor, you need to include them manually either in your page styles or in your breakpoint styles.\r\n\r\n## Plugin Features and tasks\r\n\r\n*NOTE: 'SASSquatch' is a wicked name, but can be a bugger to type quickly, so 'yeti' can be used as shorthand for all tasks*\r\n\r\n### Initial SASSquatch installation/setup.\r\n\r\n`grunt sassquatch_setup`\r\n\r\n`grunt yeti_setup`\r\n\r\nThis uses the parameters defined in the SASSquatch config in your Gruntfile to output the base folder and file structure for SASSquatch.\r\n\r\nYou can define your initial modules and pages, as well as your breakpoints and any additional config or helper files you may want.\r\n\r\nThe sample config in the plugin gruntfile includes:\r\n* home page\r\n* contact page\r\n* typography module\r\n* buttons module\r\n* color map config\r\n\r\n*NOTE: At the moment, it seems like you HAVE to explicitly add a SASSquatch config to your top level Gruntfile; the plugin doesnt fall back to what's defined in the plugin gruntfile as default. I am sure there is a way to do this, but I am a novice with grunt, so for now bear with me!*\r\n\r\n### Add Page\r\n\r\n`grunt sassquatch_add_page:[page name]`\r\n\r\n`grunt yeti_add_page:[page name]`\r\n\r\nYou can add a page to your build, and the plugin will automatically generate the appropriate files, partials and config include lines, to reduce the manualy dependancy.\r\n\r\n### Add Module\r\n\r\n`grunt sassquatch_add_module:[module name]`\r\n\r\n`grunt yeti_add_module:[module name]`\r\n\r\nSame as with adding pages, the plugin handles the files and config for you.\r\n\r\n## Future plugin features\r\n\r\n* Removing pages and modules.\r\n* Adding and removing helpers and configs\r\n* Setting default modules to be added to constructor automatically\r\n","readmeFilename":"README.md","_id":"grunt-sassquatch@0.2.3","dist":{"shasum":"78ba8b2ab3e55048ac78535c03ee11f62efaae76","tarball":"https://registry.npmjs.org/grunt-sassquatch/-/grunt-sassquatch-0.2.3.tgz","integrity":"sha512-XaQH4xj7qn6bcZVhxPvFDLerViDdVCOEPYcz6kgHVEuSigKBW/U+9a4IUJ+ubh04z1piV7FyGGr8tRIPAAMzVA==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIFI2oI/rOKZv5ZlocTXsem5H9CijtIUKPhhZLqS2bx/dAiEA93IbdWzoHuYu573siYSw5j3V/cREKuALveMr4A9Af/s="}]},"_from":".","_npmVersion":"1.3.8","_npmUser":{"name":"thealscott","email":"thealscott@gmail.com"},"maintainers":[{"name":"thealscott","email":"thealscott@gmail.com"}]},"0.2.4":{"name":"grunt-sassquatch","description":"SASSquatch, the modular SASS framework.","version":"0.2.4","homepage":"https://github.com/thealscott/sassquatch","author":{"name":"Al Scott","email":"thealscott@gmail.com"},"repository":{"type":"git","url":"git://github.com/thealscott/sassquatch.git"},"bugs":{"url":"https://github.com/thealscott/sassquatch/issues"},"licenses":[{"type":"MIT","url":"https://github.com/thealscott/sassquatch/blob/master/LICENSE-MIT"}],"main":"Gruntfile.js","engines":{"node":">= 0.8.0"},"scripts":{"test":"grunt test"},"devDependencies":{"grunt-contrib-jshint":"~0.6.0","grunt-contrib-clean":"~0.4.0","grunt-contrib-nodeunit":"~0.2.0","grunt":"~0.4.1"},"peerDependencies":{"grunt":"~0.4.1"},"keywords":["gruntplugin"],"readme":"# (grunt) SASSquatch\n\n**The grunt plugin branch is now the master branch of this project. If you want to see what SASSquatch looks like when implemented, look at the Implemented branch**\n\nSASSquatch is a SASS framework (in as much as such a thing is possible), built on top of Compass.\n\nIt splits your SASS code up into a logical groupings, based on the premise of using common modules and page specific layouts/overrides. \n\nIt encourages the use of placeholders and extending base classes, and tries to keep code as modular and reusable as possible while avoiding the pitfalls of overly presentational markup. \n\nIt also aims to give you the tools you need to define and work with responsive design. The structure has been largely driven by the desire to have common placeholder classes that can be extended from within media query blocks.\n\nIt can be used Vanilla, but this requires a lot of manual management of adding files and line to import configs, so I recommend using the Grunt plugin.\n\nBoth the framework and the Grunt plugin are still in the very early stages, so there is a lot that will probably change, both in terms of the framework approach, and in terms of the functionality of the plugin.\n\n## Framework guide \n\n*MORE COMING SOON*\n\nI will write more on the structure and thinking behind the actual framework, as well as some additional usage documentation in the near future, but for now I have outline some top level information and guidelines below. \n\n### Breakpoints\nBecause of SASS's limitations regarding extending classes across media blocks, in order to have one common source for extensible classes it is neccessary to have each media query as a separate compiled file. Each breakpoint generates a separate SASS file that will compile to separate CSS files. These should all be included in your HTML.\n\n*NOTE: I would rather be able to compile everything into a single CSS file, but at present some quirks of SASS seem to preclude the possibility so long as you want to make use of extensible classes declared outside the media block. I had originally hoped to avoid this by redeclaring those placeholders within each media block by calling the mixin again within the block, but SASS seems to ignore these declarations when you try and compile everything together, and so the first declaration still triggers the extend error on compile* \n\n### Modules\nModules are where modular style sets can be kept. These are styles that will be reused across the design, things like buttons, typography rules and so forth. Ideally you define placeholder classes here, that can be \"instantiated\" by extending them in your main/page styles, attached to semantic classes.  \n\n### Pages\nPage/pagetype specific markup hooks and styling should happen here. This requires the use of page type hooks (I suggest on the body element) in order to \"namespace\" your styles for a specific page or type of page. I find this approach useful, even if you are working on a very uniform page design, but obviously it is most useful when designs vary between pages.\n\n### Config\nGenerally you will be using scoped variables inside all the pages/modules, but if you need universal config variables, here is where to put them. In addition, the system config (import lists) will be in this folder too. As an example of a config, I use a color map where I can assign more memorable names for commonly used colors in the theme, without assigning them semantic var names. \n\n### Helpers\nIf you have general utility mixins or functions over and above compass, this is the place for them to live.\n\n### The Constructor\nThe constructor currently lives in the helpers folder (though I might move it, as it is special) and it serves a role similar to what its name implies. Each breakpoint stylesheet starts by including the constructor. In the constructor we should define any and all modules and helpers that you want to be universally applied/available. If you don't include them in the constructor, you need to include them manually either in your page styles or in your breakpoint styles.\n\n## Plugin Features and tasks\n\n*NOTE: 'SASSquatch' is a wicked name, but can be a bugger to type quickly, so 'yeti' can be used as shorthand for all tasks*\n\n### Initial SASSquatch installation/setup.\n\n`grunt sassquatch_setup`\n\n`grunt yeti_setup`\n\nThis uses the parameters defined in the SASSquatch config in your Gruntfile to output the base folder and file structure for SASSquatch. It also outputs a default-ish Compass config.rb file. This will be configurable in future, but for now it is just some quite standard output and you can manually edit/remove it. \n\nYou can define your initial modules and pages, as well as your breakpoints and any additional config or helper files you may want.\n\nThe sample config in the plugin gruntfile includes:\n* home page\n* contact page\n* typography module\n* buttons module\n* color map config\n\n*NOTE: At the moment, it seems like you HAVE to explicitly add a SASSquatch config to your top level Gruntfile; the plugin doesnt fall back to what's defined in the plugin gruntfile as default. I am sure there is a way to do this, but I am a novice with grunt, so for now bear with me!*\n\n### Add Page\n\n`grunt sassquatch_add_page:[page name]`\n\n`grunt yeti_add_page:[page name]`\n\nYou can add a page to your build, and the plugin will automatically generate the appropriate files, partials and config include lines, to reduce the manualy dependancy.\n\n### Add Module\n\n`grunt sassquatch_add_module:[module name]`\n\n`grunt yeti_add_module:[module name]`\n\nSame as with adding pages, the plugin handles the files and config for you.\n\n## Future plugin features\n\n* Removing pages and modules.\n* Adding and removing helpers and configs\n* Setting default modules to be added to constructor automatically\n","readmeFilename":"README.md","_id":"grunt-sassquatch@0.2.4","dist":{"shasum":"68e75aac60a3ebb972b9cdb269b74fbdfda4a3eb","tarball":"https://registry.npmjs.org/grunt-sassquatch/-/grunt-sassquatch-0.2.4.tgz","integrity":"sha512-MhzFsiQ6akN+dqrg7HcqSD2XzWv4Tf6zNbw1EuZ8QHHjsqKkAtpmcbbZrzZOWU6uBFeUSqfLEZpqiImGILwVhA==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIGEGwn2l2ra/NhABKvS3/J7vcpF79BSbJpd1UFKvMrWQAiEAjzGairSxEoDG7bGEHROv1rCwcKERXJPIWOSJzaSmAuo="}]},"_from":".","_npmVersion":"1.3.5","_npmUser":{"name":"thealscott","email":"thealscott@gmail.com"},"maintainers":[{"name":"thealscott","email":"thealscott@gmail.com"}]},"0.2.5":{"name":"grunt-sassquatch","description":"SASSquatch, the modular SASS framework.","version":"0.2.5","homepage":"https://github.com/thealscott/sassquatch","author":{"name":"Al Scott","email":"thealscott@gmail.com"},"repository":{"type":"git","url":"git://github.com/thealscott/sassquatch.git"},"bugs":{"url":"https://github.com/thealscott/sassquatch/issues"},"licenses":[{"type":"MIT","url":"https://github.com/thealscott/sassquatch/blob/master/LICENSE-MIT"}],"main":"Gruntfile.js","engines":{"node":">= 0.8.0"},"scripts":{"test":"grunt test"},"devDependencies":{"grunt-contrib-jshint":"~0.6.0","grunt-contrib-clean":"~0.4.0","grunt-contrib-nodeunit":"~0.2.0","grunt":"~0.4.1"},"peerDependencies":{"grunt":"~0.4.1"},"keywords":["gruntplugin"],"readme":"# (grunt) SASSquatch\r\n\r\n**The grunt plugin branch is now the master branch of this project. If you want to see what SASSquatch looks like when implemented, look at the Implemented branch**\r\n\r\nSASSquatch is a SASS framework (in as much as such a thing is possible), built on top of Compass.\r\n\r\nIt splits your SASS code up into a logical groupings, based on the premise of using common modules and page specific layouts/overrides. \r\n\r\nIt encourages the use of placeholders and extending base classes, and tries to keep code as modular and reusable as possible while avoiding the pitfalls of overly presentational markup. \r\n\r\nIt also aims to give you the tools you need to define and work with responsive design. The structure has been largely driven by the desire to have common placeholder classes that can be extended from within media query blocks.\r\n\r\nIt can be used Vanilla, but this requires a lot of manual management of adding files and line to import configs, so I recommend using the Grunt plugin.\r\n\r\nBoth the framework and the Grunt plugin are still in the very early stages, so there is a lot that will probably change, both in terms of the framework approach, and in terms of the functionality of the plugin.\r\n\r\n## Framework guide \r\n\r\n*MORE COMING SOON*\r\n\r\nI will write more on the structure and thinking behind the actual framework, as well as some additional usage documentation in the near future, but for now I have outline some top level information and guidelines below. \r\n\r\n### Breakpoints\r\nBecause of SASS's limitations regarding extending classes across media blocks, in order to have one common source for extensible classes it is neccessary to have each media query as a separate compiled file. Each breakpoint generates a separate SASS file that will compile to separate CSS files. These should all be included in your HTML.\r\n\r\n*NOTE: I would rather be able to compile everything into a single CSS file, but at present some quirks of SASS seem to preclude the possibility so long as you want to make use of extensible classes declared outside the media block. I had originally hoped to avoid this by redeclaring those placeholders within each media block by calling the mixin again within the block, but SASS seems to ignore these declarations when you try and compile everything together, and so the first declaration still triggers the extend error on compile* \r\n\r\n### Modules\r\nModules are where modular style sets can be kept. These are styles that will be reused across the design, things like buttons, typography rules and so forth. Ideally you define placeholder classes here, that can be \"instantiated\" by extending them in your main/page styles, attached to semantic classes.  \r\n\r\n### Pages\r\nPage/pagetype specific markup hooks and styling should happen here. This requires the use of page type hooks (I suggest on the body element) in order to \"namespace\" your styles for a specific page or type of page. I find this approach useful, even if you are working on a very uniform page design, but obviously it is most useful when designs vary between pages.\r\n\r\n### Config\r\nGenerally you will be using scoped variables inside all the pages/modules, but if you need universal config variables, here is where to put them. In addition, the system config (import lists) will be in this folder too. As an example of a config, I use a color map where I can assign more memorable names for commonly used colors in the theme, without assigning them semantic var names. \r\n\r\n### Helpers\r\nIf you have general utility mixins or functions over and above compass, this is the place for them to live.\r\n\r\n### The Constructor\r\nThe constructor currently lives in the helpers folder (though I might move it, as it is special) and it serves a role similar to what its name implies. Each breakpoint stylesheet starts by including the constructor. In the constructor we should define any and all modules and helpers that you want to be universally applied/available. If you don't include them in the constructor, you need to include them manually either in your page styles or in your breakpoint styles.\r\n\r\n## Plugin Features and tasks\r\n\r\n*NOTE: 'SASSquatch' is a wicked name, but can be a bugger to type quickly, so 'yeti' can be used as shorthand for all tasks*\r\n\r\n### Initial SASSquatch installation/setup.\r\n\r\n`grunt sassquatch_setup`\r\n\r\n`grunt yeti_setup`\r\n\r\nThis uses the parameters defined in the SASSquatch config in your Gruntfile to output the base folder and file structure for SASSquatch. It also outputs a default-ish Compass config.rb file. This will be configurable in future, but for now it is just some quite standard output and you can manually edit/remove it. \r\n\r\nYou can define your initial modules and pages, as well as your breakpoints and any additional config or helper files you may want.\r\n\r\nThe sample config in the plugin gruntfile includes:\r\n* home page\r\n* contact page\r\n* typography module\r\n* buttons module\r\n* color map config\r\n\r\n*NOTE: At the moment, it seems like you HAVE to explicitly add a SASSquatch config to your top level Gruntfile; the plugin doesnt fall back to what's defined in the plugin gruntfile as default. I am sure there is a way to do this, but I am a novice with grunt, so for now bear with me!*\r\n\r\n### Add Page\r\n\r\n`grunt sassquatch_add_page:[page name]`\r\n\r\n`grunt yeti_add_page:[page name]`\r\n\r\nYou can add a page to your build, and the plugin will automatically generate the appropriate files, partials and config include lines, to reduce the manualy dependancy.\r\n\r\n### Add Module\r\n\r\n`grunt sassquatch_add_module:[module name]`\r\n\r\n`grunt yeti_add_module:[module name]`\r\n\r\nSame as with adding pages, the plugin handles the files and config for you.\r\n\r\n## Future plugin features\r\n\r\n* Removing pages and modules.\r\n* Adding and removing helpers and configs\r\n* Setting default modules to be added to constructor automatically\r\n","readmeFilename":"README.md","_id":"grunt-sassquatch@0.2.5","dist":{"shasum":"b3a664c8dac705dba215852db1657384dc84a6b2","tarball":"https://registry.npmjs.org/grunt-sassquatch/-/grunt-sassquatch-0.2.5.tgz","integrity":"sha512-9T58c4+Qfcrark4HfLFnIvD8kfiFHjbUiz8hcnUEZU2zDZF4cbXVyOzBhYqYTOMfz3wsih1hY/vGHeAW20elkg==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIQCgWX40LT4WbEjBjMAa3UAWQhbbNq8/Y510Z8w9nMZWrQIgSTGsdfz75wXfahr/wt/vEj+fW8iZfbzb5GIcu4mzoO8="}]},"_from":".","_npmVersion":"1.3.8","_npmUser":{"name":"thealscott","email":"thealscott@gmail.com"},"maintainers":[{"name":"thealscott","email":"thealscott@gmail.com"}]},"0.2.6":{"name":"grunt-sassquatch","description":"SASSquatch, the modular SASS framework.","version":"0.2.6","homepage":"https://github.com/thealscott/sassquatch","author":{"name":"Al Scott","email":"thealscott@gmail.com"},"repository":{"type":"git","url":"git://github.com/thealscott/sassquatch.git"},"bugs":{"url":"https://github.com/thealscott/sassquatch/issues"},"licenses":[{"type":"MIT","url":"https://github.com/thealscott/sassquatch/blob/master/LICENSE-MIT"}],"main":"Gruntfile.js","engines":{"node":">= 0.8.0"},"devDependencies":{"grunt":"~0.4.1"},"peerDependencies":{"grunt":"~0.4.1"},"keywords":["gruntplugin"],"readme":"# (grunt) SASSquatch\n\n**The grunt plugin branch is now the master branch of this project. If you want to see what SASSquatch looks like when implemented, look at the Implemented branch**\n\nSASSquatch is a SASS framework (in as much as such a thing is possible), built on top of Compass.\n\nIt splits your SASS code up into a logical groupings, based on the premise of using common modules and page specific layouts/overrides. \n\nIt encourages the use of placeholders and extending base classes, and tries to keep code as modular and reusable as possible while avoiding the pitfalls of overly presentational markup. \n\nIt also aims to give you the tools you need to define and work with responsive design. The structure has been largely driven by the desire to have common placeholder classes that can be extended from within media query blocks.\n\nIt can be used Vanilla, but this requires a lot of manual management of adding files and line to import configs, so I recommend using the Grunt plugin.\n\nBoth the framework and the Grunt plugin are still in the very early stages, so there is a lot that will probably change, both in terms of the framework approach, and in terms of the functionality of the plugin.\n\n## Framework guide \n\n*MORE COMING SOON*\n\nI will write more on the structure and thinking behind the actual framework, as well as some additional usage documentation in the near future, but for now I have outline some top level information and guidelines below. \n\n### Breakpoints\nBecause of SASS's limitations regarding extending classes across media blocks, in order to have one common source for extensible classes it is neccessary to have each media query as a separate compiled file. Each breakpoint generates a separate SASS file that will compile to separate CSS files. These should all be included in your HTML.\n\n*NOTE: I would rather be able to compile everything into a single CSS file, but at present some quirks of SASS seem to preclude the possibility so long as you want to make use of extensible classes declared outside the media block. I had originally hoped to avoid this by redeclaring those placeholders within each media block by calling the mixin again within the block, but SASS seems to ignore these declarations when you try and compile everything together, and so the first declaration still triggers the extend error on compile* \n\n### Modules\nModules are where modular style sets can be kept. These are styles that will be reused across the design, things like buttons, typography rules and so forth. Ideally you define placeholder classes here, that can be \"instantiated\" by extending them in your main/page styles, attached to semantic classes.  \n\n### Pages\nPage/pagetype specific markup hooks and styling should happen here. This requires the use of page type hooks (I suggest on the body element) in order to \"namespace\" your styles for a specific page or type of page. I find this approach useful, even if you are working on a very uniform page design, but obviously it is most useful when designs vary between pages.\n\n### Config\nGenerally you will be using scoped variables inside all the pages/modules, but if you need universal config variables, here is where to put them. In addition, the system config (import lists) will be in this folder too. As an example of a config, I use a color map where I can assign more memorable names for commonly used colors in the theme, without assigning them semantic var names. \n\n### Helpers\nIf you have general utility mixins or functions over and above compass, this is the place for them to live.\n\n### The Constructor\nThe constructor currently lives in the helpers folder (though I might move it, as it is special) and it serves a role similar to what its name implies. Each breakpoint stylesheet starts by including the constructor. In the constructor we should define any and all modules and helpers that you want to be universally applied/available. If you don't include them in the constructor, you need to include them manually either in your page styles or in your breakpoint styles.\n\n## Plugin Features and tasks\n\n*NOTE: 'SASSquatch' is a wicked name, but can be a bugger to type quickly, so 'yeti' can be used as shorthand for all tasks*\n\n### Initial SASSquatch installation/setup.\n\n`grunt sassquatch_setup`\n\n`grunt yeti_setup`\n\nThis uses the parameters defined in the SASSquatch config in your Gruntfile to output the base folder and file structure for SASSquatch. It also outputs a default-ish Compass config.rb file. This will be configurable in future, but for now it is just some quite standard output and you can manually edit/remove it. \n\nYou can define your initial modules and pages, as well as your breakpoints and any additional config or helper files you may want.\n\nSample Config:\n\n    sassquatch: {\n      compass : true,\n      sass_path : 'sass',\n      extra_configs : [\n        'color_map'\n      ],\n      helpers : [],\n      breakpoints : [\n        // base always exists\n        '480',\n        '768', \n        '960'\n      ],\n      pages : [\n        // default always exists\n        'home',\n        'contact'\n      ],\n      modules : [\n        'typography',\n        'buttons'\n      ]\n    }\n\n### Add Page\n\n`grunt sassquatch_add_page:[page name]`\n\n`grunt yeti_add_page:[page name]`\n\nYou can add a page to your build, and the plugin will automatically generate the appropriate files, partials and config include lines, to reduce the manualy dependancy.\n\n### Add Module\n\n`grunt sassquatch_add_module:[module name]`\n\n`grunt yeti_add_module:[module name]`\n\nSame as with adding pages, the plugin handles the files and config for you.\n\n## Future plugin features\n\n* Removing pages and modules.\n* Adding and removing helpers and configs\n* Setting default modules to be added to constructor automatically\n","readmeFilename":"README.md","_id":"grunt-sassquatch@0.2.6","dist":{"shasum":"26ff02ff5e6b98d2bf18d127aad277c4fdb6be2f","tarball":"https://registry.npmjs.org/grunt-sassquatch/-/grunt-sassquatch-0.2.6.tgz","integrity":"sha512-C8H1JJmQ9LCWYCS1WqFy8jrFhDStkeERllG/n1UPr3pfgjLQ1IK6lKHBaPZsxjwedwcDo/enjc+P0tsYAtL9iw==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEYCIQCC/wbJzJDsaAN9bXzxVmYX9iIwVbk2oWnapq+LskDk1QIhAK/BKy/sDNxgaa8mcl+lTqInEgUGLv9z6Trx/3XOIfDS"}]},"_from":".","_npmVersion":"1.3.5","_npmUser":{"name":"thealscott","email":"thealscott@gmail.com"},"maintainers":[{"name":"thealscott","email":"thealscott@gmail.com"}]},"0.2.7":{"name":"grunt-sassquatch","description":"SASSquatch, the modular SASS framework.","version":"0.2.7","homepage":"https://github.com/thealscott/sassquatch","author":{"name":"Al Scott","email":"thealscott@gmail.com"},"repository":{"type":"git","url":"git://github.com/thealscott/sassquatch.git"},"bugs":{"url":"https://github.com/thealscott/sassquatch/issues"},"licenses":[{"type":"MIT","url":"https://github.com/thealscott/sassquatch/blob/master/LICENSE-MIT"}],"main":"Gruntfile.js","engines":{"node":">= 0.8.0"},"devDependencies":{"grunt":"~0.4.1"},"peerDependencies":{"grunt":"~0.4.1"},"keywords":["gruntplugin"],"readme":"# (grunt) SASSquatch\n\n**The grunt plugin branch is now the master branch of this project. If you want to see what SASSquatch looks like when implemented, look at the [Implemented branch](https://github.com/thealscott/sassquatch/tree/implemented)**\n\nSASSquatch is a SASS framework (in as much as such a thing is possible), built on top of Compass.\n\nIt splits your SASS code up into a logical groupings, based on the premise of using common modules and page specific layouts/overrides. \n\nIt encourages the use of placeholders and extending base classes, and tries to keep code as modular and reusable as possible while avoiding the pitfalls of overly presentational markup. \n\nIt also aims to give you the tools you need to define and work with responsive design. The structure has been largely driven by the desire to have common placeholder classes that can be extended from within media query blocks.\n\nIt can be used Vanilla, but this requires a lot of manual management of adding files and line to import configs, so I recommend using the Grunt plugin.\n\nBoth the framework and the Grunt plugin are still in the very early stages, so there is a lot that will probably change, both in terms of the framework approach, and in terms of the functionality of the plugin.\n\n## Framework guide \n\n*MORE COMING SOON*\n\nI will write more on the structure and thinking behind the actual framework, as well as some additional usage documentation in the near future, but for now I have outlined some top level information and guidelines below. \n\n### [Breakpoints](README_BREAKPOINTS.md)\n\n### [Modules](README_MODULES.md)\n\n### [Pages](README_PAGES.md)\n\n### [Config](README_CONFIG.md)\n\n### [Helpers](README_HELPERS.md)\n\n### [The Constructor](README_CONSTRUCTOR.md)\n\n## Plugin Features and tasks\n\nThis is just a high level overview of available grunt tasks. More details can be found in the Framework documentation.\n\n*NOTE: 'SASSquatch' is a wicked name, but can be a bugger to type quickly, so 'yeti' can be used as shorthand for all tasks*\n\n### Initial SASSquatch installation/setup.\n\n`grunt sassquatch_setup`\n\n`grunt yeti_setup`\n\nThis uses the parameters defined in the SASSquatch config in your Gruntfile to output the base folder and file structure for SASSquatch. It also outputs a default-ish Compass config.rb file. This will be configurable in future, but for now it is just some quite standard output and you can manually edit/remove it. \n\nYou can define your initial modules and pages, as well as your breakpoints and any additional config or helper files you may want.\n\nSample Config:\n\n    sassquatch: {\n      compass : true,\n      sass_path : 'sass',\n      extra_configs : [\n        'color_map'\n      ],\n      helpers : [\n        'polyfills'\n      ],\n      breakpoints : [\n        // base always exists\n        '480',\n        '768', \n        '960'\n      ],\n      pages : [\n        // default always exists\n        'home',\n        'contact'\n      ],\n      modules : [\n        'typography',\n        'buttons'\n      ]\n    }\n\n### Add Page\n\n`grunt sassquatch_add_page:[page name]`\n\n`grunt yeti_add_page:[page name]`\n\nYou can add a page to your build, and the plugin will automatically generate the appropriate files, partials and config include lines, to reduce the manual dependency.\n\n### Add Module\n\n`grunt sassquatch_add_module:[module name]`\n\n`grunt yeti_add_module:[module name]`\n\nSame as with adding pages, the plugin handles the files and config for you.\n\n## Future plugin features (in no particular order)\n\n* Adding single css file include support\n* Removing pages and modules.\n* Adding and removing helpers and configs\n* Setting default modules to be added to constructor automatically\n* Non-numeric \"breakpoints\" (possibly with new name for the concept)\n* Configurable Compass config.rb\n* Move the Constructor our of Helpers\n","readmeFilename":"README.md","_id":"grunt-sassquatch@0.2.7","dist":{"shasum":"e7662fef1b0fd775db8c6c6cf8e1f99699a38b97","tarball":"https://registry.npmjs.org/grunt-sassquatch/-/grunt-sassquatch-0.2.7.tgz","integrity":"sha512-T/SlEizsaHM9Gupzd6MWh6SctCdjQjtvDXPFI700KjrNXxmUQUjkEq+H2vQA4orm/r6fRY/gNKJ99N3D/3HTbQ==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEQCIEgOGoAVU2XpLHcxJfflCUU2I86BFWJBgfLkQIni2RVTAiA/avMLwwPn31Eg+hnvK81tO+zmxW4p9uEOdiw+cUwdfw=="}]},"_from":".","_npmVersion":"1.3.5","_npmUser":{"name":"thealscott","email":"thealscott@gmail.com"},"maintainers":[{"name":"thealscott","email":"thealscott@gmail.com"}]},"0.2.8":{"name":"grunt-sassquatch","description":"SASSquatch, the modular SASS framework.","version":"0.2.8","homepage":"https://github.com/thealscott/sassquatch","author":{"name":"Al Scott","email":"thealscott@gmail.com"},"repository":{"type":"git","url":"git://github.com/thealscott/sassquatch.git"},"bugs":{"url":"https://github.com/thealscott/sassquatch/issues"},"licenses":[{"type":"MIT","url":"https://github.com/thealscott/sassquatch/blob/master/LICENSE-MIT"}],"main":"Gruntfile.js","engines":{"node":">= 0.8.0"},"devDependencies":{"grunt":"~0.4.1"},"peerDependencies":{"grunt":"~0.4.1"},"keywords":["gruntplugin"],"readme":"# (grunt) SASSquatch\n\n**The grunt plugin branch is now the master branch of this project. If you want to see what SASSquatch looks like when implemented, look at the [Implemented branch](https://github.com/thealscott/sassquatch/tree/implemented)**\n\nSASSquatch is a SASS framework (in as much as such a thing is possible), built on top of Compass.\n\nIt splits your SASS code up into a logical groupings, based on the premise of using common modules and page specific layouts/overrides. \n\nIt encourages the use of placeholders and extending base classes, and tries to keep code as modular and reusable as possible while avoiding the pitfalls of overly presentational markup. \n\nIt also aims to give you the tools you need to define and work with responsive design. The structure has been largely driven by the desire to have common placeholder classes that can be extended from within media query blocks.\n\nIt can be used Vanilla, but this requires a lot of manual management of adding files and line to import configs, so I recommend using the Grunt plugin.\n\nBoth the framework and the Grunt plugin are still in the very early stages, so there is a lot that will probably change, both in terms of the framework approach, and in terms of the functionality of the plugin.\n\n## Framework guide \n\n*MORE COMING SOON*\n\nI will write more on the structure and thinking behind the actual framework, as well as some additional usage documentation in the near future, but for now I have outlined some top level information and guidelines below. \n\n### [Breakpoints](README_BREAKPOINTS.md)\n\n### [Modules](README_MODULES.md)\n\n### [Pages](README_PAGES.md)\n\n### [Config](README_CONFIG.md)\n\n### [Helpers](README_HELPERS.md)\n\n### [The Constructor](README_CONSTRUCTOR.md)\n\n## Plugin Features and tasks\n\nThis is just a high level overview of available grunt tasks. More details can be found in the Framework documentation.\n\n*NOTE: 'SASSquatch' is a wicked name, but can be a bugger to type quickly, so 'yeti' can be used as shorthand for all tasks*\n\n### Initial SASSquatch installation/setup.\n\n`grunt sassquatch_setup`\n\n`grunt yeti_setup`\n\nThis uses the parameters defined in the SASSquatch config in your Gruntfile to output the base folder and file structure for SASSquatch. It also outputs a default-ish Compass config.rb file. This will be configurable in future, but for now it is just some quite standard output and you can manually edit/remove it. \n\nYou can define your initial modules and pages, as well as your breakpoints and any additional config or helper files you may want.\n\nSample Config:\n\n    sassquatch: {\n      compass : true,\n      sass_path : 'sass',\n      extra_configs : [\n        'color_map'\n      ],\n      helpers : [\n        'polyfills'\n      ],\n      breakpoints : [\n        // base always exists\n        '480',\n        '768', \n        '960'\n      ],\n      pages : [\n        // default always exists\n        'home',\n        'contact'\n      ],\n      modules : [\n        'typography',\n        'buttons'\n      ]\n    }\n\n### Add Page\n\n`grunt sassquatch_add_page:[page name]`\n\n`grunt yeti_add_page:[page name]`\n\nYou can add a page to your build, and the plugin will automatically generate the appropriate files, partials and config include lines, to reduce the manual dependency.\n\n### Add Module\n\n`grunt sassquatch_add_module:[module name]`\n\n`grunt yeti_add_module:[module name]`\n\nSame as with adding pages, the plugin handles the files and config for you.\n\n## Future plugin features (in no particular order)\n\n* Adding single css file include support\n* Removing pages and modules.\n* Adding and removing helpers and configs\n* Setting default modules to be added to constructor automatically\n* Non-numeric \"breakpoints\" (possibly with new name for the concept)\n* Configurable Compass config.rb\n* Move the Constructor our of Helpers\n","readmeFilename":"README.md","_id":"grunt-sassquatch@0.2.8","dist":{"shasum":"3a197922f8905ff00506f8e2ef515329ad9791d0","tarball":"https://registry.npmjs.org/grunt-sassquatch/-/grunt-sassquatch-0.2.8.tgz","integrity":"sha512-j4x7VNXeIagccUZ4eVONPEX0SdldYt8b1Q39YHZf7AWow0StuqvdYBISdGOgmR/JMsn6b1V0Nk2MWNZVEqBwPg==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIQCKmvp5RTsu6sId31yE+3030j/661oL071RUH/cDwv54wIgL4fCQ0h4uI9KsPhIPkAJkpF8qj/R/YYD0SmOiS33BaE="}]},"_from":".","_npmVersion":"1.3.5","_npmUser":{"name":"thealscott","email":"thealscott@gmail.com"},"maintainers":[{"name":"thealscott","email":"thealscott@gmail.com"}]},"0.2.9":{"name":"grunt-sassquatch","description":"SASSquatch, the modular SASS framework.","version":"0.2.9","homepage":"https://github.com/thealscott/sassquatch","author":{"name":"Al Scott","email":"thealscott@gmail.com"},"repository":{"type":"git","url":"git://github.com/thealscott/sassquatch.git"},"bugs":{"url":"https://github.com/thealscott/sassquatch/issues"},"licenses":[{"type":"MIT","url":"https://github.com/thealscott/sassquatch/blob/master/LICENSE-MIT"}],"main":"Gruntfile.js","engines":{"node":">= 0.8.0"},"devDependencies":{"grunt":"~0.4.1"},"peerDependencies":{"grunt":"~0.4.1"},"keywords":["gruntplugin"],"readme":"# (grunt) SASSquatch\n\n**The grunt plugin branch is now the master branch of this project. If you want to see what SASSquatch looks like when implemented, look at the [Implemented branch](https://github.com/thealscott/sassquatch/tree/implemented)**\n\n## Introduction\n\nSASSquatch is a SASS framework (in as much as such a thing is possible), built on top of Compass.\n\nIt splits your SASS code up into a logical groupings, based on the premise of using common modules and page specific layouts/overrides. \n\nIt encourages the use of placeholders and extending base classes, and tries to keep code as modular and reusable as possible while avoiding the pitfalls of overly presentational markup. \n\nIt also aims to give you the tools you need to define and work with responsive design. The structure has been largely driven by the desire to have common placeholder classes that can be extended from within media query blocks.\n\nIt can be used Vanilla, but this requires a lot of manual management of adding files and line to import configs, so I recommend using the Grunt plugin.\n\nBoth the framework and the Grunt plugin are still in the very early stages, so there is a lot that will probably change, both in terms of the framework approach, and in terms of the functionality of the plugin.\n\n## Framework documentation\n\n*This is still a work in progress*\n\n[Please view the full docs on Github.](https://github.com/thealscott/sassquatch/blob/master/docs/intro.md)\n\n## Quickstart Guide\n\nThis is a concise overview of getting SASSquatch installed and running for you. Please refer to the full docs for info about the structure and logic of the framework.\n\n### Installing Node.js and NPM\n\nGo to [http://nodejs.org/](http://nodejs.org/) and use the handy installation options they offer. \n\n### Installing Grunt Command Line Interface (CLI)\n\nNow you have NPM, you can install Grunt-CLI. Follow the handy instructions [here](http://gruntjs.com/getting-started).\n\n### Setting up Grunt and SASSquatch in a new project\n\nWith Grunt-CLI installed, you can now set up a new project. You can use a [grunt-init template](http://gruntjs.com/project-scaffolding) , or else simply run these tasks from the command line in your working folder:\n\n`npm init` \n\nThis creates *package.json*\n\n`npm install grunt --save-dev` \n\nThis will install grunt to the project and include the dependencies in your package.js automatically.\n\n`npm install sassquatch --save-dev`\n\nAs above, but for SASSquatch\n\n`touch Gruntfile.js`\n\nCreates the Gruntfile, where all your grunt tasks and configuration will live.\n\nYou can use this sample code below in your Gruntfile to get up and running. Change the config settings for SASSquatch to match your needs, or just try it out with the defaults.\n\n    module.exports = function(grunt) {\n    \n      // Project configuration.\n      grunt.initConfig({\n        pkg: grunt.file.readJSON('package.json'),\n        sassquatch: {\n          compass : true,\n          sass_path : 'sass',\n          extra_configs : [\n            'color_map'\n          ],\n          helpers : [\n            'polyfills'\n          ],\n          breakpoints : [\n            // base always exists\n            '600',\n            '960'\n          ],\n          pages : [\n            // default always exists\n            'home',\n            'contact'\n          ],\n          modules : [\n            'typography',\n            'buttons'\n          ]\n        }\n      });    \n      // Load the plugin for SASSquatch\n      grunt.loadNpmTasks('grunt-sassquatch');\n    };\n\nNow everything is installed and you have a package and gruntfile with all the needed stuff in it, you are ready to start using SASSquatch.\n\n`grunt sassquatch_setup`\n\nThis will run SASSquatch for the first time and generate all the framework files you need. It will also generate a *config.rb* file for use with Compass. You will need to manually edit this if you want to change from the default settings. If you are happy with your Compass settings, then all that's left to do is:\n\n`compass watch`\n\nand voila! your SASS will be compiled, and you are ready to roll.\n\nPlease refer to the [full docs](https://github.com/thealscott/sassquatch/blob/master/docs/intro.md) and the task overview below for more information.\n\n## Grunt Tasks Overview\n\n*NOTE: 'SASSquatch' is a wicked name, but can be a bugger to type quickly, so 'yeti' can be used as shorthand for all tasks*\n\n### Initial Setup\n\n`grunt sassquatch_setup`\n\n`grunt yeti_setup`\n\nThis uses the parameters defined in the SASSquatch config in your Gruntfile to output the base folder and file structure for SASSquatch. It also outputs a default-ish Compass config.rb file. This will be configurable in future, but for now it is just some quite standard output and you can manually edit/remove it. \n\nYou can define your initial modules and pages, as well as your breakpoints and any additional config or helper files you may want.\n\n### Add Page\n\n`grunt sassquatch_add_page:[page name]`\n\n`grunt yeti_add_page:[page name]`\n\nYou can add a page to your build, and the plugin will automatically generate the appropriate files, partials and config include lines, to reduce the manual dependency.\n\n### Add Module\n\n`grunt sassquatch_add_module:[module name]`\n\n`grunt yeti_add_module:[module name]`\n\nSame as with adding pages, the plugin handles the files and config for you.\n\n## Future plugin features (in no particular order)\n\n* Adding single css file include support\n* Removing pages and modules.\n* Adding and removing helpers and configs\n* Setting default modules to be added to constructor automatically\n* Non-numeric \"breakpoints\" (possibly with new name for the concept)\n* Configurable Compass config.rb\n* Move the Constructor our of Helpers\n","readmeFilename":"README.md","_id":"grunt-sassquatch@0.2.9","dist":{"shasum":"6384da7593e2ccf0b872a06eed1362ef6f151f5a","tarball":"https://registry.npmjs.org/grunt-sassquatch/-/grunt-sassquatch-0.2.9.tgz","integrity":"sha512-CzC+9nmoSn9kXEZ2bEiA8j08E29ygUiUnYHKF7kgWCE9TgCL9p9uZkduNawy5SFqlqYlbl1RA704MxBMp4Gd8w==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEQCIAooSOfcQAWz91hFqGG6mXBZbxGRT77fYxjnOBQNK0RDAiBp7s8LqG4ODJMCOu6FLJc7IsB4g82hCqXEpu+F5xbonQ=="}]},"_from":".","_npmVersion":"1.3.5","_npmUser":{"name":"thealscott","email":"thealscott@gmail.com"},"maintainers":[{"name":"thealscott","email":"thealscott@gmail.com"}]}},"readme":"# sassquatch-test\n\n> The best Grunt plugin ever.\n\n## Getting Started\nThis plugin requires Grunt `~0.4.1`\n\nIf you haven't used [Grunt](http://gruntjs.com/) before, be sure to check out the [Getting Started](http://gruntjs.com/getting-started) guide, as it explains how to create a [Gruntfile](http://gruntjs.com/sample-gruntfile) as well as install and use Grunt plugins. Once you're familiar with that process, you may install this plugin with this command:\n\n```shell\nnpm install sassquatch-test --save-dev\n```\n\nOnce the plugin has been installed, it may be enabled inside your Gruntfile with this line of JavaScript:\n\n```js\ngrunt.loadNpmTasks('sassquatch-test');\n```\n\n## The \"sassquatch_test\" task\n\n### Overview\nIn your project's Gruntfile, add a section named `sassquatch_test` to the data object passed into `grunt.initConfig()`.\n\n```js\ngrunt.initConfig({\n  sassquatch_test: {\n    options: {\n      // Task-specific options go here.\n    },\n    your_target: {\n      // Target-specific file lists and/or options go here.\n    },\n  },\n})\n```\n\n### Options\n\n#### options.separator\nType: `String`\nDefault value: `',  '`\n\nA string value that is used to do something with whatever.\n\n#### options.punctuation\nType: `String`\nDefault value: `'.'`\n\nA string value that is used to do something else with whatever else.\n\n### Usage Examples\n\n#### Default Options\nIn this example, the default options are used to do something with whatever. So if the `testing` file has the content `Testing` and the `123` file had the content `1 2 3`, the generated result would be `Testing, 1 2 3.`\n\n```js\ngrunt.initConfig({\n  sassquatch_test: {\n    options: {},\n    files: {\n      'dest/default_options': ['src/testing', 'src/123'],\n    },\n  },\n})\n```\n\n#### Custom Options\nIn this example, custom options are used to do something else with whatever else. So if the `testing` file has the content `Testing` and the `123` file had the content `1 2 3`, the generated result in this case would be `Testing: 1 2 3 !!!`\n\n```js\ngrunt.initConfig({\n  sassquatch_test: {\n    options: {\n      separator: ': ',\n      punctuation: ' !!!',\n    },\n    files: {\n      'dest/default_options': ['src/testing', 'src/123'],\n    },\n  },\n})\n```\n\n## Contributing\nIn lieu of a formal styleguide, take care to maintain the existing coding style. Add unit tests for any new or changed functionality. Lint and test your code using [Grunt](http://gruntjs.com/).\n\n## Release History\n_(Nothing yet)_\n","maintainers":[{"name":"thealscott","email":"thealscott@gmail.com"}],"time":{"modified":"2022-06-18T15:54:24.192Z","created":"2013-08-20T15:08:24.093Z","0.1.0":"2013-08-20T15:08:27.515Z","0.1.2":"2013-09-02T09:19:57.163Z","0.1.3":"2013-09-02T11:26:47.125Z","0.1.4":"2013-09-02T11:41:53.517Z","0.1.5":"2013-09-02T11:44:52.818Z","0.1.6":"2013-09-02T11:58:43.610Z","0.2.0":"2013-09-18T14:00:52.979Z","0.2.1":"2013-09-18T15:22:09.116Z","0.2.2":"2013-09-18T15:50:01.143Z","0.2.3":"2013-09-18T16:17:26.913Z","0.2.4":"2013-09-20T14:41:02.450Z","0.2.5":"2013-09-20T21:15:02.173Z","0.2.6":"2013-09-27T09:45:23.816Z","0.2.7":"2013-10-14T15:45:32.294Z","0.2.8":"2013-10-14T16:45:06.548Z","0.2.9":"2013-10-15T10:53:43.124Z"},"author":{"name":"Al Scott","email":"thealscott@gmail.com"},"repository":{"type":"git","url":"git://github.com/thealscott/sassquatch.git"}}