Improve documentation

[hlxid]

Description

Currently the Wiki is just in this repo and should be moved into a separate repository just like the one of ChatOverflow.
It should also be built by a GitHub Actions and be hosted by GitHub Pages.

Progress

• Move docs to new repo
• Create gh actions workflow for automatic deployment
• Create gh actions workflow for automatic generation of dependency tree and services file
• Restructure the wiki
• Add a guide for contributing to the wiki
• Review all existing pages to make sure they are well structured and easy to understand.
  Add clarifications where needed.
• Use extensions (like admonition) to improve the overall style and look
• Make it MINZIG

[J0B10]

Do you want to do this?
Otherwise I would love to have a look at it as I'm already familiar with the process and it would be a perfect task I could do.

[hlxid]

Sure, you can do it @joblo2213. You probably have more experience working with mkdocs than I do.

[LarsVomMars]

Why wouldn't you simply serve the docs/ folder instead of creating an extra repo?

[sebinside]

Separation of concerns 😜

[J0B10]

Added a prorgess checklist including my further plans for the wiki

[J0B10]

Still wondering if we should add a markdown linter.
Generally I realy like the idea of having a linter that looks for style issues in the files, I only wonder how well it works together with mkdocs and the extensions.

Stuff that could be usefull:

• https://github.com/DavidAnson/markdownlint
• https://github.com/igorshubovych/markdownlint-cli
• https://github.com/xt0rted/markdownlint-problem-matcher

[hlxid]

I would also like a markdown linter, if it works fine with mkdocs.

The numbering in some sample bundle guides is currently off.
Here is the discord service guide as an example:

There the last both should be 6 and 7, but they both restart counting at one.