3f784caed1
* Change formatting of the network/user_guide tables * Tables had hardcoded line breaks to workaround a bug in the read-the-docs theme. Change those so that they now flow according to the browser size. * Also switch away from grid tables to the simpler to create and read simple tables * Changes to table stylesheet * valign all content, not just the first column. This becomes important with more than two columns * Set the font-weight to the first <p> element inside of the first column. This allows us to simplify the first column when everything there is the attribute name * Change platform_index footnote from numbered to dagger symbol The footnote notation was very odd to read. Try using a symbol for the footnote instead of a number to see if that will clarify it. We can't manually specify symbolled footnotes, though, so we have to emulate a footnote with an internal link. This loses the backref to each place that the footnote was used but since that was the portion which was hard to read, perhaps that's for the best. |
||
|---|---|---|
| .. | ||
| _extensions | ||
| _static | ||
| _themes/sphinx_rtd_theme | ||
| js/ansible | ||
| rst | ||
| .gitignore | ||
| .nojekyll | ||
| jinja2-2.9.7.inv | ||
| keyword_desc.yml | ||
| Makefile | ||
| Makefile.sphinx | ||
| modules.js | ||
| python2-2.7.13.inv | ||
| python3-3.6.2.inv | ||
| README.md | ||
| requirements.txt | ||
| variables.dot | ||
Homepage and Documentation Source for Ansible
This project hosts the source behind docs.ansible.com
Contributions to the documentation are welcome. To make changes, submit a pull request that changes the reStructuredText files in the rst/ directory only, and the core team can do a docs build and push the static files.
If you wish to verify output from the markup such as link references, you may install sphinx and build the documentation by running make webdocs from the ansible/docs/docsite directory.
To include module documentation you'll need to run make webdocs at the top level of the repository. The generated html files are in docsite/htmlout/.
To limit module documentation building to a specific module, run MODULES=NAME make webdocs instead. This should make testing module documentation syntax much faster. Instead of a single module, you can also specify a comma-separated list of modules. In order to skip building documentation for all modules, specify non-existing module name, for example MODULES=none make webdocs.
If you do not want to learn the reStructuredText format, you can also file issues about documentation problems on the Ansible GitHub project.
Note that module documentation can actually be generated from a DOCUMENTATION docstring in the modules directory, so corrections to modules written as such need to be made in the module source, rather than in docsite source.
To install sphinx and the required theme, install pip and then pip install sphinx sphinx_rtd_theme
HEADERS
RST allows for arbitrary hierarchy for the headers, it will 'learn on the fly'. We also want a standard that all our documents can follow:
##########################
# with overline, for parts
##########################
*****************************
* with overline, for chapters
*****************************
=, for sections
===============
-, for subsections
------------------
^, for sub-subsections
^^^^^^^^^^^^^^^^^^^^^
", for paragraphs
"""""""""""""""""
We do have pages littered with ```````` headers, but those should be removed for one of the above.