docs(workflow): workflow about website proccess and build tools

Author: nmccready

doc/workflow/build-tool/grunt.md

@@ -0,0 +1,4 @@
+Grunt Documentation
+===================
+
+Starting place for documentation specific to this projects grunt build process.

doc/workflow/build-tool/proposed-next-gen-build-framework.md

@@ -0,0 +1,14 @@
+Next-Gen Build Tool Framework
+=============================
+
+Currently grunt is the de-facto way of doing things on this project. However, grunt is quite outdated when compared to
+gulp, brunch.io, and etc.
+
+Point is if someone has a stick up their butt to do this we should migrate this project targeting angular 1.X before moving to or
+supporting angular 2.X .
+
+
+@nmccready is quite familiar with grunt, gulpjs, and brunch.io . But he feels that the project is not quite worth the effort in migrating yet.
+
+
+Therefore if someone else who has experience in gulp, or brunch.io and has a fire in their belly to take this on for fun please raide your hand. :)

doc/workflow/website.md

@@ -0,0 +1,25 @@
+Website Workflow Documentation
+==============================
+
+The branches *master* and *gh-pages* are now one in the same except that gh-pages has bower_components (--force) saved to the branch.
+
+Reasoning:
+
+- less confusion where and how gh-pages are deployed
+- code and docs exist in the same branch. There are **NO** **Excuses** to not update documentation now with things being in the same place.
+- documentation is now under the same version control and pull process and history of this libraries releases
+
+
+To run just the website via grunt do:
+
+- `grunt website`
+
+- Open browser to [localhost:8888](http://localhost:8888).
+
+- When done: PR or push code up.
+
+- merge master into gh-pages (via PR acceptance or manual git cli merge)
+
+- If there are new bower_components or new bower dependencies `bower install` and then `git add -A bower_components --force`.
+
+- Finally PR or push up modified bower_components or include in previous PR above