Devise a mechanism for versioning docs

[oubiwann]

Part of the Versioning Docs Epic

[oubiwann]

Currently looking at the Github documentation site. I posted the following comment in another ticket, and it should be here too:

I've been looking at projects like Read The Docs (Sphinx-based, uses ReST instead of Markdown ... not good for us, but pretty good overall API docs site features) and I haven't yet found anything that really grabs me.

The Github Documentation site is actually the most impressive I've seen so far:

• https://developer.github.com/v3/

They blogged about how they're now supporting versioned docs (which we will need) with the latest Jekyll and the release of their new site: How GitHub uses GitHub to document GitHub. They've open-sourced their site here:

• https://github.com/github/developer.github.com

I'm going to try to get a copy of it running and see how we might adapt it for LFE. Our stuff is already in markdown (all the sites as well as all the Gitbooks), and we use Jekyll already for the docs site and the blog, so this might be the best place to start for now ...

[oubiwann]

The Github docs also have their enterprise offering versioned:

• https://developer.github.com/enterprise/2.1/
• https://developer.github.com/enterprise/2.0/
• https://developer.github.com/enterprise/11.10.340/

[oubiwann]

For the past year I've been using a series of make targets for this using Slate and (more recently) lodox-generated API docs. That will work just fine for the LFE docs site.