# Automate Documentation

**URL:** <https://forum.ansible.com/t/automate-documentation/25424>\
**Category:** Ansible Developer\
**Created:** [September 6, 2017, 10:18pm UTC](https://forum.ansible.com/t/automate-documentation/25424 "2017-09-06T22:18:19Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Dave\_Jarvis](https://avatars.discourse-cdn.com/v4/letter/d/d26b3c/32.png) [@Dave\_Jarvis](https://forum.ansible.com/u/Dave_Jarvis)\
**Post date:** [September 6, 2017, 10:18pm UTC](https://forum.ansible.com/t/automate-documentation/25424/1 "2017-09-06T22:18:19Z")

</div>

From [http://docs.ansible.com/ansible/latest/intro.html](http://docs.ansible.com/ansible/latest/intro.html), the page footer reads:

> Ansible docs are generated from [GitHub sources](https://github.com/ansible/ansible) using [Sphinx](http://sphinx-doc.org/) using a theme provided by [Read the Docs](http://readthedocs.org/).

Ansible’s [integration page](https://www.ansible.com/integrations-overview) doesn’t include documentation as an integration point. In the attached diagram, Pandoc is equivalent to Sphinx, but Sphinx only parses [one Markdown flavour](http://www.sphinx-doc.org/en/stable/markdown.html); whereas, [Pandoc](http://pandoc.org/MANUAL.html) imports and exports many formats.

If Ansible could automate documentation, though I’m not sure if it is possible, then the footers of Ansible’s documentation could state, **_Ansible docs were automatically generated and published using Ansible and Sphinx_**.

Kind regards,  
Dave

> **(attachments)**
>
> ![architecture.png](https://us1.discourse-cdn.com/ansible/original/2X/1/1c0f5ff0868cd0e8e17aad5ed0307d90cc63d3b6.png)