-
Notifications
You must be signed in to change notification settings - Fork 212
Idea: Show small badge to jump to newest version #57
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
Comments
Location: I was thinking it wants to be on every single documentation page, not just the crate root (again thinking of the case when you arrive through some external link or old bookmark). Maybe top right corner, above the Platform selector and the description? (Looking at this page as a random example (page)) |
I doesn't have to be those particular "badges". Just text with some background color to make it stand out just a small amount. |
I see. Let me see what I can do without breaking page's minimalistic style and default look and feel. |
Yeah that looks great |
Maybe more "Last version" than "Recent version". Or maybe something "you are seeing an outdated version, here to see the last" |
Since we got #58 I am planning to show only version number and a dropdown menu to all versions and if version isn't the latest version I will show it orange. |
This is a crucial feature since old crate versions’ docs are placed high on google already. |
That looks perfect! |
New narrower docs.rs header is very good, too. |
Thanks a lot for implementing this! |
Imagine you're browsing the slightly outdated docs of some project: https://docs.rs/regex/0.1.75/regex/
There could be a small badge that's visible in that case (maybe yellow or orange) that lets you jump to the current version (“Version 0.1.77 is the most recent release”).
It's important for this feature that the badge is not shown if you're already at the newest release.
Versioned links are going to be very useful, but this could be a small help if you have users arrive to stale docs via old links without them being aware of it.
The text was updated successfully, but these errors were encountered: