Updated Moving to NPM and Grunt (markdown)

Moving-to-NPM-and-Grunt.md

@@ -1,5 +1,15 @@
 This is a collection of information about, and hopefully decisions for, a move away from pake/build.py to nodejs for the cli development tool chain.
 
+## Approach
+
+The following is based on the assumption that there is general agreement to move the cli development tools to NodeJS, at least where possible.  
+
+The primary tool for managing dependencies and invoking various development tasks will be `npm`, which is included with all recent NodeJS versions.  
+
+The actual development tasks will be run via [Grunt](gruntjs.com).  Grunt requires a grunt-cli module to be installed.  To avoid another dependency the user has to install, it can be installed as a direct dependency via npm and various grunt tasks can be invoked by npm via scripts.  This will keep some consistency in the command line descriptions (npm install, npm test, npm build etc) and keep the prerequisites to a minimum.
+
+## Notes and Information
+
 ### Related issues and PRs
 
 * Plovr-free build (@twpayne) [#456](https://github.com/openlayers/ol3/pull/456)
@@ -23,3 +33,7 @@ These things will need to be downloaded:
 * [http://closure-linter.googlecode.com/files/closure_linter-latest.tar.gz](http://closure-linter.googlecode.com/files/closure_linter-latest.tar.gz)
 * [http://dl.google.com/closure-compiler/compiler-latest.zip](http://dl.google.com/closure-compiler/compiler-latest.zip)
 * [http://closure-library.googlecode.com/files/closure-library-20130212-95c19e7f0f5f.zip](http://closure-library.googlecode.com/files/closure-library-20130212-95c19e7f0f5f.zip) - **or** `git clone https://code.google.com/p/closure-library/ build/closure-library`
+
+
+
+###