Add continuous integration tooling

[alukach]

After a successful build, Travis will run .travis/deploy-to-gh-pages.sh. This script will check to see that the build took place on the RELEASE_BRANCH (configured as a variable within the Travis configuration file), and if it has grunt gh-pages is ran, copying the repo (including ignored files/dirs, excluding dot files/dirs) to the gh-pages branch. This requires that Travis have a [Github OAuth token] added as a variable (this is done as a hidden variable on the Travis website, rather than within the config file). I've gone ahead and set Travis up with a token.

Currently, RELEASE_BRANCH is set as master, meaning any commits to master will be deployed. If this proves to be a source of error, we can adjust as necessary.

This addresses #38

[mapsam]

@alukach this is really terrific. So many freaking things happening I can't keep my head straight but I'm trusting you 100% on this one. Sounds like we should wait until @aaronr finishes up #45 before this merges in. But otherwise 👍

[alukach]

@svmatthews Do you think so? I feel like this is independent of #45 (or maybe a requirement for #45). This has functionality on its own. I'm also a fan of keeping as few PRs open at any given time, helps make merges a bit easier. Open to merging it?

[mapsam]

👍