New build process

[hdngr]

Re-scaffolds application and uses yeoman (bower, grunt) to manage dependencies and build process.

gh-pages task builds site into gh-pages branch automatically. See the gh-pages branch on this fork for an example of how this works.

TODO

• Build vendor and main css instead of using cdns
• Use grunt for dev server with reloader and watch tasks

[nawroth]

While it adds a bit of complexity, I think this is the way we have to go. Loading less files to bring the depenencies in is good. It's still possible to check out the gh-pages branch to try out changes without using the build tools -- let's add that to the readme (which should really be AsciiDoc!)

The TODO items above are the ones I was going to to ask for ;-)

It seems to work well: http://hustonhedinger.github.io/graphgist/

The different versions of the CodeMirror dependecies are most likely just a mistake by me. Should be updated to 4.5.0 now.

The license of the project should be Apache 2.

Why move the javascripts to the end of the body instead of in the head? We don't optimze for the HTML to show up fast, we optimize for starting to load the content using JS as fast as possible. So to me it makes more sense to me to load the JS in the head then.

WDYT? @hustonhedinger @jexp

[hdngr]

• @nawroth OK great - I will likely get to the TODOs this weekend.
• Re: http://hustonhedinger.github.io/graphgist/ - lol, I did not even think to check my gh-pages - I just ran a local static server and assumed it worked, way to think out side the box! ;-)
• Re loading of Githubissues.
• Githubissues is a development platform for aggregating issues.