019d078a5a
We have some common code used by several docs scripts. Migrate that into the build-only shared code repository. * Move lib/ansible/utils/_build_helpers.py to the directory for common build code * Migrate docs/bin/dump_config.py to a build-ansible subcommand * Migrate dump_keywords to the build-ansible framework * Make the script more maintainable by using functions and good variable names * Port to Python3 idioms * Fix bug so that private attributes will be undocumented * Move generate_man to a build-ansible subcommand * Port plugin_formatter to a build-ansible subcommand * Rework command_plugins so that docs scripts can target Python-3.4+ and releng-only subcommands can use more recent versions of Python. The architecture is now that command_plugins/* need to be importable on Python-3.4. The init_parsers() method needs to run on Python-3.4. But the main() method can utilize features of more recent Python as long as it fits within those parameters. * Update docs build requirements Port the plugin_formatter to build-ansible framework |
||
---|---|---|
.. | ||
_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.