fix(app generator): clarify build target environment into build anatomy

README.md

@@ -169,9 +169,9 @@ Grunt can do more than just that; here's a recap of common grunt idioms:
 
 command           | description
 :--               |:--
-`grunt [default]` | does a production, non-debugging, all-parts, minified build plus artifacts;
-`grunt debug`     | does a testing, debugging, all-parts except documentation, as-is build;
-`grunt dev`       | does a local, debugging, all-parts except documentation, as-is build; <br>_(**Note that this variant doesn't exit**. Instead it'll keep a close watch on filesystem changes, selectively re-triggering part builds as needed)_
+`grunt [default]` | does a for-production, non-debugging, all-parts, minified build plus artifacts;
+`grunt debug`     | does a for-testing, debugging, all-parts except documentation, as-is build;
+`grunt dev`       | does a for-local, debugging, all-parts except documentation, as-is build; <br>_(**Note that this variant doesn't exit**. Instead it'll keep a close watch on filesystem changes, selectively re-triggering part builds as needed)_
 `grunt doc`       | will build just the code documentation;
 `grunt lint`      | will just lint your code;
 `grunt test`      | will run your test suite;

generators/app/index.js

@@ -630,13 +630,13 @@ var AppGenerator = generators.Base.extend(
 
                 +   '\n'
                 +   chalk.bold( '  * ' + chalk.yellow( 'grunt ' + chalk.cyan( '[' ) + 'default' + chalk.cyan( ']' ) + '     ' ))
-                +   '- does a production, non-debugging, all-parts, minified build plus artifacts;\n'
+                +   '- does a for-production, non-debugging, all-parts, minified build plus artifacts;\n'
 
                 +   chalk.bold( '  * ' + chalk.yellow( 'grunt debug         ' ))
-                +   '- does a testing, debugging, all-parts except documentation, as-is build;\n'
+                +   '- does a for-testing, debugging, all-parts except documentation, as-is build;\n'
 
                 +   chalk.bold( '  * ' + chalk.yellow( 'grunt dev           ' ))
-                +   '- does a local, debugging, all-parts except documentation, as-is build;\n'
+                +   '- does a for-local, debugging, all-parts except documentation, as-is build;\n'
                 +   '                          (' + chalk.bold( 'Note that this variant doesn\'t exit.' ) + ' Instead, it\'ll keep a close watch on\n'
                 +   '                          filesystem changes, selectively re-triggering part builds as needed)\n'
 

generators/app/templates/@Gruntfile.coffee

@@ -22,6 +22,12 @@
 ##        * The application
 ##        * The application's code documentation
 ##
+##    * The build's target environment:
+##        * local
+##        * testing
+##        * acceptance
+##        * production
+##
 ##    * The build parts:
 ##        * app<@ if ( i18n ) { @>
 ##            * i18n<@ } @>
@@ -70,6 +76,8 @@
 ##        * A debugging build implies as-is packing.
 ##        * Minified packing implies a non-debugging build.
 ##
+##    * A for-acceptance targetted build is identical to a for-production build.
+##
 ##    * The build's artifacts are an all-or-nothing deal, currently.
 ##
 ##    * The build parts can be processed seperately, but some depend on others:
@@ -107,9 +115,9 @@
 ##
 ##  Finally, this is how the main grunt commandline tasks are mapped to all of the above:
 ##
-##      * grunt [default]   - does a production, non-debugging, all-parts, minified build plus artifacts;
-##      * grunt debug       - does a testing, debugging, all-parts except documentation, as-is build;
-##      * grunt dev         - does a local, debugging, all-parts except documentation, as-is build;
+##      * grunt [default]   - does a for-production, non-debugging, all-parts, minified build plus artifacts;
+##      * grunt debug       - does a for-testing, debugging, all-parts except documentation, as-is build;
+##      * grunt dev         - does a for-local, debugging, all-parts except documentation, as-is build;
 ##                            (Note that this variant doesn't exit. Instead, it'll keep a close watch on
 ##                            filesystem changes, selectively re-triggering part builds as needed)
 ##

generators/app/templates/@README.md

@@ -55,9 +55,9 @@ If you would like something different, here's a recap of most common grunt idiom
 
 command           | description
 :--               |:--
-`grunt [default]` | does a production, non-debugging, all-parts, minified build plus artifacts;
-`grunt debug`     | does a testing, debugging, all-parts except documentation, as-is build;
-`grunt dev`       | does a local, debugging, all-parts except documentation, as-is build; <br>_(**Note that this variant doesn't exit**. Instead it'll keep a close watch on filesystem changes, selectively re-triggering part builds as needed)_
+`grunt [default]` | does a for-production, non-debugging, all-parts, minified build plus artifacts;
+`grunt debug`     | does a for-testing, debugging, all-parts except documentation, as-is build;
+`grunt dev`       | does a for-local, debugging, all-parts except documentation, as-is build; <br>_(**Note that this variant doesn't exit**. Instead it'll keep a close watch on filesystem changes, selectively re-triggering part builds as needed)_
 `grunt doc`       | will build just the code documentation;
 `grunt lint`      | will just lint your code;
 `grunt test`      | will run your test suite;

generators/demo/templates/src/views/buildscript.hbs

@@ -8,7 +8,7 @@
         <h3>Default</h3>
         <code>grunt [default]</code>
     </div>
-    <p>This task does a production, non-debugging, all-parts, minified build, plus deployable artifacts. It will run the following tasks:</p>
+    <p>This task does a for-production, non-debugging, all-parts, minified build, plus deployable artifacts. It will run the following tasks:</p>
     <ul>
         <li>
             <a href="https://github.com/gruntjs/grunt-contrib-clean#readme">Clean</a>: