ansible/docsite
John R Barker 5cdc2b5738 repomerge.rst (#18756)
* repomerge.rst

* Past tense

* Update repomerge.rst

* Readonly repos, not deleted

* Make ansible/ansible a link

* Links

* maturity of the module's parameters

* PR & Issue mover is done - don't document as future

* Update repomerge.rst

* Typo
2016-12-08 11:35:19 -05:00
..
_static Fix and create code-smell test for line endings. 2016-11-03 14:58:11 -07:00
_themes/srtd Reinstating mysteriously truncated hubspot analytics. 2016-10-10 13:10:55 -07:00
js/ansible
man
rst repomerge.rst (#18756) 2016-12-08 11:35:19 -05:00
rst_common Mocate ansible_ssh_changes into a common directory 2016-05-24 11:37:04 -07:00
.gitignore
.nojekyll
build-site.py
conf.py updated devel to 2.3 (#17884) 2016-10-03 15:08:19 -04:00
favicon.ico
Makefile Clean up shebangs for various files. 2016-11-02 17:00:27 -07:00
modules.js
README.md
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 viewdocs from the ansible/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/.

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"