Remove mentioning of mxmake.

Author: ksuess

docs/glossary.md

@@ -52,9 +52,6 @@ mxdev
     It is designed for developers who use stable version constraints, then layer their customizations on top of that base while using a version control system.
     This design allows developers to override their base package constraints with a customized or newer version.
 
-mxmake
-    mxmake helps create development environments for Python projects based on [make](https://www.gnu.org/software/make) and [mxdev](https://github.com/mxstack/mxdev).
-
 NFS
     [Network File System](https://en.wikipedia.org/wiki/Network_File_System).
 

docs/install/source-step-by-step.md

@@ -4,7 +4,7 @@ myst:
     "description": "Install Plone 6 backend from its packages for the one who wants to look under the hood"
     "property=og:description": "Install Plone 6 backend from its packages for the one who wants to look under the hood"
     "property=og:title": "Install Plone backend from its Packages – Step by Step"
-    "keywords": "Plone, Plone 6, install, backend, pip, mxdev, mxmake, cookiecutter, packages, source, Zope, buildout"
+    "keywords": "Plone, Plone 6, install, backend, pip, mxdev, cookiecutter, packages, source, Zope, buildout"
 ---
 
 

docs/install/source.md

@@ -113,12 +113,6 @@ You can now run `cookiecutter` to create a Zope instance sceleton with configura
 cookiecutter https://github.com/bluedynamics/plone-kickstarter
 ```
 
-```{todo}
-- Documentation driven implementation: plone-kickstarter: configure with mxmake [on top of] / [enhancing with scripts like test and check and you name it] mxdev.
-- Move bluedynamics/plone-kickstarter to plone/plone-kickstarter in Plone repo?
-- See mxmake in action:  https://github.com/rohberg/Plone_mxmake_example  for ONE single Makefile, ONE single requirements, ONE single constraints
-```
-
 Answer the prompts with:
 
 ```ini
@@ -218,7 +212,6 @@ Checkout an add-on
   url[email protected]:collective/collective.bookmarks.git
   branch=master
   extras = test
-  mxmake-test-path = src
   ```
 
   Add it to {file}`instance.yml` to let Zope know that this add-on should be loaded: