-
Notifications
You must be signed in to change notification settings - Fork 3.8k
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
docs: update master docs #8353
Conversation
Will this make v0.40.0 the default version as well @lovincyrus ? |
Hmm, i’d maybe include progressively and leave warnings on the pages
they’re not up to date. With the announcement I think a lot more people are
looking ti the docs and expecting it to be the place to learn what’s going
on.
On Mon, Jan 18, 2021 at 11:24 AM Amaury ***@***.***> wrote:
***@***.**** commented on this pull request.
------------------------------
In docs/.vuepress/config.js
<#8353 (comment)>:
> + {
+ "label": "v0.40",
+ "key": "v0.40"
+ },
just a note: I'd say 0.40 docs are 90% done, however, a lot of them are
not on the release/v0.40.x branch yet, and need to be backported (will
happen most likely in this week and next week).
If you think it'd be better to wait until all docs are updated on
release/v0.40.x first, we can also wait a bit for this PR.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#8353 (review)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAHLLVEWX6XYFZDE4E4QPBDS2QD7PANCNFSM4WEZDTLQ>
.
--
billyrennekamp.com
|
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. |
Bump @lovincyrus (CC'ing @fadeev for visibility) |
Just ran the latest of Netlify: https://release-v0-40-x-docs.vercel.app/intro/overview.html
RE: Circleci
Just deployed Not sure what went wrong to the v0.40 dir.
DNS: https://mxtoolbox.com/SuperTool.aspx?action=http%3a%2f%2fdocs.cosmos.network%2f&run=toolpage
Update: |
I will go ahead and convert this PR to a draft until |
There's a deadlink that causes build error: https://github.com/cosmos/cosmos-sdk/blob/master/docs/core/cli.md#L99
Could we update that @amaurymartiny 💯 Once that's resolved, this PR is ready to merge. |
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. |
docs/.vuepress/config.js
Outdated
@@ -38,6 +38,10 @@ module.exports = { | |||
index: "cosmos-sdk" | |||
}, | |||
versions: [ | |||
{ | |||
"label": "v0.40", | |||
"key": "v0.40" |
There was a problem hiding this comment.
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?
There was a problem hiding this comment.
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
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
confirmed
There was a problem hiding this comment.
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
There was a problem hiding this comment.
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?
There was a problem hiding this comment.
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.
There was a problem hiding this comment.
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.
There was a problem hiding this comment.
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)
ja!, also would be good to fix so that it is automatically selected.
There's some problems when it shows "master" in the URL it doesn't work and
is shown as blank. Also 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?
…On Fri, Jan 29, 2021 at 11:59 AM Amaury ***@***.***> wrote:
***@***.**** commented on this pull request.
------------------------------
In docs/.vuepress/config.js
<#8353 (comment)>:
> @@ -38,6 +38,10 @@ module.exports = {
index: "cosmos-sdk"
},
versions: [
+ {
+ "label": "v0.40",
+ "key": "v0.40"
Now that the v0.40 has been kind of yanked, should we just show v0.39,
v0.41 and master?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#8353 (review)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAHLLVELLN52THSYUKAO52DS4KIJXANCNFSM4WEZDTLQ>
.
--
billyrennekamp.com
|
Docs typically list this on the top right nav bar. References: |
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. |
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 |
There was a problem hiding this 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 to0.41
(no strong opinion on top-left or top-right) - not mention
0.40
in the docs
This is blocking getting modules onto atlas. |
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. |
* 0.39, 0.41, master * defaulting to 0.41
There was a problem hiding this 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?
thanks @lovincyrus ! |
* 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
* 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>
Description
Ref: cosmos/vuepress-theme-cosmos#91
/master
closes: #XXXX
error Error rendering /core/cli.html: false
when npm run buildBefore 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.
docs/
) or specification (x/<module>/spec/
)godoc
comments.Unreleased
section inCHANGELOG.md
Files changed
in the Github PR explorerCodecov Report
in the comment section below once CI passes