Merge branch '6.0' into linkcheck-news-volto

Author: stevepiercy

.github/ISSUE_TEMPLATE/new-issue-form.yml

@@ -5,17 +5,18 @@ body:
     attributes:
       value: |
         Thanks for taking the time to fill out this issue report!
-  - type: checkboxes
-    id: plone-versions
+  - type: textarea
+    id: documentation-url
     attributes:
-      label: Plone Documentation versions affected
-      options:
-        - label: 5.x
-        - label: 6.x
+      label: Links of affected pages in Plone Documentation, if any.
+      value: |
+        - Link_1
+        - Link_2
+        - ...
   - type: textarea
     id: description
     attributes:
       label: Description
-      description: If relevant, please include links to the affected resources, screenshots, and any other helpful information.
+      description: Include include screenshots and any other helpful information.
     validations:
       required: true

.github/PULL_REQUEST_TEMPLATE/pull_request_template.md renamed to .github/pull_request_template.md

@@ -1,3 +1,11 @@
+## First-time contributors
+
+You **must** read and follow our [First-time contributors](https://6.docs.plone.org/contributing/first-time.html).
+
+---
+
+## Submit a pull request
+
 Thank you for your contribution to the Plone Documentation.
 
 Before submitting this pull request, please make sure you follow our guides:
@@ -7,9 +15,9 @@ Before submitting this pull request, please make sure you follow our guides:
 -   [Authors guide](https://6.docs.plone.org/contributing/authors.html)
 -   [MyST reference](https://6.docs.plone.org/contributing/myst-reference.html)
 
-## Issue Number
+## Issue number
 
-- Issue #
+- Fixes #
 
 ## Description
 

.vale.ini

@@ -8,3 +8,5 @@ Packages = Microsoft
 
 [*]
 BasedOnStyles = Vale, Microsoft
+Microsoft.Contractions = suggestion
+Microsoft.Units = suggestion

docs/backend/behaviors.md

@@ -30,7 +30,7 @@ Other behaviors are implemented as add-on products, which can be installed and c
 Once a behavior has been installed, it can be applied to any content type by selecting it in the {guilabel}`Content Types` control panel.
 This allows items of this content type to gain the additional functionality provided by the behavior.
 
-A key feature of behaviors is that they allow encapsulating functionality so that it can be reused for multiple content types without needing to reimplement it.
+A key feature of behaviors is that they allow encapsulating functionality so that it can be reused for multiple content types without needing to implement it again.
 Overall, behaviors are an important part of the Plone content management system and allow for powerful customization and extensibility of content objects.
 
 
@@ -40,7 +40,7 @@ Overall, behaviors are an important part of the Plone content management system
 
 To view a complete list of built-in behaviors, browse to {guilabel}`Content Types` control panel, then click {guilabel}`Page` (or any other content type), then {guilabel}`Behaviors`.
 
-| short name | Title | Desription |
+| short name | Title | Description |
 |---|---|---|
 | `plone.allowdiscussion` | Allow discussion | Allow discussion on this item |
 | `plone.basic` | Basic metadata | Adds title and description fields. |
@@ -72,11 +72,11 @@ To view a complete list of built-in behaviors, browse to {guilabel}`Content Type
 | `volto.preview_image` | Preview Image | Preview image for listings |
 | `volto.preview_image_link` | Preview Image Link | Preview image for listings based on links |
 | `plone.relateditems` | Related items | Adds the ability to assign related items |
-| `plone.richtext` | RichText | Adds richtext behavior |
+| `plone.richtext` | RichText | Adds RichText behavior |
 | `plone.shortname` | Short name | Gives the ability to rename an item from its edit form. |
 | `plone.tableofcontents` | Table of contents | Adds a table of contents |
-| `plone.thumb_icon` | Thumbs and icon handling | Options to suppress thumbs and/or icons and to override thumb   size in listings, tables etc.
-| `plone.versioning` | Versioning | Versioning support with CMFEditions |
+| `plone.thumb_icon` | Thumbs and icon handling | Options to suppress thumbs or icons and to override thumb size in listings, tables, and other user interface elements |
+| `plone.versioning` | Versioning | Versioning support with `CMFEditions` |
 
 ```{todo}
 For each behavior in the table above, one may view the source code of the checkbox (its `name` attribute) to view its Short Name.
@@ -307,7 +307,7 @@ You do not *need* to know this, but it may help if you run into problems.
 ```
 
 In Plone, behaviors can be globally enabled on content types at runtime.
-With add-ons, behaviors can be enabled even on a single content object or for a whole subtree in the content hierarchy.
+With add-ons, behaviors can be enabled even on a single content object or for a whole subdirectory tree in the content hierarchy.
 
 
 ### Interfaces and adapters

docs/backend/content-types/creating-content-types.md

@@ -0,0 +1,120 @@
+---
+myst:
+  html_meta:
+    "description": "Creating content types to manage tasks in Plone."
+    "property=og:description": "Creating content types to manage tasks in Plone."
+    "property=og:title": "Creating content types to manage tasks in Plone."
+    "keywords": "Content Types, FTI, Dexterity, plonecli, bobtemplates.plone"
+---
+
+# Creating content types
+
+When we attempt to solve a particular content management problem with Plone, we will often design new content types.
+For the purpose of this example, we'll build a simple set of types to manage tasks.
+
+-   We will use a content type `Tasks` to hold all task objects and present a list of tasks to the user.
+    This type is folderish (`Container`).
+-   We will use a content type `Task` with the information about the task.
+    Fields include name, description, and status of the task.
+    This type is non-folderish (`Item`).
+
+## Creating a Plone package
+
+We typically create a content type inside a Plone package.
+We will use the {term}`plonecli` to create a Plone package and our content types.
+
+```shell
+plonecli create addon collective.tasks
+cd collective.tasks
+```
+
+## Adding content types
+
+Let's add a content type called `Tasks`:
+
+```shell
+plonecli add content_type
+```
+
+Fill in the name `Tasks` for the first content type:
+
+```console
+-> Content type name (Allowed: _ a-z A-Z and whitespace) [Todo Task]: Tasks
+```
+
+We keep the default base class `Container` here:
+
+```console
+--> Dexterity base class (Container/Item) [Container]:
+```
+
+We keep the default `globally addable`:
+
+```console
+--> Should the content type globally addable? [y]:
+```
+
+We want to filter content types, which can be added to this container:
+
+```console
+--> Should we filter content types to be added to this container? [n]: y
+```
+
+We keep the default behaviors active:
+
+```console
+--> Activate default behaviors? [y]:
+```
+
+Now let's add a content type called `Task`:
+
+```shell
+plonecli add content_type
+```
+
+Fill in the name `Task` for the first content type:
+
+```console
+-> Content type name (Allowed: _ a-z A-Z and whitespace) [Todo Task]: Task
+```
+
+We change the base class to `Item` here:
+
+```console
+--> Dexterity base class (Container/Item) [Container]: Item
+```
+
+We don't want it to be globally addable `globally addable`:
+
+```console
+--> Should the content type globally addable? [y]: n
+```
+
+If we disable `globally addable`, the next question will ask for the parent content type, where we will answer `Tasks`:
+
+```console
+--> Parent container portal_type name: Tasks
+```
+
+For the rest of the questions, we can keep the defaults.
+
+To test our new Plone package and its content types, we can use {term}`plonecli` to build a development environment and start Plone.
+
+```shell
+plonecli build
+plonecli serve
+```
+
+Your Plone is now running on http://localhost:8080.
+You can add a new Plone site, enable your add-on, and add your content types.
+
+```{seealso}
+{term}`plonecli` takes care of all the details of a content type and its configuration.
+For more configuration details, see {doc}`fti`.
+```
+
+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.