diff --git a/docs/admin-guide/add-site.md b/docs/admin-guide/add-site.md index 0fd93872de..971f10496c 100644 --- a/docs/admin-guide/add-site.md +++ b/docs/admin-guide/add-site.md @@ -71,3 +71,12 @@ 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` +- {doc}`/admin-guide/install-buildout` +- {doc}`/admin-guide/install-pip` +- {doc}`/conceptual-guides/distributions` +- {doc}`/developer-guide/create-a-distribution` +- {doc}`/conceptual-guides/choose-user-interface` diff --git a/docs/admin-guide/backup-restore-plone-buildout.md b/docs/admin-guide/backup-restore-plone-buildout.md index aa204b3ef8..2e36751426 100644 --- a/docs/admin-guide/backup-restore-plone-buildout.md +++ b/docs/admin-guide/backup-restore-plone-buildout.md @@ -92,4 +92,9 @@ 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. \ No newline at end of file +Some Plone sites require incremental backups every few minutes. + +## Related content + +- {doc}`/admin-guide/export-import` +- {doc}`/admin-guide/install-buildout` \ No newline at end of file diff --git a/docs/admin-guide/export-import.md b/docs/admin-guide/export-import.md index 76132a1847..ea908b7245 100644 --- 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` +- {ref}`add-a-plone-site-label` diff --git a/docs/admin-guide/install-buildout.md b/docs/admin-guide/install-buildout.md index da4dfc386c..5888502c1e 100644 --- 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` +- {doc}`/admin-guide/install-pip` +- {doc}`/admin-guide/backup-restore-plone-buildout` +- {doc}`/conceptual-guides/compare-buildout-pip` diff --git a/docs/admin-guide/install-pip.md b/docs/admin-guide/install-pip.md index 0cd7bc7aef..fbdfd32e3c 100644 --- 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` +- {doc}`/admin-guide/install-buildout` +- {doc}`/conceptual-guides/compare-buildout-pip` diff --git a/docs/backend/behaviors.md b/docs/backend/behaviors.md index 3cb7271c28..0cab7e8055 100644 --- 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` +- {doc}`/backend/schemas` +- {doc}`/backend/fields` diff --git a/docs/backend/content-types/creating-content-types.md b/docs/backend/content-types/creating-content-types.md index 29781858ef..c3e6433baf 100644 --- 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` +- {doc}`/backend/fields` +- {doc}`/backend/widgets` +- {doc}`/backend/behaviors` +- {doc}`/backend/content-types/fti` diff --git a/docs/backend/content-types/index.md b/docs/backend/content-types/index.md index 165fbfec9e..676bccf8d4 100644 --- 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 index a7d261ad35..b3c2212c8a 100644 --- 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. @@ -363,3 +365,10 @@ In supermodel XML, the directives are `security:read-permission` and Secret ``` + +## Related content + +- {doc}`/backend/schemas` +- {doc}`/backend/content-types/index` +- {doc}`/backend/vocabularies` +- {doc}`/backend/relations` diff --git a/docs/backend/relations.md b/docs/backend/relations.md index c943b94e8c..18a32c8acd 100644 --- 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` +- {ref}`backend-fields-relation-fields-label` +- {doc}`/backend/content-types/index` +- {doc}`/backend/vocabularies` diff --git a/docs/backend/schemas.md b/docs/backend/schemas.md index 24bc654a10..8483cefa2a 100644 --- 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 `, which specifies what kind of data each Python attribute can hold. @@ -729,4 +731,11 @@ def fields(self): f.field = schema_field ``` +## Related content + +- {doc}`/backend/fields` +- {doc}`/backend/content-types/index` +- {doc}`/classic-ui/forms` +- {doc}`/backend/vocabularies` + diff --git a/docs/backend/vocabularies.md b/docs/backend/vocabularies.md index e4bc50cc22..780644ad64 100644 --- 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). -``` \ No newline at end of file +``` + +## Related content + +- {doc}`/backend/fields` +- {doc}`/backend/schemas` +- {doc}`/backend/content-types/index` \ No newline at end of file diff --git a/docs/backend/widgets.md b/docs/backend/widgets.md index aa77d8eb73..5b6cf16f77 100644 --- 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 ``` + +## Related content + +- {doc}`/backend/fields` +- {doc}`/backend/schemas` +- {doc}`/classic-ui/forms` +- {doc}`/backend/content-types/index` diff --git a/docs/conceptual-guides/compare-buildout-pip.md b/docs/conceptual-guides/compare-buildout-pip.md index af770a7064..24a56f459b 100644 --- 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.