the workaround will ensure the collections
section of the devel docs will be identical to the collections
section of latest docs for now. Until we have real 'devel'
collections docs(samccann,
15:21:33)
reviews welcome on
https://github.com/ansible-community/antsibull/pull/282 and
https://github.com/ansible/ansible/pull/74988(samccann,
15:28:38)
related issue is
https://github.com/ansible-community/antsibull/issues/54(samccann,
15:29:12)
reviews welcome on
https://github.com/ansible/ansible/pull/74914(samccann,
15:37:20)
reviews also welcome on
https://github.com/ansible/ansible/pull/74963 btw which adds
documentation capabilities for filter and test docs(samccann,
15:38:27)
the two PRs above expand the range of the
generated technical docs (by extending config documentation and
documenting filter and test plugins)(acozine,
15:39:34)
related PRs
https://github.com/ansible/ansible/pull/74937
https://github.com/ansible-community/antsibull/pull/281
https://github.com/ansible-collections/community.dns/pull/23(samccann,
15:45:44)
key=value pair rendering - IBM style guide
suggests monospace(samccann,
15:48:17)
- older discussions on this topic
https://github.com/ansible/community/issues/521#issuecomment-739263018
and
https://meetbot.fedoraproject.org/ansible-docs/2020-12-15/dawgs_aka_docs_working_group.2020-12-15-16.01.log.html
(search for value)(samccann,
15:55:14)
ACTION: - review
these rendering options to vote next week:(samccann,
15:59:44)