Toshio Kuratomi
12e1884352
Merge pull request #9755 from armetiz/docs_format
Add missing connection and header |
10 years ago | |
---|---|---|
.. | ||
_static | multiple spelling error changes | 11 years ago |
_themes/srtd | Add ebook link to docsite. | 10 years ago |
js/ansible |
…
|
|
man |
…
|
|
rst | Merge pull request #9755 from armetiz/docs_format | 10 years ago |
.gitignore |
…
|
|
.nojekyll |
…
|
|
Makefile | Updating the module formatter to deal with the new repo structure. | 10 years ago |
README.md | AnsibleWorks -> Ansible | 11 years ago |
build-site.py | Remove unused if/else clause, since it doesn't change anything | 10 years ago |
conf.py | AnsibleWorks -> Ansible | 11 years ago |
favicon.ico | Retinafy favicon.ico | 11 years ago |
modules.js |
…
|
|
variables.dot | Add the start of a graphviz doc to illustrate variable precedence graphically. | 11 years ago |
README.md
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 Michael 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"