[Docs] Migrate docs framework to Docusaurus

[anbraten]

closes #254
closes #268
closes #165
closes #255

Note: Some parts are marked with TODO as they are based on ongoing changes from other PRs or I simply don't know what to write at that point 😉. I would suggest to leave them for know and create new PRs updating them later.

Todo

• replace mkdocs with docosaurus (improved menu structure, ...)
• structure docs into Usage and Server Setup / Administration
• update favicon
• Create new pipeline-syntax page with all options and links to more detailed docs if available 🎉 🎉 🎉
• add ci to publish to woodpecker-ci.github.io
• deploy docs preview to surge for review
• update start-page

preview

https://probable-stop.surge.sh

screenshots

required actions by maintainer

• create some bot account for github?
• create some ssh key and save to woodpecker as GITHUB_PRIVATE_KEY

Docs about deploy workflow

[anbraten]

@6543 I updated the docs a "bit" and added some deployment workflow. For that we need some github user with a private ssh key applied to woodpecker to automatically deploy docs. I had the idea that some woodpecker-bot account would be best suited for that.

Could you have a look to the docs cd docs/; yarn install; yarn start.

At the start page we could list some features of woodpecker. What do you think would be suited or should we replace it with something else?

[6543]

Will take me some time

[6543]

what's the difference to docs/static/img/logo.svg and docs/static/img/favicon.svg ?

[anbraten]

what's the difference to docs/static/img/logo.svg and docs/static/img/favicon.svg ?

I don't think there is one. Just replaced the content of the sample files from Docusaurus.