Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Revamp of the documentation #1

Merged
merged 6 commits into from
Jun 11, 2023
Merged

Revamp of the documentation #1

merged 6 commits into from
Jun 11, 2023

Conversation

samricotta
Copy link
Contributor

@samricotta samricotta commented May 7, 2023

closes part of: cosmos/cosmos-sdk#15705

This closes the main parts of the above issue including:

  • Moving the documentation to a new repo
  • Landing page
  • Redesigning the categorisation of the documentation
  • Separating developer and user sections and adding validation and vision
  • Aligning with additional user journeys

The following parts will happen in additional PRs

  • Versioning
  • Deleting the current docs from cosmos/cosmos-sdk
  • Copying over changes from any changes in cosmos/cosmos-sdk using github workflows

Note: This PR must be merged last.

@samricotta samricotta marked this pull request as ready for review May 10, 2023 08:21
sidebar_position: 1
---

# Architecture Decision Records (ADR)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this should stay in the sdk repo

@@ -0,0 +1,42 @@
---
sidebar_position: 0
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this should stay in the sdk

sidebar_position: 1
---

# Requests for Comments
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ditto

@@ -0,0 +1,60 @@
# Specification of Modules

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ditto with this folder

@samricotta samricotta mentioned this pull request May 10, 2023
@julienrbrt
Copy link
Member

Agree with the comment Marko made above, and I would add the tooling documentation needs to stay in the SDK repo as well (so only some of the tooling).
The easy way to know what should stay in the SDK repo is to look at pre.sh: https://github.com/cosmos/cosmos-sdk/blob/117a426/docs/pre.sh. Everything that is copied must still live in the SDK repo, and be copied at build time here.

@samricotta
Copy link
Contributor Author

samricotta commented May 10, 2023

Thanks @julienrbrt ! I personally believe it should all be in one place, just had a chat to marko (so the above comment is ood) and I'm going to try the following. Im working on a script that copies over any MD files that have had changes and replaces the same existing MD files on this repo using a GitHub Actions workflow which is triggered on any deployment in the main sdk repo.

@julienrbrt
Copy link
Member

julienrbrt commented May 10, 2023

Thanks @julienrbrt ! I personally believe it should all be in one place, just had a chat to marko (so the above comment is ood) and I'm going to try the following. Im working on a script that copies over any MD files that have had changes and replaces the same existing MD files on this repo using a GitHub Actions workflow which is triggered on any deployment in the main sdk repo.

I see, so it won't be removed from the SDK right? If so that makes sense as well.

@samricotta
Copy link
Contributor Author

They wont be removed, those files will remain but also live in this repo

Copy link
Member

@julienrbrt julienrbrt left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we have a PR with only the category and the docusaurus config and the action?
This is harder to review otherwise, my Google Chrome literally crashes viewing the diff.

This way there is as well a working base in the repo.

It would be nice as well if it can be configured simply without domain, so we can compare both website simultaneously (the current docs.cosmos.network and this one, at cosmos.github.io/cosmos-sdk-docs or another subdomain like docs-beta.cosmos.network)

- run: yarn build

- name: Deploy to GitHub Pages
uses: peaceiris/actions-gh-pages@v3
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We should use the same action as in the SDK: https://github.com/cosmos/cosmos-sdk/blob/main/.github/workflows/deploy-docs.yml
There is no need to hardcode such thing in the action.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes to all the above, ill make those changes !

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we have a PR with only the category and the docusaurus config and the action? This is harder to review otherwise, my Google Chrome literally crashes viewing the diff.

just to be clear you mean the category.json right?

name: Deploy to GitHub Pages
runs-on: ubuntu-latest
env:
CROWDIN_PERSONAL_TOKEN: ${{ secrets.CROWDIN_PERSONAL_TOKEN }}
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What token is that?

# https://github.com/actions/checkout/issues/13#issuecomment-724415212
# The GH actions bot is used by default if you didn't specify the two fields.
# You can swap them out with your own user credentials.
cname: docs.cosmos.network
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This should be a file called CNAME at the root of the GH-pages branch

go.mod Outdated
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This file should be deleted.

Copy link
Member

@julienrbrt julienrbrt left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

tACK, pending a few changes (gh actions and unnecessary go.mod)

- name: Build 🔧
- run: yarn install --frozen-lockfile
- run: yarn crowdin:sync
- name: Clean Crowdin Front Matter issues
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What is Crodwin and what is that clean.sh script?
It isn't present in the repo.
From what I can see it is for translations? Given that the website is in english, I do not think we need this.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah its just something specific from docusaurus, ill remove

with:
node-version: "16.x"

# npm install npm should be removed when https://github.com/npm/cli/issues/4942 is fixed
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
# npm install npm should be removed when https://github.com/npm/cli/issues/4942 is fixed

- main
paths:
- "docs/**"
- "x/**/*.md"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
- "x/**/*.md"

There is no x folder here.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For compatibilities issues, we really need to keep the redirections working. Many website depends on it, and it is even in governance proposal.
This can definitely be done in a follow-up, but all redirections present in the docusaurus config in the SDK should as well be ported there.
Moreover, redirections should be set from all the links that have changed from the current docs version to this version.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah i thought I mentioned in the description that the redirects section will be added to the versioning PR. So that piece of work will be added there. Thnx for checking up tho

@samricotta samricotta merged commit b2b498a into main Jun 11, 2023
samricotta added a commit that referenced this pull request Jun 11, 2023
* wip

* Update glossary

* review updates

* update actions

* remove path

* Update deploy-docs.yml
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants