Enable auto-deploy to gh-pages

[pjackson28]

Currently this is a manual process and would reduce effort if Travis could deploy to gh-pages automatically after each merge to master.

Instructions can be found here: https://docs.travis-ci.com/user/deployment/pages/

[nschonni]

Is there a need to compile and push, or can the gh-pages branch just be changed to master in the settings?

[pjackson28]

There is #87 (Provide single page view) and #93 (Provide other views?) which could mean other pages would need to be built (since I haven't found a way to do this through Jekyll/Liquid). Is it possible to do these automatically without a build and push or do we need to keep gh-pages to reasonably achieve this?

[nschonni]

The SPA might be possible my just creating a page/layout that globs in all the subpages. Never tried it though

[pjackson28]

The challenge will be that the headers in the included content will need to be incremented when combined in one page and I haven't yet found a way to do that through Jekyll without pre-processing of some sort (such as the build making a copy of the .md files, replacing "##" with "###", then the Jekyll includes using the modified copies when building the single page).