# CfgMgmtCamp 2026 discussion (6/12): Collection documentation on Ansible Galaxy is incomplete and partially confusing **URL:** \ **Category:** Project Discussions\ **Tags:** cfgmgmgtcamp, documentation, galaxy-ng\ **Created:** [February 7, 2026, 9:00pm UTC](https://forum.ansible.com/t/cfgmgmtcamp-2026-discussion-6-12-collection-documentation-on-ansible-galaxy-is-incomplete-and-partially-confusing/45293 "2026-02-07T21:00:18Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![felixfontein](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/felixfontein/32/7530_2.png) [@felixfontein](https://forum.ansible.com/u/felixfontein)\ **Post date:** [February 7, 2026, 9:00pm UTC](https://forum.ansible.com/t/cfgmgmtcamp-2026-discussion-6-12-collection-documentation-on-ansible-galaxy-is-incomplete-and-partially-confusing/45293/1 "2026-02-07T21:00:18Z")
# As a user **Collection documentation on Ansible Galaxy is incomplete and partially confusing** # Latest developments None that I know of. This wasn’t discussed at CfgMgmtCamp 2026. # Original text There are some things about Ansible Galaxy’s collection documentation viewer that aren’t good: - Documentation of roles (from argument spec, similar than for modules and plugins) is missing (for example, see the [community.sops.install “documentation” on Galaxy](https://galaxy.ansible.com/ui/repo/published/community/sops/content/role/install/)). - Modules or plugins using doc fragments from other collections [are not shown at all](https://forum.ansible.com/t/3496). (Doc fragments from ansible-core or from the same collection work.) - [The Documentation tab](https://galaxy.ansible.com/ui/repo/published/community/general/docs/) is grouped by modules / plugins, and “plugins” contains things like doc fragments and module utils. This is pretty much **useless**. ---
**Author:** ![russoz](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/russoz/32/127_2.png) [@russoz](https://forum.ansible.com/u/russoz)\ **Post date:** [February 12, 2026, 9:48pm UTC](https://forum.ansible.com/t/cfgmgmtcamp-2026-discussion-6-12-collection-documentation-on-ansible-galaxy-is-incomplete-and-partially-confusing/45293/2 "2026-02-12T21:48:27Z")
The extra docs are also not rendered in Galaxy. In community.openwrt, like many other collections not in the ACP, those docs are being published directly to Github. Being a new collection, a lot of things are changing quickly, including those extra docs, and we currently have no trivial way of publishing multiple versions of those docs. It would be wonderful to have that in Galaxy. The other option we have been considering is publishing directly to [readthedocs.io](http://readthedocs.io). ---
**Author:** ![gundalow](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/gundalow/32/99_2.png) [@gundalow](https://forum.ansible.com/u/gundalow)\ **Post date:** [February 12, 2026, 10:03pm UTC](https://forum.ansible.com/t/cfgmgmtcamp-2026-discussion-6-12-collection-documentation-on-ansible-galaxy-is-incomplete-and-partially-confusing/45293/3 "2026-02-12T22:03:21Z")
We often see Collection maintainers wanting to get into the `ansible` package, purely to good quality HTML docs, rather than them being useful to the majority of Ansible users. One thing @oranod and I have talked about is ripping out all the docs build/rendering code from Galaxy (and Automation Hub) and just using the upstream community docs build scripts. They are the most feature rich and well tested. I know @oranod has some ideas about a how we could have all collection docs built this way. So please do share your ideas what what you’d like to see done. ---
**Author:** ![russoz](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/russoz/32/127_2.png) [@russoz](https://forum.ansible.com/u/russoz)\ **Post date:** [February 12, 2026, 10:34pm UTC](https://forum.ansible.com/t/cfgmgmtcamp-2026-discussion-6-12-collection-documentation-on-ansible-galaxy-is-incomplete-and-partially-confusing/45293/4 "2026-02-12T22:34:13Z")
The blunt answer is: I would like to have the ability of publishing docs the same way that packages in ACP do (with versioning in the rendered HTML, with extra docs, the whole shebang), _without_ having to add the package to ACP. Particularly in the case of community.openwrt, I don’t see it ever going into the ACP for many reasons but especially for the fact that the modules are _not_ written in Python, so this would be a need for that collection for the foreseeable future. ---
**Author:** ![felixfontein](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/felixfontein/32/7530_2.png) [@felixfontein](https://forum.ansible.com/u/felixfontein)\ **Post date:** [February 13, 2026, 5:56am UTC](https://forum.ansible.com/t/cfgmgmtcamp-2026-discussion-6-12-collection-documentation-on-ansible-galaxy-is-incomplete-and-partially-confusing/45293/5 "2026-02-13T05:56:12Z")
The shared workflows from [GitHub - felixfontein/github-docs-build: GitHub actions and workflows for building Ansible collection documentation.](https://github.com/felixfontein/github-docs-build/) allow you to do that (except that you don’t have a version selector). For example, the docs for [GitHub - ansible-collections/community.internal\_test\_tools: Internal only, not for end users](https://github.com/ansible-collections/community.internal_test_tools) are at [Community.Internal\_Test\_Tools — Community.Internal\_test\_tools Collection documentation](https://ansible-collections.github.io/community.internal_test_tools/branch/main/), and if you replace `branch/main` by `tag/0.9.0`, you get the docs for version 0.9.0 of the collection (that was the first version for which docs were published for that collection, the docs there aren’t exactly useful, that started with `tag/0.12.0`). What’s missing right now is a version selector which makes these versions accessible. I guess one could also use ReadTheDocs to publish the documentation, since they’re taking care of version selection. I haven’t tried that, but I guess it shouldn’t be too hard to set up either. ---
**Author:** ![oranod](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/oranod/32/1434_2.png) [@oranod](https://forum.ansible.com/u/oranod)\ **Post date:** [February 19, 2026, 5:13pm UTC](https://forum.ansible.com/t/cfgmgmtcamp-2026-discussion-6-12-collection-documentation-on-ansible-galaxy-is-incomplete-and-partially-confusing/45293/6 "2026-02-19T17:13:19Z")
As @gundalow alluded to, and as it came up at CfgMgmtCamp, we’re really interested in using the new docs landing page and RTD hosting to sort of bypass some of the docs rendering issues on Galaxy. We’re working on putting together all the notes from Contributor Summit and outlining work that we’ve identified for the Community and Partner Engineering team. One of those things will be some wireframes and maybe a POC to show how this might work. It could be quite similar to the [ecosystem band](https://docs.ansible.com/#ecosystem) that takes you to the [ecosystem page](https://docs.ansible.com/ecosystem.html). The difference in what we’re thinking is the focus on collections with sort of overlay on Galaxy. We have a js button on `docs.ansible.com` that copies `pip install ansible` to your clipboard. It is easy to add buttons to install collections. I’m not sure if there is a limit to the number of subprojects we can add to the `ansible` namespace in Read the Docs. But if collections publish to RTD it is possible to add them as a subproject so the docs are available under `docs.ansible.com`. The end result should give us a convenient way to highlight collections, increase discovery, and do other things like provide clear indicators of content quality.