# Return documentation fragments, the way forward

**URL:** <https://forum.ansible.com/t/return-documentation-fragments-the-way-forward/44422>\
**Category:** Project Discussions\
**Tags:** dev, mindshare, community-wg-nextmtg, documentation, collections, dawgs-meeting\
**Created:** [September 4, 2025, 3:18pm UTC](https://forum.ansible.com/t/return-documentation-fragments-the-way-forward/44422 "2025-09-04T15:18:23Z")\
**Posts on this page:** 1\
**Showing post:** 7

<div class="post-metadata">

**Author:** ![samccann](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/samccann/32/18_2.png) [@samccann](https://forum.ansible.com/u/samccann)\
**Post date:** [September 9, 2025, 3:50pm UTC](https://forum.ansible.com/t/return-documentation-fragments-the-way-forward/44422/7 "2025-09-09T15:50:00Z")

</div>

With the caveat of - we’re not deeply considering coding and backporting considerations, We discussed in [the DaWGs meeting today](https://forum.ansible.com/t/44449) and in general are liking the direction of the E) proposal above. To be sure we are understing this, we think it means:

- Feature works full in core 2.20 and above. Any user with that version and a collection with the new fragment time is in happy land.
- For any older versions of core (TBD how far back) - a collection with this new fragment will show some kind of ‘helpful warning’ about missing return value info only visible for core 2.20 and above.

…and we did do a bit of ‘squinting/ignoring’ on the backport of that warning - considering it a bugfix is a bit of a ..squint/ignore, and the more ‘purist’ approach is D - it only exists in 2.20, and we’d probably have to remember in 18 months to socialize this new fragment at the point when most collection maintainers would actually consider implementing it.

---

_[View the full topic](https://forum.ansible.com/t/return-documentation-fragments-the-way-forward/44422)._