Usability: intersection between Documentation web, README.md, project page and API site

Hello and thanks for all the documentation

I have used it so much!
And contribute to it a bit long time ago...

Sorry for my bad English.
If you don't understand something, please, ask :)

Problem/Motivation

I use little nowadays Drupal, but I have just migrated and old D7 to D10 and enjoyed a lot the new features.
And of course use a lot the documentation.
Some times already in the project pages, others in the README.md, others in the Drupal Documentation pages and others in the API site.
Drupal is great, but for site builders or frontends the usability is not great as in the backend part.
So I am trying to collaborate with my experience to Drupal.
And I have just thought about Documentation and joining the ways I receive it.

Why don't we join the system?

Steps to reproduce

• Investigate the different solutions that a module offers o search in documentation new Drupal features.
• You get the solutions in the three ways or in internet or in Drupal old documentation that is not good nowadays.
• So you spent a lot of time that I would like to optimize.

Proposed resolution

Documentation:
I put in a screenshot a theoretical text that has to be much better :)
Some times I arrive after searching in internet, so I would like to have the link to the module page.
And I use multilingual, so I would like to have a link to translation page (to download or contribute).

README.md:
Maybe links to the others? I have it not clear, so I don't make an screenshot.

Project page:
On the right column we have: Maintainers, Issues for the project, Resources and Development.
I would add Documentation.
In it, if the project has README.md, a script that adds the link to it from the source code automatically.
By other side, all the projects when they get the project page created in the site have a new page on the Documentation with a default message inviting to collaborate in making it.
With the API I don't have it clear if it has to be with Development or in the Documentation, so I don't put it.

API
I have it not clear, so I don't make an screenshot. Maybe link to Documentation? To make programmers collaborate?

Remaining tasks

Collaborate to make the proposal better with input of different type of this areas to get documentation.
Programing the necessary tools.
Document them.

User interface changes

I add the screenshots.

API changes

Better that a programmer write this.

I hope you think this reporting in my experience is worth and thanks thanks thanks for Documentation