Add related content

docs/_inc/_continuous-integration.md

@@ -4,4 +4,4 @@ All of a project's CI jobs must pass before a contribution may be accepted.
 
 ```{seealso}
 {doc}`/contributing/core/continuous-integration`
-```
+```

docs/_inc/_create-classic-ui-instance.md

@@ -13,3 +13,6 @@ 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
+
+- {ref}`Classic UI <classic-ui-index-label>`

docs/_inc/_install-python-plone61.md

@@ -7,3 +7,7 @@ The instructions below will create one.
 ```
 
 Plone 6.1 requires Python version {{SUPPORTED_PYTHON_VERSIONS_PLONE61}}.
+
+## Related content
+
+- {ref}`Plone installation requirements <get-started-label>`

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
+
+- {ref}`Install Plone with Cookieplone <install-cookieplone-label>`
+- {ref}`Install Plone with Buildout <install-buildout-label>`
+- {ref}`Install Plone with pip <install-pip-label>`

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
+
+- {ref}`Export and import site data <exportimport>`
+- {ref}`Install Plone with Buildout <install-buildout-label>`
+- {ref}`Install Plone with pip <install-pip-label>`

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
+
+- {ref}`Back up and restore a Plone buildout <back-up-and-restore-a-plone-buildout-label>`
+- {ref}`Add a Plone site <add-a-plone-site-label>`

docs/admin-guide/install-buildout.md

@@ -126,3 +126,10 @@ Stop the instance.
 ```shell
 bin/instance stop
 ```
+
+## Related content
+
+- {ref}`Add a Plone site <add-a-plone-site-label>`
+- {ref}`Install Plone with pip <install-pip-label>`
+- {ref}`Back up and restore a Plone buildout <back-up-and-restore-a-plone-buildout-label>`
+- {ref}`Compare Buildout and pip <compare-buildout-pip-label>`

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
+
+- {ref}`Add a Plone site <add-a-plone-site-label>`
+- {ref}`Install Plone with Buildout <install-buildout-label>`
+- {ref}`Compare Buildout and pip <compare-buildout-pip-label>`

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
+
+- {ref}`Content types <backend-content-types-index-label>`
+- {ref}`Schemas <backend-schemas-label>`
+- {ref}`Fields <backend-fields-label>`

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
+
+- {ref}`Schemas <backend-schemas-label>`
+- {ref}`Fields <backend-fields-label>`
+- {ref}`Widgets <backend-widgets-label>`
+- {ref}`Behaviors <backend-behaviors-label>`
+- {ref}`Factory Type Information <backend-content-types-fti-label>`

docs/backend/content-types/index.md

@@ -7,6 +7,8 @@ myst:
     "keywords": "Content types, Dexterity, Plone"
 ---
 
+(backend-content-types-index-label)=
+
 # Content Types
 
 This part of the documentation describes how to develop content types in Plone.

docs/backend/fields.md

@@ -123,6 +123,8 @@ img_obj = api.content.create(
 
 
 
+(backend-fields-relation-fields-label)=
+
 ### Fields in `z3c.relationfield.schema`
 
 See [`z3c.relationfield`](https://pypi.org/project/z3c.relationfield/) for more details.
@@ -363,3 +365,10 @@ In supermodel XML, the directives are `security:read-permission` and
     <title>Secret</title>
 </field>
 ```
+
+## Related content
+
+- {ref}`Schemas <backend-schemas-label>`
+- {ref}`Content types <backend-content-types-index-label>`
+- {ref}`Vocabularies <backend-vocabularies-label>`
+- {ref}`Relations <relations-label>`

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
+
+- {ref}`Schemas <backend-schemas-label>`
+- {ref}`Relation fields <backend-fields-relation-fields-label>`
+- {ref}`Content types <backend-content-types-index-label>`
+- {ref}`Vocabularies <backend-vocabularies-label>`

docs/backend/schemas.md

@@ -39,6 +39,8 @@ Zope schemas are used for tasks such as:
 -   specifying required attributes on an object
 -   defining custom validators on input data
 
+(schemas-fields-label)=
+
 The basic unit of data model declaration is the {doc}`field </backend/fields>`, which specifies what kind of data each Python attribute can hold.
 
 
@@ -729,4 +731,11 @@ def fields(self):
             f.field = schema_field
 ```
 
+## Related content
+
+- {ref}`Fields <backend-fields-label>`
+- {ref}`Content types <backend-content-types-index-label>`
+- {ref}`Forms <classic-ui-forms-label>`
+- {ref}`Vocabularies <backend-vocabularies-label>`
+
 

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
+
+- {ref}`Fields <backend-fields-label>`
+- {ref}`Schemas <backend-schemas-label>`
+- {ref}`Content types <backend-content-types-index-label>`

docs/backend/widgets.md

@@ -783,3 +783,10 @@ The code renders both widgets, {guilabel}`min` and {guilabel}`max`, in a single
 
 </div>
 ```
+
+## Related content
+
+- {ref}`Fields <backend-fields-label>`
+- {ref}`Schemas <backend-schemas-label>`
+- {ref}`Forms <classic-ui-forms-label>`
+- {ref}`Content types <backend-content-types-index-label>`

docs/conceptual-guides/compare-buildout-pip.md

@@ -7,6 +7,8 @@ myst:
     "keywords": "Plone 6, Conceptual guides, Classic UI, Buildout, pip, install"
 ---
 
+(compare-buildout-pip-label)=
+
 # Compare Buildout and pip
 
 This guide explains the differences between two tools, {term}`Buildout` and {term}`pip`, to install Plone and its Classic UI user interface, helping to inform your choice when developing your new project in Plone.