Add "Related content" as the final section in most pages

[stevepiercy]

As an example, the MS SQL docs have "Related content" as the final section in most of their pages.

https://learn.microsoft.com/en-us/sql/t-sql/queries/at-time-zone-transact-sql?view=sql-server-ver17#related-content

I think something like this would be a nice enhancement for the future docs structure.

Caution

Pull requests that don't meet the following requirements shall be immediately closed.

1. The contributor should actually read and understand the content on both the page where they put the links and the destination pages of the links.
2. Ensure that the content between pages or sections is truly related. I've already seen and closed many PRs that mindlessly match a single word.
3. Not be on index.md pages. There's no content on index pages, so it's impossible for anything to be related to it.
4. Not be on pages that serve a similar function as index pages, such as a landing page that directs users to other pages.

Originally posted by @stevepiercy in plone/volto#7360 (comment)

[Manas-Kenge]

This issue is really vague, I think it can be broken down

[stevepiercy]

That comment is pretty vague. If you can improve the description to be less vague, then please do so.

I don't think it's necessary to say, for example, "On Page X, add section 'Related content' with links to Page 1, Page 2, Page 3. On Page Y, add section 'Related content' with links to Page 4, Page 5, Page 6." That's busy work.

[Manas-Kenge]

That comment is pretty vague. If you can improve the description to be less vague, then please do so.

I don't think it's necessary to say, for example, "On Page X, add section 'Related content' with links to Page 1, Page 2, Page 3. On Page Y, add section 'Related content' with links to Page 4, Page 5, Page 6." That's busy work.

I understand what you mean but I didn’t mean to suggest specifying every single page. I only meant that the current issue feels quite broad, and breaking it into a few scoped sub-issues (e.g., Volto UI, Classic UI, REST API, etc.) might make it easier to discuss and implement. This could help reduce the overall scope while keeping the work manageable.

[stevepiercy]

I'm fine with incremental change. One page at a time, where relevant, is good. I don't expect it all to be added everywhere in one fell swoop, and I certainly wouldn't want to review such a humongous beast all at once either.

[Roshani-97]

Hi! I'm Roshani,
I'm new to Plone and would love to contribute to this issue.
I plan to start small by adding a "Related content" section to one or two suitable documentation pages,
following the guidelines mentioned above.
Please let me know if that sounds good.