Restructure documentation

[ch1bo]

Why

The documentation is currently quite fragmented and not consistent between user and developer documentation.

To improve upon this, we want to analyse and test a different structure with improved user journey / experience.

What

As a first step we outlined a better distribution of sections in this sitemap draft:

• Create a branch with an outline matching what is currently in the draft
• Meet with tech writers Monday 2024-03-18
• Create / move pages according to outline, but only with placeholders content with one sentence "what this page will be about"
• Meet again to speak about the landing page
• Implement the documentation changes
  • Try that prominent entry pages (according to our analystics) are still using the same URL or are redirected

Maybe out of scope / follow-up

• Adopt / integrate a provided landing page design + content

[ch1bo]

Drafted and discussed this clustering today and added some notes / aiken inspiration to the landing page:

Current changes on https://github.com/input-output-hk/hydra/tree/docs-restructure

[ch1bo]

Collected new landing page contents (at IOG) in this document: https://docs.google.com/document/d/1CvwS_aGJlzQcJbeRp-F_jAJ3TytF1WbLUJ1yaKsoIbM/edit#heading=h.qd4d3g5btn2t

We'll be looking for someone creative at IOG or independent to design a landing page (markup + stylesheets) around this.

[ch1bo]

Started work on this, some more sub-tasks to keep track off

• Convert demo to tutorial
• Provide a good intro to /docs
• Simplify installation & configuration in docs
• Groom how-tos
• Complete intro to /docs/dev
• Remove glossary
• (optional?) Convert coding standards to ADR-like blog?
• (optional?) Convert testing strategy to docs page
• (optional?) Add media pack