Configurator for and Infopage about Collective Infrastructure

Is your feature request related to a problem? Please describe.
If I start a project/collective, I need to setup a bunch of infrastructure for all members to share: e.g. Talk channel(s), Deck(s), Calendar(s), Adressbook(s), ...
The people and the folder for all the files is just the most basic stuff.

Describe the solution you'd like
There should be a page (or page snippets for the start page) available and initially filled, where all the potentially interesting stuff can be easily accessed.
It should cover the stuff for the members of the collective to know what is available and to easily jump to it (in the web UI) and integrate it into their devices (e.g. for the collectives calendar).
A config page (or integrated links to the respective configs) were I find all the links to the configurations of the above elements would also be helpful.

Maybe an easy solution would be a start page for a collective that is automatically created at creation of the collective with all the potential stuff in it (depending on what is installed in this Nextcloud instance). This page can then be edited. Everything that is not needed can be thrown out and other stuff (maybe external, e.g. Wiki, Accounting SW, ...) added. It even would be easy this way to cut/paste the stuff to other subpages. Macros/Templates could further simplify the editing.

Describe alternatives you've considered
Creating it manually is possible for more tech-savvy creators of collectives. But it is cumbersome, takes time, and is potentially error-prone (if missing manual maintenance after any changes in the system).

Additional context
It would probably be helpful for every new collective to speed up the ramp-up phase and on-board new members.

The issue identifies no files, tests, or entry points; begin by mapping how a collective is created and how its start pages and installed-app links are represented. Done would require an agreed scope and an automatically created, editable infrastructure page with configuration links, but the proposal does not define those details.