Hard at work moving the unofficial devRant api documentation to GitBook.

Note: The previous link provided will stop working in due course.

18 commits later, the unofficial documentation has been ported over to GitBook.

The documentation now lives in a private repo on GitHub which is hooked up to a CI tool to build the book when a commit is pushed.

This will make maintaining the documentation much easier and also allow for collaboration which was previously not possible.

Because this documentation contains some endpoints some of you might not even know about, access is provided on a invite-only basis which is controlled by @dfox.

For new requests, contact @dfox with your name and what you are planning to build.

If you have already created something with the API email me at support@nblackburn.uk with your name and a link and I will send you a invite.

Recently I've been tasked with setting up of a small /mid-size infrastructure and I've been documenting things like infrastructure design, network configuration all the way to playbooks and cluster configuration.
Since I just started with this, until now I have been doing this in a Google doc / some spread around markdown files. I would like to have a better way of having this documentation hosted internally..
I have been playing around with local installations of rtd, gitbook and mkdocs. So far, I've liked the simplicity and customizability of mkdocs.

Any other options before I commit myself to mkdocs?

Ever since i added cloudflare to my site i get this error. everything exploded and the site no longer loads (i had to set cloudflare so i can use gitbook docs so im forced to use cloudflare even tho i dont want to use it). Anyone had this problem before and knows a fix?