[R4R] New docs V1 (merge master-docs to master)

[gamarin2]

Description

This PR brings to master all the docs changes that have been worked on in the past months. They are accompanied with a new docs website, the release of which is planned to coincide with the upcoming Hub upgrade.

Note that almost all changes included in this PR have already been reviewed in other PRs to the master-docs branch. Here is the list (there's prob more):

• R4R: Docs Cleanup #5246
• R4R - Finish new docs v1 #5186
• R4R: Docs: Building-modules section 2nd part #5037
• Docs fixes #5014
• Add baseapp concept doc #4691

Note:
The new docs build process included in this PR should not break the current docs website. Instead, the new docs should be deployed to docs.cosmos.network. Therefore, it'd be great to merge this PR before end of tomorrow (Tuesday) so that we can test if it works properly. We will do a redirect from cosmos.network/docs to docs.cosmos.network after the Hub successfully upgrades.

Sidenote:
Companion Gaia PR: cosmos/gaia#183

---

For contributor use:

• Targeted PR against correct branch (see CONTRIBUTING.md)
• Linked to Github issue with discussion and accepted design OR link to spec that describes this work.
• Code follows the module structure standards.
• Wrote unit and integration tests
• Updated relevant documentation (docs/) or specification (x/<module>/spec/)
• Added relevant godoc comments.
• Added a relevant changelog entry to the Unreleased section in CHANGELOG.md
• Re-reviewed Files changed in the Github PR explorer

---

For admin use:

• Added appropriate labels to PR (ex. WIP, R4R, docs, etc)
• Reviewers assigned
• Squashed all commits, uses message "Merge pull request #XYZ: [title]" (coding standards)

[alexanderbez]

What is this for? (Note, this renders in markdown).

[gamarin2]

we use that in the website build. I'll see with @fadeev if we can change convention to

<!-- 
--- 
parent:
  order: false
--- 
-->

so that it does not render in markdown

[fadeev]

<!-- won’t work out of the box, because VuePress parses files for --- (this is hard-coded into VP) and then passes them to gray-matter JS-lib for further conversion into JSON.

https://github.com/vuejs/vuepress/blob/master/packages/@vuepress/shared-utils/src/parseVueFrontmatter.ts#L5

Of course, we can comment frontmatter out and strip <!-- and --> at build even with something like sed 's/<!--//g' . That being said, I think we should think about maintainability of all this before we add any more custom things to our markdown files. I’m not saying we shouldn’t (I actually like extending stuff), I just think we should think about it, or we’ll to end up with a hodgepodge of custom syntax parsed with hacky shell-scripts.

[fedekunze]

We should add a link on the docs/README.md to the rendered documentation on the website. I think that suffices (at least for me).

[gamarin2]

Great @fedekunze. Will do so as soon as this PR is merged.

We will think of ways to improve readability of github in later upgrades

[alexanderbez]

fix merge conflict remnants

[gamarin2]

done

[alexanderbez]

ditto. can we avoid this being rendered in markdown?

[gamarin2]

Please see comments above

[fedekunze]

@gamarin2 or @fadeev can we add an entry on the CHANGELOG.md to this docs PR?

[gamarin2]

Done @fedekunze

[alexanderbez]

ACK -- delegating trust to the docs team et al that the contents are correct. Any corrections can be made in subsequent PRs.