reorganize distribution docs

Author: davisagli

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

@@ -123,32 +123,14 @@ If you have an existing Plone 5.2 or 6.0 site and you migrate to 6.1, then migra
 
 Plone 6.1 introduces the concept of a Plone {term}`distribution`.
 A Plone distribution is a Python package that defines specific features, themes, add-ons, and configurations that get activated when creating a Plone site.
-Now it is available in core Plone as the recommended way for creating a Plone site.
+Now it is available in core Plone as the recommended way for {doc}`creating a new Plone site </install/add-site>`.
 
-When you install the [`Plone` 6.1 Python package](https://pypi.org/project/Plone/), you get several new packages and two distributions:
-
--   [`plone.distribution`](https://github.com/plone/plone.distribution) is the new main package that offers the basis for distributions.
--   [`plone.exportimport`](https://github.com/plone/plone.exportimport) imports and exports content, users, and other objects between Plone sites.
-    `plone.distribution` uses it.
--   [`plone.volto`](https://github.com/plone/plone.volto) is the distribution to create a Plone site with the default frontend Volto.
-    This package was already present in Plone 6.0, but was upgraded to a distribution.
--   [`plone.classicui`](https://github.com/plone/plone.classicui) is a new package and is the distribution to create a Plone site with the Classic UI frontend.
-
-When you start Plone, the launch screen prompts you to choose a distribution when creating a new Plone site.
-
-````{card}
-```{image} /backend/upgrading/version-specific-migration/images/distribution-chooser.png
-:alt: Launch screen for choosing a distribution
-:target: /_images/distribution-chooser.png
+```{seealso}
+For more information, see {doc}`/conceptual-guides/distributions`.
 ```
-+++
-_Launch screen for choosing a distribution_
-````
-
-After you select a distribution, you will fill out a brief form to configure your new Plone 6.1 site, similar to the process for Plone 6.0.
 
 Distributions are optional.
-If your project only uses the `Products.CMFPlone` Python package, you can still create a Plone site in the usual way.
+If your project only uses the `Products.CMFPlone` Python package, you can still create a Plone site in the old way.
 Consider, however, the following differences from distributions and from Plone 6.0.
 
 -   The configuration form is simpler and shorter.
@@ -157,45 +139,22 @@ Consider, however, the following differences from distributions and from Plone 6
 
 There are a few things you should consider when upgrading a project to, or making an add-on compatible with, Plone 6.1:
 
--   In general, you don't need no change anything.
+-   In general, you don't need to change anything.
     Your existing site will keep working.
     But adding a new site may change in the ways described earlier.
 -   Do you want to use the `Products.CMFPlone` package (0 distributions), either `plone.volto` or `plone.classicui` (1 distribution), or `Plone` (2 distributions)?
--   When your site used the default Volto frontend, you will already have `plone.volto` as a dependency.
+-   If your site uses the default Volto frontend, you will already have `plone.volto` as a dependency.
     This can stay the same.
--   When your site uses only the `Products.CMFPlone` package, the frontend is Classic UI.
+-   If your site uses only the `Products.CMFPlone` package, the frontend is Classic UI.
     This can stay the same, but you may want to depend on `plone.classicui`.
     With that package you can still create a new site and have the same content as before.
--   When your site is using the `Plone` package, you will have the two new distributions available.
+-   If your site uses the `Plone` package, you will have the two new distributions available.
     This is fine.
-    If you know you only need `plone.volto` or only need `plone.classicui`, you can switch to that.
+    If you know you only need `plone.volto` or only need `plone.classicui`, you can switch to only that one.
     You can also limit the options for selecting a distribution by setting the environment variable `ALLOWED_DISTRIBUTIONS` with fewer options.
     Set `ALLOWED_DISTRIBUTIONS=default` for the distribution targeting the default Volto frontend (`plone.volto`).
     Set `ALLOWED_DISTRIBUTIONS=classic` for the distribution with the Classic UI frontend (`plone.classicui`).
 -   If you switch from `Plone` to `plone.volto` or `plone.classicui`, you might want to install extra core add-ons, for example `plone.app.upgrade` or `plone.app.caching`.
--   If your add-on is only for Volto, you may want to add `plone.volto` as a dependency.
--   If your add-on is only for Classic UI, you may want to add `plone.classicui` as a dependency.
+-   If your add-on is only for Volto, you might want to add `plone.volto` as a dependency.
+-   If your add-on is only for Classic UI, you might want to add `plone.classicui` as a dependency.
     Note though that `plone.classicui` is not available for Plone 6.0.
-
-You can create your own distributions to suit your needs.
-
--   Create a distribution demonstrating your favorite setup for Plone.
-    This would contain the add-ons that you usually add in each project, including example content.
-    With this you can create a fully configured Plone site filled with content for a potential client.
-    Or they can try it themselves if the distribution is available publicly.
--   Create a distribution for an internal or client project.
-    This would create a site with all add-ons activated and configured for this project, including example content, and optionally users and groups.
-    During the development phase of a new project, all developers would use this to create a fresh site locally so that everyone has the same configuration and content.
-    Before the project goes live, you can use the distribution to create the initial setup.
-
-```{note}
-For Plone 7, the [Plone roadmap](https://plone.org/why-plone/roadmap) guides development toward a clearer separation between the Classic UI frontend and the core `Products.CMFPlone` backend.
-This means in Plone 7 `Products.CMFPlone` will have less code and pull in fewer dependencies.
-`plone.classicui` may have more code and pull in more dependencies.
-This is the direction in which the backend is heading, and the introduction of the `plone.classicui` distribution package is an important step along this path.
-```
-
-For detailed information, see the source code of the new packages.
-
--   [`plone.distribution`](https://github.com/plone/plone.distribution/)
--   [`plone.exportimport`](https://github.com/plone/plone.exportimport/)

docs/conceptual-guides/distributions.md

@@ -0,0 +1,79 @@
+---
+myst:
+  html_meta:
+    "description": "A Plone distribution is a pre-packaged version of Plone that includes specific features, themes, modules, and configurations."
+    "property=og:description": "A Plone distribution is a pre-packaged version of Plone that includes specific features, themes, modules, and configurations."
+    "property=og:title": "Plone distributions"
+    "keywords": "Plone 6, distribution, plone.distribution"
+---
+
+(plone-distributions-label)=
+
+# Plone distributions
+
+```{versionadded} Plone 6.1
+```
+
+A Plone distribution is a pre-packaged version of Plone that includes specific features, themes, modules, and configurations.
+It is a convenient way to get a specific type of website up and running quickly, as the distribution includes everything needed to run that type of site.
+
+
+## Similar Concept in Other CMS
+
+- **Drupal:** Drupal has distributions for blogs, e-commerce sites, and intranet portals.
+
+- **WordPress:** WordPress has a similar concept in the form of "WordPress Multisite," which allows users to run multiple websites from a single installation of WordPress.
+
+- **Joomla:** Joomla has a similar concept in the form of "Joomla Templates," which are pre-designed templates for Joomla websites.
+
+- **TYPO3:** TYPO3 has a similar concept in the form of "TYPO3 Distributions," which are pre-configured installations of TYPO3 for specific types of websites.
+
+
+## Built-in distributions
+
+Plone comes with two built-in distributions, which correspond to the two Plone user interfaces:
+- `default` (Volto)
+- `classic` (Classic UI)
+
+
+## Third-party distributions
+
+You can create your own distributions to suit your needs.
+
+```{seealso}
+For a how-to guide, see {doc}`/developer-guide/create-a-distribution`.
+```
+
+For example, a Plone consulting agency can create a distribution demonstrating its favorite setup for Plone.
+This would contain the add-ons that they usually add in each project, including example content.
+With this, the agency can create a fully configured Plone site filled with content for a potential client.
+
+Or, an agency or implementer can create a distribution for specific project.
+This would create a site with all add-ons activated and configured for this project, including example content, and optionally users and groups.
+During the development phase of a new project, all developers would use this to create a fresh site locally so that everyone has the same configuration and content.
+
+Custom Plone distributions can be distributions for use by others.
+Examples of third-party Plone distributions include:
+
+- [SENAITE](https://www.senaite.com)
+- [Quaive](https://quaivecloud.com/)
+- [Portal Modelo](https://www.interlegis.leg.br/produtos-servicos/portal-modelo/)
+- [Portal Padrão](https://identidade-digital-de-governo-plone.readthedocs.io/en/latest/)
+
+
+## Related packages
+
+The implementation of distributions in the Plone codebase is found in the following Python packages:
+
+-   [`plone.distribution`](https://github.com/plone/plone.distribution) provides the framework for defining distributions.
+-   [`plone.exportimport`](https://github.com/plone/plone.exportimport) imports and exports content, users, and other objects between Plone sites.
+    `plone.distribution` uses it.
+-   [`plone.volto`](https://github.com/plone/plone.volto) is the distribution to create a Plone site with the default frontend, Volto.
+-   [`plone.classicui`](https://github.com/plone/plone.classicui) is the distribution to create a Plone site with the Classic UI frontend.
+
+```{note}
+For Plone 7, the [Plone roadmap](https://plone.org/why-plone/roadmap) guides development toward a clearer separation between the Classic UI frontend and the core `Products.CMFPlone` backend.
+This means that in Plone 7, `Products.CMFPlone` will have less code and pull in fewer dependencies.
+`plone.classicui` may have more code and pull in more dependencies.
+This is the direction in which the backend is heading, and the introduction of the `plone.classicui` distribution package is an important step along this path.
+```

docs/conceptual-guides/index.md

@@ -15,6 +15,7 @@ This part of the documentation provides explanation of concepts to deepen and br
 ```{toctree}
 :maxdepth: 2
 
+distributions
 package-management
 make-build-backend-walk-through
 ```