Easier gh-pages deploy

[sole]

Is there a reason why we're not using something like the gh-pages utility instead of the long amount of commands described in the README? As in here:

gh-pages -d dist

this creates a new commit in the gh-pages branch with the content of the dist directory.

I can send a PR with this new package.json command if that sounds OK

[callahad]

Maybe I'm doing things wrong, but the dist folder only includes the generated javascript, since we re-use everything else (css, webfonts) as-is.

What I want is a structure that:

1. Keeps generated artifacts out of master
2. Works seamlessly with Webpack's hot module reloading

If the gh-pages NPM package is a better way to get us there, please do submit a PR. ;) Whatever we do should be sufficiently foolproof so that you only push things to gh-pages that have also made it into master on github.