Some boilerplate code for static site generation

1. Clone this repository git clone https://github.com/bdadam/static-site-boilerplate
2. Install node dependencies npm install
3. Install bower dependencies bower install
4. Simply run grunt build to see that everything works

You can run grunt dev while developing. This starts a new web server on port 3000 (http://localhost:3000/). After every change the affected files are regenerated.

1. grunt - default task: build everything and then whatches for changes and regenerated the affected files
2. grunt build - builds everything
3. grunt clean - cleanup
4. grunt assemble - generates html with Assemble
5. grunt less - generated css file(s) from less files
6. grunt sass - generated css file(s) from scss files
7. grunt uncss - removes unnecessary css rules
8. grunt requirejs - generates JavaScript files with RequireJS (or Almond)
9. grunt webpack - generates JavaScript files with WebPack - uses CommonJS format
10. grunt hashres - computes hash code for static resources (aka cachebusting)
11. grunt connect - starts web server and stops it automatically when all the other tasks finished
12. grunt watch - checks for file modifications and runs the appropriate tasks
13. grunt dev - runs a complete build and then waits for modifications (watch)

1. grunt karma:dist - runs JS unit tests in Chrome, Firefox, IE and PhantomJS
2. grunt karma:dev - runs JS unit tests in PhantomJS only

All tasks accept a --dev flag, which disables many optimizations (minification), enables source maps, etc. This should only be used during development.

1. Static site generation with Assemble
2. Generating and minifying a single CSS file with Less
3. Generating and minifying a single JavaScript file with RequireJS or WebPack
4. Linting JS files with ESlint
5. Unit testing for JavaScript with Karma
6. Generating hash (cache buster) for JS and CSS files
7. Automatic regeneration and Liverload during development

• bdadam.com [complete source code]
• the-game-of-love.com [complete source code]