antsibull-docs VS docsite

antsibull-docs 2.6.0 has been released with a fix for EXAMPLES parsing and error message improvements.

More than two years ago the Ansible Docs Working Group started discussing the use of semantic markup for Ansible plugin/module documentation. This resulted in a specification that has been implemented as proofs of concept both for ansible-doc and the validate-modules sanity test, as well as for antsibull-docs. From the docs perspective this will improve plugin, module, and now also role documentation a lot, and in particular separate markup from content. (Right now you have to use C(...) and I(...) for values and option names, which stand for 'code-style' and 'italics'.)

antsibull-core 2.0.0a1 has been released. This major release drops support for Python 3.6, 3.7, and 3.8 and deprecates some compatability code (full changelog). It also includes a new feature needed by antsibull-build. antsibull-core houses shared code used by antsibull-build and antsibull-docs. If you use either of these tools, please help us test this new release. It can be installed with pip install -U antsibull-core==2.0.0a1. Note that you'll need the latest version of antsibull and antsibull-docs to use antsibull-core 2.0.0a1.

antsibull-docs 1.3.0 (changelog) has been released with several new features for the docs build! The most important changes are that now booleans are rendered as true and false instead of yes and no (https://github.com/ansible-community/community-topics/issues/116), and that a proper parser is used for Ansible markup, which properly escapes for example backticks instead of simply inserting them into the RST files (https://github.com/ansible-community/antsibull-docs/issues/21).

If you are using the antsibull-docs or antsibull-lint collection-docs CLI command from the antsibull package, consider switching to using the new antsibull-docs 1.0.0 package instead! It is more stable and comes with less potential baggage to carry around.

Before we add the redirect we'd like to get your feedback. Please leave a comment on the pull request or head over to the docs channel on Matrix and let us know your thoughts.

Hopefully you've noticed that the "docs.ansible.com" landing page has a different navigation. We've updated it to focus on user journeys so users can find support from Ansible docs more efficiently. There is still lots to do and we'd love to hear from you! Do you have ideas about new user journeys? Do you see any content gaps? Are there things you'd just like to change? Send a PR or open an issue in the ansible/docsite repo and help us keep building better content journeys for the community.

We've just refreshed the layout on docs.ansible.com to include quick and easy links for most visited doc pages. You can find the new "Quicklinks" section on the index, user, developer, and maintainer pages. We want to hear from you, especially if you have a killer suggestion for a quicklink, so open an issue in the ansible/docsite repo.

You might have noticed that "docs.ansible.com" has a different layout. That's because we've revamped it to focus on user journeys so that users find what they need from Ansible docs more efficiently. There is still lots to do and we'd love to hear from you! Do you have ideas about new user journeys? Do you see anything missing from the new docsite? Are there things you'd just like to change? Send a PR or open an issue in the ansible/docsite repo and help us make it even better.

Come join us and help build a new docsite! The community team has been working to update the Ansible documentation landing page based on a set of user journeys. Right now we're working on a prototype docsite to improve the navigation and user experience.

The community engineering team has put together a first set of user journeys for Ansible docsite personas and would like your feedback. You can find the user journeys in GitHub.

The ansible/docsite repo is now public, giving the Ansible community full access to all the html and navigation assets that go into docs.ansible.com. Fork the repo and start hacking.