Updating pull request

Manik-Khajuria-5 · Manik-Khajuria-5 · commit 90286569949e · 2025-12-02T18:38:32.000+05:30
diff --git a/docs/_inc/_create-classic-ui-instance.md b/docs/_inc/_create-classic-ui-instance.md
@@ -15,4 +15,4 @@ To stop the Plone instance in foreground mode, type {kbd}`ctrl-c`.
 
 ## Related content
 
-- {doc}`Classic UI </classic-ui/index>`
+- {ref}`Classic UI <classic-ui-index-label>`
diff --git a/docs/_inc/_install-python-plone61.md b/docs/_inc/_install-python-plone61.md
@@ -10,4 +10,4 @@ Plone 6.1 requires Python version {{SUPPORTED_PYTHON_VERSIONS_PLONE61}}.
 
 ## Related content
 
-- {doc}`Plone installation requirements </install/index>`
+- {ref}`Plone installation requirements <get-started-label>`
diff --git a/docs/admin-guide/add-site.md b/docs/admin-guide/add-site.md
@@ -72,8 +72,8 @@ Regardless of the frontend you select, you will be redirected to the backend's u
 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
+## 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.
+- {ref}`Install Plone with Cookieplone <install-cookieplone-label>`
+- {ref}`Install Plone with Buildout <install-buildout-label>`
+- {ref}`Install Plone with pip <install-pip-label>`
diff --git a/docs/admin-guide/backup-restore-plone-buildout.md b/docs/admin-guide/backup-restore-plone-buildout.md
@@ -96,6 +96,6 @@ 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
+- {ref}`Export and import site data <exportimport>`
+- {ref}`Install Plone with Buildout <install-buildout-label>`
+- {ref}`Install Plone with pip <install-pip-label>`
diff --git a/docs/admin-guide/export-import.md b/docs/admin-guide/export-import.md
@@ -114,5 +114,5 @@ Consider a File content item with UID `3e0dd7c4b2714eafa1d6fc6a1493f953` and a P
 
 ## 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
+- {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>`
diff --git a/docs/admin-guide/install-buildout.md b/docs/admin-guide/install-buildout.md
@@ -129,7 +129,7 @@ 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
+- {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>`
diff --git a/docs/admin-guide/install-pip.md b/docs/admin-guide/install-pip.md
@@ -100,6 +100,6 @@ bin/runwsgi -v instance/etc/zope.ini
 
 ## 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
+- {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>`
diff --git a/docs/backend/behaviors.md b/docs/backend/behaviors.md
@@ -381,6 +381,6 @@ This dynamically provided interface enables the component architecture to react
 
 ## 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
+- {ref}`Content types <backend-content-types-index-label>`
+- {ref}`Schemas <backend-schemas-label>`
+- {ref}`Fields <backend-fields-label>`
diff --git a/docs/backend/content-types/creating-content-types.md b/docs/backend/content-types/creating-content-types.md
@@ -121,8 +121,8 @@ Also have a look at Plone {doc}`/backend/behaviors`, which provide default featu
 
 ## 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
+- {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>`
diff --git a/docs/backend/content-types/index.md b/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.
diff --git a/docs/backend/fields.md b/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.
@@ -366,7 +368,7 @@ In supermodel XML, the directives are `security:read-permission` and
 
 ## 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
+- {ref}`Schemas <backend-schemas-label>`
+- {ref}`Content types <backend-content-types-index-label>`
+- {ref}`Vocabularies <backend-vocabularies-label>`
+- {ref}`Relations <relations-label>`
diff --git a/docs/backend/relations.md b/docs/backend/relations.md
@@ -646,7 +646,7 @@ But it can also be the name of a relation that is created by code, for example,
 
 ## 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
+- {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>`
diff --git a/docs/backend/schemas.md b/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.
 
 
@@ -731,9 +733,9 @@ def fields(self):
 
 ## 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
+- {ref}`Fields <backend-fields-label>`
+- {ref}`Content types <backend-content-types-index-label>`
+- {ref}`Forms <classic-ui-forms-label>`
+- {ref}`Vocabularies <backend-vocabularies-label>`
 
 
diff --git a/docs/backend/vocabularies.md b/docs/backend/vocabularies.md
@@ -22,6 +22,6 @@ See issue [Backend > Vocabularies needs content](https://github.com/plone/docume
 
 ## 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
+- {ref}`Fields <backend-fields-label>`
+- {ref}`Schemas <backend-schemas-label>`
+- {ref}`Content types <backend-content-types-index-label>`
diff --git a/docs/backend/widgets.md b/docs/backend/widgets.md
@@ -786,7 +786,7 @@ The code renders both widgets, {guilabel}`min` and {guilabel}`max`, in a single
 
 ## 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
+- {ref}`Fields <backend-fields-label>`
+- {ref}`Schemas <backend-schemas-label>`
+- {ref}`Forms <classic-ui-forms-label>`
+- {ref}`Content types <backend-content-types-index-label>`
diff --git a/docs/conceptual-guides/compare-buildout-pip.md b/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.

Original file line number	Diff line number	Diff line change
@@ -15,4 +15,4 @@ To stop the Plone instance in foreground mode, type {kbd}`ctrl-c`.
`15`	`15`
`16`	`16`	`## Related content`
`17`	`17`
`18`		-- {doc}`Classic UI </classic-ui/index>`
	`18`	+- {ref}`Classic UI <classic-ui-index-label>`
Original file line number	Diff line number	Diff line change
`@@ -10,4 +10,4 @@ Plone 6.1 requires Python version {{SUPPORTED_PYTHON_VERSIONS_PLONE61}}.`
`10`	`10`
`11`	`11`	`## Related content`
`12`	`12`
`13`		-- {doc}`Plone installation requirements </install/index>`
	`13`	+- {ref}`Plone installation requirements <get-started-label>`