Define documentation strategy

[Taucher2003]

The current documentation page uses Astro preconfigured with Starlight. This setup is causing problems:

• The build is hacked together with a bash script as each page build actually consists of multiple Astro builds that get merged together
• Things like the dev server are not properly usable because we can't get the full page with a single Astro build

We have multiple options going forward:

• Stay with Astro and work around the problems we currently have
• Evaluate Fumadocs
• Evaluate Hugo
• Develop something ourself using pictor

[nicosammito]

We will use Fumadocs in the future

[Taucher2003]

The Fumadocs project switcher will be used for separate projects and in there, we will separate the Usage, Administration and Development sections.