Add config option to add custom concat tasks (#87)

This also includes docs, using xtend for concat.

CHANGELOG.md

@@ -3,6 +3,7 @@
 ### HEAD
 
 * Use load-grunt-tasks instead of matchdep
+* Add config option to add custom concat tasks (#87)
 * Clean up Karma configuration and make coverage working with new version
 * Add `grunt/tasks` folder for own tasks
 * Add directory `grunt/plugins` to include plugins for Grunt config

docs/TOC.md

@@ -13,6 +13,7 @@
 * [JavaScript](js.md) — A guide to the default JavaScript with RequireJS.
 * [Build process](grunt.md) - A detailed guide to the GruntJS configs.
 * [Testing](tests.md) — How to test your code with INIT.
+* [Custom File Concatenation](concat.md) — How to concatenate your files with INIT.
 * [Some other things](misc.md).
 
 ## Extend INIT

docs/concat.md

@@ -0,0 +1,29 @@
+[« back to Table of Contents](TOC.md)
+
+# Concatenate files with INIT
+
+INIT supports concatenation out of the box through
+[`grunt-contrib-concat`](https://github.com/gruntjs/grunt-contrib-concat).
+This is used by default for concatenating your template partials into a working
+prototype / HTML page.
+
+## Add custom concat tasks
+
+You can add custom tasks to concatenate files. Add your custom concatenations to
+the config object in `config.js`.
+
+A sample custom config object could look like:
+
+	concat: {
+		concatFirst: {
+			src: [
+				'js/part1.js',
+				'js/part2.js'
+			],
+			dest: 'concatenatedfile.js'
+		}
+	},
+
+The `src` key references your partials that you want to concatenate. The `dest`
+key describes the relative path to the result. The path is set relative from
+INIT’s root.

grunt/options/concat.js

@@ -3,6 +3,8 @@
  */
 'use strict';
 
+var xtend = require('xtend');
 var pages = require('../../pages');
+var config = require('../config');
 
-module.exports = pages;
+module.exports = xtend(pages, config.concat || {});