docs: Add 'Related content' as the final section in most pages (#1973)

Manik-Khajuria-5 · Manik-Khajuria-5 · commit ef0354f581c3 · 2025-12-02T11:06:48.000+05:30
diff --git a/docs/_inc/_continuous-integration.md b/docs/_inc/_continuous-integration.md
@@ -5,3 +5,6 @@ All of a project's CI jobs must pass before a contribution may be accepted.
 ```{seealso}
 {doc}`/contributing/core/continuous-integration`
 ```
+
+
+
diff --git a/docs/_inc/_create-classic-ui-instance.md b/docs/_inc/_create-classic-ui-instance.md
@@ -13,3 +13,9 @@ You will be redirected to your new Classic UI Plone site.
 
 To stop the Plone instance in foreground mode, type {kbd}`ctrl-c`.
 
+## Related content
+
+- {doc}`Classic UI </classic-ui/index>`
+
+
+
diff --git a/docs/_inc/_install-python-plone61.md b/docs/_inc/_install-python-plone61.md
@@ -7,3 +7,8 @@ The instructions below will create one.
 ```
 
 Plone 6.1 requires Python version {{SUPPORTED_PYTHON_VERSIONS_PLONE61}}.
+
+## Related content
+
+- {doc}`Plone installation requirements </install/index>`
+
diff --git a/docs/admin-guide/add-site.md b/docs/admin-guide/add-site.md
@@ -71,3 +71,9 @@ The launch screen for adding a site is hosted by the Plone backend server.
 Regardless of the frontend you select, you will be redirected to the backend's user interface after you create the site.
 If you select the Volto frontend, you can switch to it by changing the port number in the URL, usually `3000`, and visiting it at http://localhost:3000, for example.
 ```
+
+## Related Content
+
+- {doc}`/install/create-project-cookieplone` — Create a new Plone project using Cookiecutter.
+- {doc}`/admin-guide/install-buildout` — Install Plone using Buildout.
+- {doc}`/admin-guide/install-pip` — Install Plone using pip.
diff --git a/docs/admin-guide/backup-restore-plone-buildout.md b/docs/admin-guide/backup-restore-plone-buildout.md
@@ -92,4 +92,10 @@ Tune these to meet your needs.
 When you enable incremental backups, the database packing operation will automatically cause the next backup to be a full backup.
 
 If your backup continuity need is critical, then your incremental backup schedule may need to be frequent.
-Some Plone sites require incremental backups every few minutes.
+Some Plone sites require incremental backups every few minutes.
+
+## Related content
+
+- {doc}`/admin-guide/export-import` — Export and import content
+- {doc}`/admin-guide/install-buildout` — Install Plone using Buildout
+- {doc}`/admin-guide/install-pip` — Install Plone using pip
diff --git a/docs/admin-guide/export-import.md b/docs/admin-guide/export-import.md
@@ -111,3 +111,8 @@ Consider a File content item with UID `3e0dd7c4b2714eafa1d6fc6a1493f953` and a P
 | --- | --- |
 | `content/3e0dd7c4b2714eafa1d6fc6a1493f953/data.json` | JSON File with serialized representation of a content item |
 | `content/3e0dd7c4b2714eafa1d6fc6a1493f953/file/plone.pdf` | Blob file stored in the `file` field in the content item |
+
+## Related content
+
+- {doc}`/admin-guide/backup-restore-plone-buildout` — Back up and restore Plone sites
+- {doc}`/admin-guide/add-site` — Add a Plone site to an existing instance
diff --git a/docs/admin-guide/install-buildout.md b/docs/admin-guide/install-buildout.md
@@ -126,3 +126,10 @@ Stop the instance.
 ```shell
 bin/instance stop
 ```
+
+## Related content
+
+- {doc}`/admin-guide/add-site` — Add a Plone site after installation
+- {doc}`/admin-guide/install-pip` — Alternative installation method using pip
+- {doc}`/admin-guide/backup-restore-plone-buildout` — Back up and restore your Plone site
+- {doc}`/conceptual-guides/compare-buildout-pip` — Compare Buildout and pip installation methods
diff --git a/docs/admin-guide/install-pip.md b/docs/admin-guide/install-pip.md
@@ -97,3 +97,9 @@ bin/runwsgi -v instance/etc/zope.ini
 
 ```{include} /_inc/_create-classic-ui-instance.md
 ```
+
+## Related content
+
+- {doc}`/admin-guide/add-site` — Add a Plone site after installation
+- {doc}`/admin-guide/install-buildout` — Alternative installation method using Buildout
+- {doc}`/conceptual-guides/compare-buildout-pip` — Compare Buildout and pip installation methods
diff --git a/docs/backend/behaviors.md b/docs/backend/behaviors.md
@@ -378,3 +378,9 @@ The [README file of `plone.behavior`](https://github.com/plone/plone.behavior/bl
 Plone content objects have logic to look up the behaviors' names registered from their types' configuration, the {term}`Factory Type Information` (FTI).
 At runtime, the logic provides the interface (or marker) from the behavior to the object.
 This dynamically provided interface enables the component architecture to react to this new interface by adding additional form fields, bindings events, enabling more specific views, and more.
+
+## Related content
+
+- {doc}`/backend/content-types/index` — Add behaviors to content types
+- {doc}`/backend/schemas` — Define schemas for behaviors
+- {doc}`/backend/fields` — Field types used in behavior schemas
diff --git a/docs/backend/content-types/creating-content-types.md b/docs/backend/content-types/creating-content-types.md
@@ -118,3 +118,11 @@ For now your content type doesn't have any custom schema with fields defined.
 See {doc}`/backend/schemas`, {doc}`/backend/fields` and {doc}`/backend/widgets` for information on how to add custom fields and widgets to your content type.
 
 Also have a look at Plone {doc}`/backend/behaviors`, which provide default features you can enable per content type.
+
+## Related content
+
+- {doc}`/backend/schemas` — Define schemas for your content types
+- {doc}`/backend/fields` — Field types for content type schemas
+- {doc}`/backend/widgets` — Customize form widgets
+- {doc}`/backend/behaviors` — Add reusable behaviors to content types
+- {doc}`/backend/content-types/fti` — Configure Factory Type Information
diff --git a/docs/backend/fields.md b/docs/backend/fields.md
@@ -363,3 +363,10 @@ In supermodel XML, the directives are `security:read-permission` and
     <title>Secret</title>
 </field>
 ```
+
+## Related content
+
+- {doc}`/backend/schemas` — How fields compose schemas
+- {doc}`/backend/content-types/index` — Use fields in content type schemas
+- {doc}`/backend/vocabularies` — Define vocabularies for Choice fields
+- {doc}`/backend/relations` — Relation fields for linking content
diff --git a/docs/backend/relations.md b/docs/backend/relations.md
@@ -643,3 +643,10 @@ Thus the API for getting the target uses:
 In addition, the relation value knows under which attribute it has been stored as `from_attribute`.
 It is usually the name of the field with which the relation is created.
 But it can also be the name of a relation that is created by code, for example, through link integrity relations (`isReferencing`) or the relation between a working copy and the original (`iterate-working-copy`).
+
+## Related content
+
+- {doc}`/backend/schemas` — Define schemas for content types and forms
+- {doc}`/backend/fields` — Field types including `RelationChoice` and `RelationList`
+- {doc}`/backend/content-types/index` — Create custom content types with relations
+- {doc}`/backend/vocabularies` — Control which items can be related using vocabularies
diff --git a/docs/backend/schemas.md b/docs/backend/schemas.md
@@ -729,4 +729,11 @@ def fields(self):
             f.field = schema_field
 ```
 
+## Related content
+
+- {doc}`/backend/fields` — Field types used in schemas
+- {doc}`/backend/content-types/index` — Use schemas to define content types
+- {doc}`/classic-ui/forms` — Use schemas to create forms
+- {doc}`/backend/vocabularies` — Define vocabularies for Choice fields
+
 
diff --git a/docs/backend/vocabularies.md b/docs/backend/vocabularies.md
@@ -18,4 +18,10 @@ See the chapter {ref}`training:vocabularies-label` from the Mastering Plone 6 Tr
 ```{todo}
 Contribute to this documentation!
 See issue [Backend > Vocabularies needs content](https://github.com/plone/documentation/issues/1306).
-```
+```
+
+## Related content
+
+- {doc}`/backend/fields` — Use vocabularies with Choice fields
+- {doc}`/backend/schemas` — Define schemas with Choice fields
+- {doc}`/backend/content-types/index` — Use vocabularies in content type schemas
diff --git a/docs/backend/widgets.md b/docs/backend/widgets.md
@@ -783,3 +783,10 @@ The code renders both widgets, {guilabel}`min` and {guilabel}`max`, in a single
 
 </div>
 ```
+
+## Related content
+
+- {doc}`/backend/fields` — Field types that use widgets
+- {doc}`/backend/schemas` — Define schemas with widget directives
+- {doc}`/classic-ui/forms` — Use widgets in forms
+- {doc}`/backend/content-types/index` — Customize widgets for content types
