feat: migrate to docusaurus

[julienrbrt]

Description

Migrates to docusaurus (PoC). Long living PR, migrating when I have actual time.

TODO

• move folders and documentation at the right place
• create components for {prereq}, {synopsis} ...
• create components for having a similar look as current homepage
• resolve +++ for displaying code snippet (https://github.com/saucelabs/docusaurus-theme-github-codeblock)
• update theme to match current SDK colors
• have docusaurus know to resolve relative links containing .md.
• update pre.sh / post.sh for adding modules specs
• runpre.sh / post.sh at build
• versioning of old versions
• add redirects (keep the old redirects, and redirects all links from docs.cosmos.network documentation tracking #11898)
• update deployment documentation
• update makefile build-docs
• update github action (/dist folder instead of /output)
• verify all links

Inspiration

• https://github.com/ignite/cli/blob/develop/docs/docusaurus.config.js
• https://github.com/osmosis-labs/docs/blob/main/docusaurus.config.js
• https://github.com/InterWasm/docs/blob/main/docusaurus.config.js

Then

• We can delete this image: https://github.com/cosmos/images/tree/main/website-deployment

---

Author Checklist

All items are required. Please add a note to the item if the item is not applicable and
please add links to any relevant follow up issues.

I have...

• included the correct type prefix in the PR title
• added ! to the type prefix if API or client breaking change
• targeted the correct branch (see PR Targeting)
• provided a link to the relevant issue or specification
• followed the guidelines for building modules
• included the necessary unit and integration tests
• added a changelog entry to CHANGELOG.md
• included comments for documenting Go code
• updated the relevant documentation or specification
• reviewed "Files changed" and left comments if necessary
• confirmed all CI checks have passed

Reviewers Checklist

All items are required. Please add a note if the item is not applicable and please add
your handle next to the items reviewed if you only reviewed selected items.

I have...

• confirmed the correct type prefix in the PR title
• confirmed ! in the type prefix if API or client breaking change
• confirmed all author checklist items have been addressed
• reviewed state machine logic
• reviewed API design and naming
• reviewed documentation is accurate
• reviewed tests and test coverage
• manually tested (if applicable)

[alexanderbez]

WTF is docusaurus lol?

[julienrbrt]

WTF is docusaurus lol?

A tool to render our documentation, in replacement of vuepress. This PR is a PoC to see if docusaurus is suitable for us.

Basically everyone moved from vuepress to it (osmosis, cosmwasm, ignite).

[julienrbrt]

This is R4R. I will work on the GitHub fetch extension in a follow-up PR (https://github.com/saucelabs/docusaurus-theme-github-codeblock does not work).
Currently, only the main documentation will change, but v0.45 and v0.46 will still be using vuepress.
I'll gladly have this merged before 0.47, so we can have 0.47 use docusaurus as well (as the directory structure will be the same, which makes it super easy to version).

[alexanderbez]

@julienrbrt how does one review this PR?

[tac0turtle]

@julienrbrt how does one review this PR?

yolo ack

we should merge it here or in its own repo

[julienrbrt]

I am for merging here, as for versioning we can copy the docs/ folder and the sidebar from the branch nicely at build time. Moreover, the naming of the file is important for the ordering.
But yeah, for reviewing you go on docs.cosmos.network as I have already deployed it accidentally 😅 (it should have gone in my fork, but I forgot to use the right remote)

[alexanderbez]

YOLO ACK 🦖