Init sass bootstrap v2
User is prompted whether to include each remotes (except from h5bp base one), unless the init task is triggered with a "template" with include_remotename (ex: include_bootstrap) set to 'y'. * js plugins are pulled in from bootstrap repo * sass files are pulled from compass_twitter_bootstrap * js files are copied into root/js/vendor/*, sass goes in root/css/sass. * a default Gruntfile is copied from tasks/init/yeoman/Gruntfile.js * the --template <name> option is used to load a pre-defined template Then the actual grunt file copy happens with what is in root folder. docs/init.md includes some notes and a start of developer documentation The --template <name> option is used to load a pre-defined template, a set of default answers. They are different from grunt's usual default prompt answers (where the prompt still happens, but with a different default value)
Make .coffee files in the /js folder automagically compile
…asks are run #22
Remove everything that should be in a devs own global gitignore
…decide we don't need it.
Tests for the cli tool
* this uses the yeoman binary script to init a new default project * then a given task (or set of tasks) is triggered * assertions then compare files in .test/ with what is expected in test/fixtures/*/
Also added a templates/ folder with a default.json file. This introduces the notion of templates. The `--noprompt` option may be renamed to `--template <name>`, the semantic and the way the init task work will most likely vary and going to be improved.
…minor expansion to readme.