docs(tools): added overview of tools used
chore(index.html): added social media meta tags
Spelling correction.
Karma runner port to 9101, fixing watch issues

Credit to @helmi03.

Tested on:
 - MacOS 10.7.5 (Karma 0.8.5, NodeJS 0.10.4)
 - Ubuntu 12.04 (Karma 0.8.5, NodeJS 0.10.10)
 - Arch Linux (Karma 0.8.5, NodeJS 0.10.10)

Fixes #37. Fixes #20.
Merge pull request #45 from shanestillwell/master

docs(README): fixes minor spelling error
Merge pull request #32 from joshdmiller/tools-readme

docs(tools): added overview of tools used
chore(*): migrated local html2js to npm

Closes #26.
chore(*): removed `dist/` refs from Gruntfile

Using instead, naturally, the `distdir` config variable.
chore(*): renamed src/components to src/common
feat(build): split build into build+compile

To increase build speed during iterative development, the build task
has been split into two tasks: build and compile. The build task
performs only the minimum amount of work necessary to test and run your
app; the compile task does all the production-ready stuff like
minification and concatenation.

The default grunt task now performs a build and a compile.

A large chunk of this feature comes from @ajoslin. Thanks!!!
feat(*): switched to ui-router for state mgmt

Instead of $routeProvider, ui-router's $stateProvider is now used for
managing application states and routes. ui-router is *much* more
powerful and for large applications will provide many benefits that the
boilerplate does not explore in vitro.

Closes #4.
feat(karma): karma config managed automatically

Prior to this commit, any vendor code changes would require manually
adding them to the karma config file. Now, these changes are managed
automatically based on the settings in the Gruntfile.

The `karma/karma-unit.tpl.js` file is a Grunt template that the build
process uses to generate a config file for use during testing. As a
result, the `karma/karma-unit.js` file has been removed.

Unfortunately, there is no easy way to dynamically reload the karma
config file during a watch, so when new vendor files are added to the
build variables in the Gruntfile, we need to restart the watch.

Closes #47.
chore(*): removed node 0.8 from CI
fix(bower): renamed ui-router to angular-ui-router
feat(coffee): CoffeeScript support

CoffeeScript files are now supported out of the box. Any coffeescript
files in `src/` that match `*.coffee` will be linted and included in
the tests and builds.

Just to demo that it works, the `titleService` has been migrated to
CoffeeScript.
fix(*): ui.route from bower is out of date

v0.0.3 is not yet available in Bower but v0.0.2 does not support
ui-router. This commit switches temporarily to a static version of
ui.route.
feat(*): Added changelog generation

Running `grunt changelog` will now create a changelog of the revisions
from hash-to-hash.

Closes #28.
feat(release): Added grunt-bump to ease releasing
chore(bootstrap): Updated to Twitter Bootstrap 2.3.2
chore(fontawesome): Updated Font Awesome to v3.2.1

Because manual management of Font Awesome files is a pain, this now
runs the CDN version. With a little work, we can get this working with
the Bower version, but because there are assets it becomes more of a
challenge.