Awesome work Joster... always great to see this technique in action.
To highlight an offering from Asciidoctor, we've used jekyll, jekyll-asciidoctor, asciidoctor and Travis to facilitate on the fly editing and rendering of Asciidoctor content via Travis CI, specifically targeting documentation centric websites. The end result is automatically rendered content (Travis watches for changes, renders and publishes the site) deployed any time you push to master. Also, this means that you can edit the content directly on Github via a web browser. I love the ability to edit content quickly in the browser or accept a PR and have content automatically updated.
We put together a quickstart project recently to bootstrap this functionality called JAQ:
https://github.com/asciidoctor/jekyll-asciidoc-quickstartThis project includes the default asciidoctor css along with foundation css to encourage some good design behavior.
I based both of my most popular project documentation sites off of JAQ:
ParcelerTransfuseHere are the source projects:
https://github.com/johncarl81/parceler-sitehttps://github.com/johncarl81/transfuse-siteI'm curious if this technique would also work for your content. If anything, maybe having the content published automatically via Travis may be of benefit. Food for thought.
John