Merge branch '6.0' into create-an-emergency-user

Author: stevepiercy

.vscode/settings.json

@@ -0,0 +1,5 @@
+{
+  "[markdown]": {
+    "editor.formatOnSave": false
+  }
+}

docs/_inc/_continuous-integration.md

@@ -0,0 +1,7 @@
+Plone project repositories use {term}`continuous integration` (CI) to run tests, ensure code quality, or provide previews for every contribution.
+Plone uses GitHub workflows, Jenkins, Cypress, Read the Docs, and other services for CI.
+All of a project's CI jobs must pass before a contribution may be accepted.
+
+```{seealso}
+{doc}`/contributing/core/continuous-integration`
+```

docs/backend/annotations.md

@@ -1,10 +1,10 @@
 ---
 myst:
   html_meta:
-    "description": ""
-    "property=og:description": ""
-    "property=og:title": ""
-    "keywords": ""
+    "description": "Annotations store arbitrary values on Python objects—such as a Plone site or HTTP request—for storage and caching purposes."
+    "property=og:description": "Annotations store arbitrary values on Python objects—such as a Plone site or HTTP request—for storage and caching purposes."
+    "property=og:title": "Annotations"
+    "keywords": "Annotations, plone.memoize, cache, portal, content object"
 ---
 
 (backend-annotations-label)=

docs/backend/upgrading/version-specific-migration/upgrade-to-python3.md

@@ -14,9 +14,6 @@ myst:
 
 This chapter provides instructions and tips for porting Plone projects to Python 3.
 
-```{seealso}
-If you want to upgrade add-ons to Python 3, the list of all Plone packages that still need to be ported can be found on the GitHub project board [Python 3 porting state for Plone add-ons](https://github.com/orgs/collective/projects/1).
-```
 
 ## Principles
 

docs/conf.py

@@ -125,15 +125,21 @@
     "**/CONTRIBUTORS.rst",
     "**/LICENSE.rst",
     "**/README.rst",
+    "**/eggs",
+    "_inc/.*",
     "plone.restapi/.*",
     "plone.restapi/bin",
+    "plone.restapi/develop-eggs",
     "plone.restapi/docs/source/glossary.md",  # There can be only one Glossary.
+    "plone.restapi/eggs",
     "plone.restapi/ideas",
     "plone.restapi/include",
     "plone.restapi/lib",
     "plone.restapi/news",
+    "plone.restapi/parts",
     "plone.restapi/performance",
     "plone.restapi/src",
+    "plone.restapi/var",
     "volto/contributing/branch-policy.md",
     "volto/contributing/install-docker.md",
     "volto/contributing/install-git.md",

docs/contributing/core/continuous-integration.md

@@ -27,6 +27,12 @@ Otherwise GitHub workflows do not run automatically, and require a member with w
 GitHub workflows should pass before running Jenkins checks and before merging an open pull request.
 
 
+## `mr-roboto`
+
+[`mr-roboto`](https://github.com/plone/mr.roboto) enforces the requirement of a signed Plone Contributor Agreement from a new contributor, and being assigned to a Plone team on GitHub.
+It also suggests to run Jenkins for many Plone packages.
+
+
 ## Jenkins
 
 [Jenkins](https://jenkins.plone.org) is the authoritative source to see whether the complete test suite passes for any Plone version under development.

docs/contributing/core/index.md

@@ -292,14 +292,10 @@ This enables automatic closing of the related issue when the pull request is mer
 This also creates a hyperlink to the original issue for easy reference.
 
 
-## Jenkins and mr.roboto
+## Continuous integration
 
-Plone has a continuous integration ({term}`CI`) setup and follows CI rules.
-
-When you push a change to a Plone package, there may be GitHub workflows that run automatically.
-The CI package [mr.roboto](https://github.com/plone/mr.roboto) will perform some checks and suggest that you run Jenkins after all other CI runs.
-
-See {doc}`continuous-integration` for more information.
+```{include} /_inc/_continuous-integration.md
+```
 
 
 ## Additional material

docs/contributing/documentation/index.md

@@ -111,7 +111,7 @@ After your Plone Contributor Agreement has been approved, and you have been adde
 
 1.  Clarify the scope of work that needs to be done.
     Check for previous work, assignment to another developer, or whether the requirements have changed.
-1.  [Assign yourself to the issue](https://docs.github.com/en/issues/tracking-your-work-with-issues/assigning-issues-and-pull-requests-to-other-github-users).
+1.  [Assign yourself to the issue](https://docs.github.com/en/issues/tracking-your-work-with-issues/using-issues/assigning-issues-and-pull-requests-to-other-github-users).
     This signals to other developers that you are working on the issue.
 
 From here, you can either make {ref}`contributing-quick-edits-label` or {ref}`contributing-large-edits-label`.

docs/contributing/first-time.md

@@ -260,7 +260,7 @@ Once you have completed, tested, and linted your code, and created a {ref}`contr
         This also creates a hyperlink to the original issue for easy reference.
 
         ```{seealso}
-        [Linking a pull request to an issue using a keyword](https://docs.github.com/en/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword)
+        [Linking a pull request to an issue using a keyword](https://docs.github.com/en/issues/tracking-your-work-with-issues/using-issues/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword)
         ```
 
 1.  **Request a review.**

docs/contributing/index.md

@@ -60,13 +60,13 @@ All contributors to the Plone Documentation follow the Code of Conduct.
 
 First-time contributors should read and follow our guide {doc}`first-time`.
 
+
 (contributing-continuous-integration-label)=
 
 ## Continuous integration
 
-Plone project repositories use continuous integration (CI) to run tests, ensure code quality, or provide previews for every contribution.
-Plone uses GitHub Actions, Jenkins, Cypress, Netlify, and other services for CI.
-All of a project's CI jobs must pass before a contribution may be accepted.
+```{include} /_inc/_continuous-integration.md
+```
 
 (contributing-change-log-label)=