We moved the majority of docs for our projects (<a href="https://github.com/2600hz" rel="nofollow">https://github.com/2600hz</a>) to use mkdocs to build our doc sites (<a href="https://docs.2600hz.com/dev" rel="nofollow">https://docs.2600hz.com/dev</a> <a href="https://docs.2600hz.com/ui" rel="nofollow">https://docs.2600hz.com/ui</a> etc).<p>I have a simple script that receives github webhooks on PR merges to master that fetches the latest version of master and builds the site. So from PR merge to the docs site being updated is now seconds of time.<p>We also integrated building the doc sites into our CI process so PRs will fail if they would cause mkdocs to fail to build the site (borked yaml, make sure docs are included in the yaml, other things).<p>This has been a boon for our community of users and developers. Coupled with our AST parsers that look for code changes that require doc changes, we're getting better about alerting developers of the need to document something, and reviewers of the need if the developer forgot. Not a panacea but has significantly improved doc coverage for Kazoo which has a broad set of APIs available to different types of users.<p>Cheers to 1.0!