We need an explicit way to link a module's documentation to its related project page. In the module project page we already have a field to link to the documentation. But if you go to the documentation you won't see a link to the project page unless someone has manually created a link within the text. The link between documentation and project is a critical bit of data that should be in a separate field.
If the project page was explicitly a "related node" we could pull all sorts of useful information into a block on the handbook page like - Drupal versions supported, related modules, whether the module is deprecated etc.
This would only be needed on the parent page of the module's documentation as the child pages could inherit the information.
Perhaps in an ideal world, we wouldn't need to do create this again on the documentation side. There might be some way of capturing that relationship from what already exists in the project page. But in any case we should have, for each module's handbook content, a block that provides a link to the project page and that shows the supported versions.
wrapup of the discussion in comments:
Postponed: needs info
Docs infrastructure
Infrastructure/code improvements related to documentation. The Core Documentation team uses this tag.
Makes Drupal easier to use. Preferred over UX, D7UX, etc.
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
There hasn't been work on this for 11 years. Is there interest in pursuing this?
I don’t think this is relevant now.
Projects have a documentation link field which can go anywhere, since things like documentation in GitLab pages are effectively off-site.
Documentation on Drupal.org has related content that can include projects, or any other content.