cleanup of old doc migration files

[4ydan]

Problem

Currently when opening the Mdbook you get greeted with a Changelog.
Also the chapters on the left side are way too many.

The reference below has a sidebar that is barely scrollable.

Our book:

Example1:
https://rust-lang.github.io/mdBook/index.html

Example2: (a bigger left nav bar)
https://doc.rust-lang.org/nightly/reference/

Suggested Solution

• Have an Introduction first page showing either a summary of what there is or duplicate the left side bar for better navigation
• Dont show meeting subchapters
• Dont allow 3 nesting levels (X.X.X is fine but not X.X.X.X)
• Or Create multiple different books(Design, Development, Guidelines, Meetings, Use cases, etc.) each with ther own subpath and own nav bar on the left
• Or split the book in frontend/backend/infrastructure for different teams
• Or fold all chapters per default

[4ydan]

There are also blank pages

[markus2330]

Thank you for creating the issue!

Currently when opening the Mdbook you get greeted with a Changelog.

Why is C ordered before a? Maybe we rename CHANGELOG.md to changelog.md?

Dont show meeting subchapters

I think we can simply remove all old meetings.

Or Create multiple different books(Design, Development, Guidelines, Meetings, Use cases, etc.) each with ther own subpath and own nav bar on the left

I am afraid this will lead to even more duplication and problems where to put what.

Or split the book in frontend/backend/infrastructure for different teams

We already have separate documentation for frontend (storybook), backend (API docu) and infrastructure (private repo). 😉

Or fold all chapters per default

This is an excellent idea. Do you know how to do it?

[markus2330]

There are also blank pages

I hope @temmey can clean them up now after we implemented the hierarchy. (Then we don't need these example migrations anymore).

[4ydan]

This is an excellent idea. Do you know how to do it?

Dont know, can have a look.

[temmey]

There are also blank pages

I hope @temmey can clean them up now after we implemented the hierarchy. (Then we don't need these example migrations anymore).

will be done in #793