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

docs: update master docs #8353

Merged
merged 11 commits into from
Feb 23, 2021
Merged

docs: update master docs #8353

merged 11 commits into from
Feb 23, 2021

Conversation

lovincyrus
Copy link
Contributor

@lovincyrus lovincyrus commented Jan 16, 2021

Description

Ref: cosmos/vuepress-theme-cosmos#91

/master

  • bump docs theme
  • add v0.40 to config.js versions

closes: #XXXX

  • to fix error Error rendering /core/cli.html: false when npm run build

Before we can merge this PR, please make sure that all the following items have been
checked off. If any of the checklist items are not applicable, please leave them but
write a little note why.

  • 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
  • Review Codecov Report in the comment section below once CI passes

@okwme
Copy link
Contributor

okwme commented Jan 17, 2021

Will this make v0.40.0 the default version as well @lovincyrus ?

@okwme
Copy link
Contributor

okwme commented Jan 19, 2021 via email

@clevinson
Copy link
Contributor

This PR only adds the dropdown handle for v0.40, but the actual http://docs.cosmos.network/v0.40/ site is broken, and docs have not been able to build on circleci for the past few weeks. Can we make sure that the v0.40 docs are successfully deployed before merging this? Otherwise, the dropdown will lead to a dead page.

@alessio
Copy link
Contributor

alessio commented Jan 21, 2021

Bump @lovincyrus (CC'ing @fadeev for visibility)

@lovincyrus
Copy link
Contributor Author

lovincyrus commented Jan 21, 2021

Just ran the latest of release/v0.40.x branch locally and deployed the build folder on Netlify and Vercel. Everything looks fine.

Netlify: https://release-v0-40-x-docs.vercel.app/intro/overview.html
Vercel: https://release-v0-40-x-docs.lovincyrus.vercel.app/intro/overview.html


and docs have not been able to build on circleci for the past few weeks. @clevinson

RE: Circleci

gh-pages
  - /master
  - /v0.39
  - /v0.40

Just deployed gh-pages on Vercel: https://cosmos-sdk-gh-pages.vercel.app — It works.

Not sure what went wrong to the v0.40 dir. Can we somehow redeploy the gh-pages branch? @marbar3778

DNS: https://mxtoolbox.com/SuperTool.aspx?action=http%3a%2f%2fdocs.cosmos.network%2f&run=toolpage

For some reason, it's still showing AmazonS3. Didn't we update the DNS of docs and point it to https://cosmos.github.io/cosmos-sdk? cc: @helder-moreira @marbar3778

Update: https://docs.cosmos.network/v0.40's DNS has been updated and it's now using Github pages.

@lovincyrus
Copy link
Contributor Author

I will go ahead and convert this PR to a draft until http://docs.cosmos.network/v0.40/ is not dead. #8353 (comment)

@lovincyrus lovincyrus marked this pull request as draft January 21, 2021 02:14
@lovincyrus
Copy link
Contributor Author

There's a deadlink that causes build error:

https://github.com/cosmos/cosmos-sdk/blob/master/docs/core/cli.md#L99

Here is an example of a `queryCmd` aggregating subcommands from the `simapp` application:

+++ https://github.com/cosmos/cosmos-sdk/blob/0.40.0/simapp/simd/cmd/root.go#L99-L121

Could we update that @amaurymartiny 💯

Once that's resolved, this PR is ready to merge.

@amaury1093
Copy link
Contributor

Could we update that @amaurymartiny 💯

Sure, can I just push this fix to this branch? (or would you like to do it?)

@lovincyrus
Copy link
Contributor Author

Sure, can I just push this fix to this branch? (or would you like to do it?)

Either way works. Feel free to just push to this branch.

@lovincyrus lovincyrus marked this pull request as ready for review January 26, 2021 17:13
@amaury1093 amaury1093 added T:Docs Changes and features related to documentation. A:automerge Automatically merge PR once all prerequisites pass. labels Jan 28, 2021
@@ -38,6 +38,10 @@ module.exports = {
index: "cosmos-sdk"
},
versions: [
{
"label": "v0.40",
"key": "v0.40"
Copy link
Contributor

Choose a reason for hiding this comment

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

Now that the v0.40 has been kind of yanked, should we just show v0.39, v0.41 and master?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

if we don't plan on using v0.40, then we shouldn't include it in the version dropdown. Can you confirm that? @amaurymartiny

Copy link
Contributor

Choose a reason for hiding this comment

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

confirmed

Copy link
Contributor

Choose a reason for hiding this comment

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

Question about this. A recent bugfix (#8461) makes 0.40.* and 0.41.* buggy for ALL chains except gaia. Maybe in the docs we should just skip 0.40 and 0.41 altogether? And show 0.42 directly?

cc @clevinson

Copy link
Contributor

Choose a reason for hiding this comment

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

Or actually, for 0.41, it would be ideal to show a banner on top of the page saying "if you're not using the hub, please upgrade to 0.42". wdyt?

Copy link
Contributor

Choose a reason for hiding this comment

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

Yes i like this approach. Let's only show docs for v0.41 and v0.42, and have v0.41 clearly point out that there is an evidence bug on v0.41.x that renders chains unstable on v0.41.x if they have a non-default bech32 prefix.

Copy link
Contributor

Choose a reason for hiding this comment

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

@lovincyrus can we update this accordingly & merge? This should also include then an update to the versions file, as we now have a release/v0.41.x branch, and most stargate docs updates will only be be backported to there.

Copy link
Contributor Author

@lovincyrus lovincyrus Feb 22, 2021

Choose a reason for hiding this comment

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

only show docs for v0.41 and v0.42

Are we only showing v0.41 and v0.42 and get rid of v0.39 and master from the version dropdown?

nvm, just saw this #8353 (review)

@okwme
Copy link
Contributor

okwme commented Jan 29, 2021 via email

@lovincyrus
Copy link
Contributor Author

lovincyrus commented Feb 6, 2021

would be good to actually move to the top left, i think it's very hard to see it in the current location and typically docs list this above the left side menu, right?

Docs typically list this on the top right nav bar.

image

References:

@lovincyrus
Copy link
Contributor Author

There's some problems when it shows "master" in the URL it doesn't work and is shown as blank.

If you're referring to http://localhost:8080/master when you run it locally on this branch, that's expected because we don't have /master in the docs dir. The docs are deployed from this branch.

image

@okwme
Copy link
Contributor

okwme commented Feb 6, 2021

I'd submit vuejs.org as a counter example for putting the version in the top left but what i think really makes me look to the top left is seeing so many gitbooks which also default to that spot (example). This is not a hill I'll die on, but those are my two cents.

What I am more concerned with is making sure its visible and correct.

When the URL doesn't match the path it shows up as empty. I think we have some options with customized routing rules (not sure if we're using netlify or github at this point) but I don't know how the routing rules interact with this dropdown. Just know that I've come to the site through various paths and realized it wasn't correct. I'm sure you've considered this before Cyrus and I'd be keen to hear your opinion on what should happen that could be useful as a guiding light in the hunt to find all edge cases where it's not happening. (bonus points if we come up with a system that is flexible on jumps to semver since we're basically foresaking v0.40.x in favor of v0.41.x)

@amaury1093 amaury1093 mentioned this pull request Feb 22, 2021
9 tasks
Copy link
Contributor

@amaury1093 amaury1093 left a comment

Choose a reason for hiding this comment

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

Any updates on this? imo the ideal solution would be:

  • dropdown showing 0.39, 0.41, master, defaulting to 0.41 (no strong opinion on top-left or top-right)
  • not mention 0.40 in the docs

@tac0turtle
Copy link
Member

This is blocking getting modules onto atlas.

@lovincyrus
Copy link
Contributor Author

I'll focus on cleaning up the version dropdown in this PR. Regarding the position of version dropdown, I've created an issue cosmos/vuepress-theme-cosmos#189. Let's move our discussion there and submit another PR next time.

Copy link
Contributor

@clevinson clevinson left a comment

Choose a reason for hiding this comment

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

👍 @lovincyrus thanks!

Let's make sure this gets backported to launchpad/backports and release/v0.41.x as well.

I think mergify should be able to take care of this now?

@amaury1093
Copy link
Contributor

thanks @lovincyrus !

@mergify mergify bot merged commit 4c70268 into master Feb 23, 2021
@mergify mergify bot deleted the cyrus/master-docs branch February 23, 2021 10:57
mergify bot pushed a commit that referenced this pull request Feb 23, 2021
* bump docs theme to 1.0.180

* add v0.40 to config.js versions

* Fix code snippet link

* reorganize order of versions
* 0.39, 0.41, master
* defaulting to 0.41

Co-authored-by: billy rennekamp <billy.rennekamp@gmail.com>
Co-authored-by: Amaury Martiny <amaury.martiny@protonmail.com>
Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>
(cherry picked from commit 4c70268)

# Conflicts:
#	docs/package-lock.json
@amaury1093 amaury1093 mentioned this pull request Feb 24, 2021
6 tasks
alessio pushed a commit that referenced this pull request Feb 24, 2021
* docs: update master docs (#8353)

* bump docs theme to 1.0.180

* add v0.40 to config.js versions

* Fix code snippet link

* reorganize order of versions
* 0.39, 0.41, master
* defaulting to 0.41

Co-authored-by: billy rennekamp <billy.rennekamp@gmail.com>
Co-authored-by: Amaury Martiny <amaury.martiny@protonmail.com>
Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>
(cherry picked from commit 4c70268)

# Conflicts:
#	docs/package-lock.json

* rm package-lock.json, reinstall

Co-authored-by: Cyrus Goh <hello@lovincyrus.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A:automerge Automatically merge PR once all prerequisites pass. T:Docs Changes and features related to documentation.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants