Too many installation docs (and other suggested improvements)

[stevepiercy]

We have too many Volto installation docs.

• https://github.com/plone/volto#quick-start DELETED.
• https://github.com/plone/volto#volto-development DELETED.
• docs/source/getting-started/install.md DELETED.
• Develop Volto core
• Install Volto for development See Consolidate install Volto for development docs #5556 RESOLVED
• Creating a new Volto project
• Too many ways to start dev pieces #4079
• Plone 6 Install
• Trainings:
  • https://training.plone.org/volto/bootstrap.html ARCHIVED to https://2022.training.plone.org/volto/bootstrap.html
  • https://training.plone.org/voltohandson/quickstart.html
  • https://training.plone.org/voltoaddons/01-addon-basics.html#bootstrap-a-new-volto-project
  • https://training.plone.org/mastering-plone/installation.html#installing-plone-frontend
  • https://training.plone.org/plone_training_config/instructions.html#installing-the-frontend DELETED
• Others?

I would strongly advocate for one, and only one, way to install Volto for development in Plone 6.

This would make it easier to maintain installation documentation and reduce frustration of developers.

As a couple of side notes:

1. I would require, not make it optional, to use nvm. Alternatively, we should make a statement such as, "The Volto development team uses nvm for installing and managing versions of Node.js. We do not support any other node version manager or the lack of one. If you do not use nvm, then we assume you know what you are doing and can resolve issues on your own."
2. Provide clear paths to install Volto using either Docker or a manual installation. The current docs are not structured clearly because all headings are at the same level and not in order. The proposed version aims to provide that structure and order.
3. State "For simplicity in documentation, we use bash for a shell. Adjust commands according to your preferred shell flavor."
4. Specify what characters are valid in a project name for npm init yo @plone/volto. Letters, number, dashes, underscores, other characters?
5. Use "Install", not "Getting Started", buried under "Introduction". Elevate it.
6. Separate "Installation" from "Development" documentation. Volto (and any other core Plone package) should still have its specific documentation for development purposes, such as for running tests.

[stevepiercy]

I've created a project to track all Install-related issues, Install Docs.

[stevepiercy]

I'm going to close this issue, because we have resolved most of the issues and consolidated documentation into include files. Specific issues remain, but they can be addressed separately.