reorg docs: Install section

[fenekku]

• docs-reorg: refactor Install section

Notes

• This reorganization pass makes more content changes than the previous ones.
• The split between "containerized preview" and "local development" installation is made explicit
• virtualenvs.md is moved to References
• migrate.md (migrating data) is moved to Operate > Operations
• debugging.md is moved to Operate > Add custom code
• help.md is merged with troubleshoot.md (was too short to stand on its own)
• consolidate user remarks to users.md
• consolidate logging remarks to logging.md
• enable the "caption" extension and use it for 1 image

Screenshots

Home

Section

Site

https://fenekku.github.io/docs-invenio-rdm/

[fenekku]

From discussions

tldr
More content, and potentially changes to installation would be needed to make this section shine.

Longer version
"Get started" was remarked as having no clear and immediate audience/goal as opposed to other sections. As such I kept "Install" instead. This is not 'yet' ideal, but with some future content changes we can make it work.

Lots of other popular self-hostable software use "Install" as a section header for how to deploy/host the software on your infrastructure.

• Wordpress: Install means host/deploy https://wordpress.org/documentation/category/installation/
• Discourse: Install means host/deploy https://github.com/discourse/discourse/blob/main/docs/INSTALL.md
• Gitlab: Getting started > Install host/deploy https://about.gitlab.com/install/
• Archivespace: Getting started -> Administration > Running with Docker https://docs.archivesspace.org/administration/docker/
• DSpace: Install is more hosting/deploying https://wiki.lyrasis.org/display/DSDOC9x/Installing+DSpace#InstallingDSpace-InstallationOverview

The containerized preview content we have sort of does that. I've done a little more content editing there, but to really make it work, I think we should more clearly recommend/adopt an installation setup (a-la inveniordm-starter from @mfenner ).

This may introduce fuzziness around what goes in Install and what goes in Operate ops. To address that, we should emphasize that the Install section is to get from 0 to 1 instance. The "Operate" section should be about getting that 1 generic instance to your (reader's) personalized instance (both infrastructure wise and feature/customization-wise). It's about fleshing out that 1 instance.

Anyway, I think the content can do for now, but we definitely need more refinement of that as a whole at a project level.

PS:

• the devbox discussion (Add devbox installation method to docs #690) will be addressed separately (we settled on going for a link to awesome-invenio of some kind).

[fenekku]

Included in #779