66fb7fd9de
At the moment Ansible prefers yes/no for module booleans, however booleans in playbooks are still using True/False, rather than yes/no. This changes modifies boolean uses in playbooks (and man pages) to favor yes/no rather than True/False. This change includes: - Adaptation of documentation and examples to favor yes/no - Modification to manpage output to favor yes/no (the docsite output already favors yes/no) |
||
|---|---|---|
| .. | ||
| _static | ||
| _themes/bootstrap | ||
| man | ||
| rst | ||
| .gitignore | ||
| .nojekyll | ||
| ansible-logo.png | ||
| ansible_arch.jpg | ||
| ansible_arch2.jpg | ||
| build-site.py | ||
| conf.py | ||
| DOCUMENTATION.yaml | ||
| github.png | ||
| Makefile | ||
| README.md | ||
Homepage and documentation source for the Ansible
This project hosts the source behind ansible.cc/docs
Contributions to the documentation are welcome. To make changes, submit a pull request that changes the restructured text files in the "rst/" directory only, and Michael can do a docs build and push the static files.
If you do not want to learn RST format (ReStructured Text), you can also file issues on the documentation project.
Note that module documentation can actually be generated from a DOCUMENTATION docstring in the modules directory, so corrections to modules written as much need to be made in the main project in the module source, rather than in the documentation for the module.
Author
Michael DeHaan -- michael.dehaan@gmail.com