Document installing a Classic UI project with cookieplone (#1953)

* Document installing a classic project with cookieplone

* update cookieplone output and some wording

* add note for classic ui

* The targets build-dev and build-backend have be replaced by install and backend-build. Also simplify the complex explanation of the make process.

* imho this is distracting for the beginner-oriented installation

* Don't erase history, append to it instead.

* Simplify choose a user interface

* Only markup first instance of glossary terms, move warnings before installing

* Change heading, its label, and prevent an empty heading

* Change headings to be explicitly for Volto, its label, prevent an empty heading, and remove now redundant seealso

* Update docs/install/create-project-cookieplone.md

Co-authored-by: Steve Piercy <[email protected]>

* Update docs/install/index.md

Co-authored-by: Steve Piercy <[email protected]>

* Update docs/reference-guide/cookieplone-make-commands.md

Co-authored-by: Steve Piercy <[email protected]>

* Update docs/admin-guide/add-ons.md

Co-authored-by: Steve Piercy <[email protected]>

* Update docs/admin-guide/add-ons.md

Co-authored-by: Steve Piercy <[email protected]>

* Update docs/admin-guide/add-ons.md

Co-authored-by: Steve Piercy <[email protected]>

* Apply suggestions from code review

Co-authored-by: Steve Piercy <[email protected]>

* rename file

* Anonymize cookieplone output

* Explicitly name heading

* Rename and add redirect

* Promote Cookieplone as the recommended installation method, shortening the path by moving the Buildout and pip comparison to a seealso at the end.

* Remove duplicate versionadded

* Git is capitalized

* Clean up Volto project console output

* Clean up Classic UI project console output

* Make distinction between Volto and Classic UI projects in both headings and narrative text

* Grammar

* Tweak glossary entry

---------

Co-authored-by: Steve Piercy <[email protected]>

Author: pbauer

docs/_static/plone-classic-ui-home-page.png

@@ -26,11 +26,18 @@ Use the following instructions if you installed Plone with Cookieplone.
 
 ### Install an add-on
 
-Add a line with the name of your add-on in the file {file}`backend/requirements.txt`.
-This example uses [`collective.easyform`](https://pypi.org/project/collective.easyform/).
-
-```
-collective.easyform==4.2.1
+Add the name of your add-on in the file {file}`backend/pyproject.toml` in the section `dependencies`.
+This example adds [`collective.easyform`](https://pypi.org/project/collective.easyform/).
+
+```{code-block} toml
+:emphasize-lines: 6
+dependencies = [
+    "Products.CMFPlone==6.1.1",
+    "plone.api",
+    "plone.classicui",
+    "plone.app.caching",
+    "collective.easyform==4.4.0",
+]
 ```
 
 ```{tip}

docs/_static/plone-classic-ui-login-page.png

@@ -25,6 +25,8 @@ The choice of user interface has implications for editors, admins, and developer
 :target: /_static/volto-ui.png
 ```
 
+Test it on https://volto.demo.plone.org (without add-ons) or https://demo.plone.org (with add-ons).
+
 For editors and other end users:
 
 -   The user interface is a fast, modern, single-page web application.
@@ -47,6 +49,8 @@ For developers and integrators:
 :target: /_static/classic-ui.png
 ```
 
+Test it on https://classic.demo.plone.org.
+
 For editors and other end users:
 
 -   The user interface is similar to Plone 5.

docs/admin-guide/add-ons.md

@@ -20,6 +20,6 @@ compare-buildout-pip
 distributions
 package-management
 package-dependencies
-make-build-backend-walk-through
+make-backend-build
 components
 ```

docs/conceptual-guides/choose-user-interface.md

@@ -0,0 +1,25 @@
+---
+myst:
+  html_meta:
+    "description": "make backend-build in Plone."
+    "property=og:description": "make backend-build in Plone."
+    "property=og:title": "make backend-build"
+    "keywords": "Plone 6, make, backend-build, install"
+---
+
+(make-backend-build-label)=
+
+# `make backend-build`
+
+This chapter assumes you have previously followed {doc}`/install/create-project-cookieplone`.
+
+The `Makefile` at the root of your project invokes commands in `backend/Makefile`.
+
+The command `make backend-build` performs the following tasks.
+
+-   Invokes the target `install` in `backend/Makefile`.
+-   `install` has the two dependencies `$(VENV_FOLDER)` and `config`.
+-   `$(VENV_FOLDER)` creates and populates a virtual Python environment with uv from a {file}`constraints.txt` file generated using mxdev.
+-   `config` creates the Zope and Plone configuration files using cookiecutter-zope-instance.
+
+You can configure your Zope instance as described in the section {doc}`/admin-guide/configure-zope`.

docs/conceptual-guides/index.md

@@ -383,6 +383,7 @@
 # -- sphinx-reredirects configuration ----------------------------------
 # https://documatt.com/sphinx-reredirects/usage.html
 redirects = {
+    "conceptual-guides/make-build-backend-walk-through": "/conceptual-guides/make-backend-build.html",
     "contributing/plone-api": "/plone.api/contribute.html",
     "contributing/plone-restapi": "/plone.restapi/docs/source/contributing/index.html",
     "contributing/volto": "/volto/contributing/index.html",

docs/conceptual-guides/make-backend-build.md

@@ -36,8 +36,9 @@ Cookieplone
     ```{versionadded} Volto 18.0.0-alpha.43
     ```
 
-    [Cookieplone](https://github.com/plone/cookieplone) is the method to create a Plone project.
-    You can use Cookieplone to build a backend add-on, a new Volto add-on, or a full project with both backend and frontend.
+    [Cookieplone](https://github.com/plone/cookieplone) is the recommended way to create a Plone project.
+    You can use Cookieplone to build full Plone projects with either {term}`Volto` or {term}`Classic UI` for a frontend.
+    You can also create a backend add-on, a Volto add-on, or a documentation scaffold.
     Cookieplone simplifies the process using robust Cookiecutter templates from {term}`cookieplone-templates`.
 
 cookieplone-templates
@@ -896,7 +897,7 @@ Higher-Order Component
     ```
 
 Mocha
-    [Mocha](https://mochajs.org/) is a feature-rich JavaScript test framework running on {term}`Node.js` and in the browser, making asynchronous testing simple and fun.    
+    [Mocha](https://mochajs.org/) is a feature-rich JavaScript test framework running on {term}`Node.js` and in the browser, making asynchronous testing simple and fun.
 
 Chai
     [Chai](https://www.chaijs.com/) Chai is a {term}`BDD` and {term}`TDD` assertion library for {term}`Node.js` and the browser that can be delightfully paired with any JavaScript testing framework.