Improve install docs

[MrTango]

This corrects the creation of Python venv. We shoud never mix the venv with other configuration like the buildout configuration or others. This can lead to losing data or configuration when updating the venv later.

so instead of

python3 -m venv .

we should use

python3 -m venv venv

or similar to create a venv.
Then either activate the venv or use it like this

./venv/bin/pip install Plone

The buildout bootstrap command is useful to avoid the need to always prefix the buildout run with the venv path later.
It will create the bin/buildout script and only need to run once.

[davisagli]

Basically LGTM now.

[stevepiercy]

This corrects the creation of Python venv. We shoud never mix the venv with other configuration like the buildout configuration or others. This can lead to losing data or configuration when updating the venv later.

so instead of

python3 -m venv .

we should use

python3 -m venv venv

or similar to create a venv. Then either activate the venv or use it like this

./venv/bin/pip install Plone

The buildout bootstrap command is useful to avoid the need to always prefix the buildout run with the venv path later. It will create the bin/buildout script and only need to run once.

I just want to say that I really appreciate this explanation. I have long felt that creating Python virtual environments at the project root was "not right", both in Plone documentation and our tools. Coming from Pyramid, I always used env/bin/thingie but never activated it. In their docs, they used an additional step as demonstrated in Set an environment variable and explained in Why use $VENV/bin/pip instead of source bin/activate, then pip?. In practice, I felt that last bit was too much, because anything that requires me to hold down the SHIFT key slows down my typing.

[stevepiercy]

Minor tweaks to grammar, sprinkle some MyST syntax and reference links, and reword a few things.

[stevepiercy]

Thanks @MrTango and @davisagli! I'll merge this as soon as it's green.