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

No obvious way to find changelogs for previous versions #6627

Open
wesleytodd opened this issue Apr 8, 2024 · 17 comments
Open

No obvious way to find changelogs for previous versions #6627

wesleytodd opened this issue Apr 8, 2024 · 17 comments
Labels
accessibility Issues concerning accessibility design good first issue Issues for newcomers help wanted

Comments

@wesleytodd
Copy link
Member

Enter your suggestions in details:

I see I can click the link for "this version" but that is in a modal with no obvious url to visit it directly or link to it. It also means even if I know the version I am looking for I cannot even edit a URL for it. Ideally IMO that link would load a whole new page, not a modal but if not that I think we should make it really easy to find all changelog links.

@wesleytodd
Copy link
Member Author

Looks like the click was intercepted and a cmd-click did open in a new window. That said, I think my "obvious" comment stands as an improvement recommendation.

@AugustinMauroy AugustinMauroy added accessibility Issues concerning accessibility design labels Apr 9, 2024
@Jay-Karia
Copy link
Contributor

@wesleytodd

Node.js full changelog can be found in it's GitHub repo: https://github.com/nodejs/node/tree/main/doc/changelogs

Should we consider making a new page for changelogs which can link to the repo?

@wesleytodd
Copy link
Member Author

There used to be a link to the individual change logs for a version from the downloads page. The problem with the current modal window is it doesn't update the browser url, so it is harder to share.

Specifically this link (which now I apparently cannot cmd-click to get a new tab):

Screenshot 2024-08-05 at 10 41 45 AM

Additionally on this, I think that we regressed a few UX things related to finding the metadata for versions. There used to be a single link to view this page: https://nodejs.org/dist/

I used that link all the time, and I dont see anything linking to it anymore. IIRC it used to say something like "other download options" or something?

@ovflowd
Copy link
Member

ovflowd commented Sep 10, 2024

Specifically this link (which now I apparently cannot cmd-click to get a new tab):

Because it is not a link, just a modal. Ultimately, the blog post should suffice if you want a shareable link.

Additionally on this, I think that we regressed a few UX things related to finding the metadata for versions. There used to be a single link to view this page: nodejs.org/dist

For the end user, there's no point seeing nodejs.org/dist; Very few users would know what is what and what to download. That's why each tab has specific download methods for what they might be searching for; It's like throwing them at a huge Netflix catalog (pun not intentionally intended) versus showing them "series we recommend for you"

I used that link all the time, and I dont see anything linking to it anymore. IIRC it used to say something like "other download options" or something?

The closest to this, which remains true is

image

On the "Prebuilt binaries" tab, as they are all Prebuilt binaries. I'm definitely open for suggestions :)

@wesleytodd
Copy link
Member Author

wesleytodd commented Sep 10, 2024

Because it is not a link, just a modal. Ultimately, the blog post should suffice if you want a shareable link.

No I dont want a blog post though lol. I want the changelog. I use this to find and debug issues, not just learn about the release. I often find the specific thing I think is broken and run a node version right before it to check. I really would like to make the case for bringing back links to a full page change log view for the release, even if that just links to GH.


Sorry early send.

For the end user, there's no point seeing nodejs.org/dist; Very few users would know what is what and what to download.

Yeah but I use it. I use it for all sorts of things, like checking on my phone which versions of things ship with what (I do support for folks, and sometimes and doing it from my phone). I agree most users dont need it, but for those of us that do I think a small link makes sense.

@ovflowd
Copy link
Member

ovflowd commented Sep 10, 2024

No I dont want a blog post though lol. I want the changelog. I use this to find and debug issues, not just learn about the release. I often find the specific thing I think is broken and run a node version right before it to check. I really would like to make the case for bringing back links to a full page change log view for the release, even if that just links to GH.

You are aware the changelog is embedded on the blog post, right? It is even more complete there, in general.

@wesleytodd
Copy link
Member Author

Sure, but I dont want to read or find it in there. I want the plain old changelog which still exists and was always available easily from that link. Ideally I have the running changlog so I can search through all releases for keywords. Like this is the link I need and I usually dont want to go digging in the GH repo for it. https://github.com/nodejs/node/blob/main/doc/changelogs/CHANGELOG_V22.md

@ovflowd
Copy link
Member

ovflowd commented Sep 10, 2024

Yeah but I use it. I use it for all sorts of things, like checking on my phone which versions of things ship with what (I do support for folks, and sometimes and doing it from my phone). I agree most users dont need it, but for those of us that do I think a small link makes sense.

Then just go nodejs.org/dist -- why should this link be listed on the website? 😅 again, your use case is very specific.

@wesleytodd
Copy link
Member Author

your use case is very specific.

I dont see this being only a me thing. But I am not going to die on this hill.

@ovflowd
Copy link
Member

ovflowd commented Sep 10, 2024

Sure, but I dont want to read or find it in there. I want the plain old changelog which still exists and was always available easily from that link. Ideally I have the running changlog so I can search through all releases for keywords. Like this is the link I need and I usually dont want to go digging in the GH repo for it. nodejs/node@main/doc/changelogs/CHANGELOG_V22.md

We never had a changelog button. https://web.archive.org/web/20180308115257/https://nodejs.org/en/download/

@ovflowd
Copy link
Member

ovflowd commented Sep 10, 2024

your use case is very specific.

I dont see this being only a me thing. But I am not going to die on this hill.

Can you prove to me this is something other people used? Our designs are backed by data on what people clicked or not. We recorded thousands of user sessions via Sentry and still record and actively monitor engagement and people's actions.

I'm not saying I triple-checked that now, but that back then, we made these decisions conscious with said data. I can double-check if it was actively used, but I doubt.

@ovflowd
Copy link
Member

ovflowd commented Sep 10, 2024

Again, it's not something to die on a hill for, but just the more links and the more things we add to the website, the more confusing it can be for an end-user. Our website is targeted at the absolute rookies who have no idea what they are doing -- and needs to be tailored so that it is safe for them to go around, and that gives them confidence.

A link to "All download options" that goes to a default "no index" directory listing... It is the opposite of that.

Regarding the changelog button, it was used somewhat, but only on the homepage. What I can do here for you, @wesleytodd, is add a link to changelog on GitHub within the modal that we open, or we can use regular a' elements, but by default clicking on it opens the modal (onClick`) and then all other commands should still work, like open on a new tab, copy link, etc. Would that work for you? And if yes, which option is desirable? A link on the modal or the modal itself being a link?

@wesleytodd
Copy link
Member Author

Regarding the changelog button, it was used somewhat, but only on the homepage. What I can do here for you, @wesleytodd, is add a link to changelog on GitHub within the modal that we open

This sounds like a great place to put it. I agree and totally understand your data driven approach, and don't mean my report here to be enough to counter that decision. I honeslty thought maybe others were wanting the same thing so figured it was better open the issue. If that is not the case, fine, but I do think this proposal you made is a good middle ground.

@ovflowd
Copy link
Member

ovflowd commented Sep 10, 2024

No worries, again, I could be wrong as these decisions were done a time ago.

Ill proceed with the middle ground approach for the changelog.

But I won't be adding a button to go to nodejs.org/dist

@ovflowd ovflowd added help wanted good first issue Issues for newcomers labels Sep 11, 2024
@bmuenzenmeyer
Copy link
Collaborator

@wesleytodd As part of fixing #7060 I wondered if https://nodejs.org/en/about/previous-releases#looking-for-latest-release-of-a-version-branch suffices.

It's such a simple question I thought I'd ask before we go too much further down another path.

@J-dev740
Copy link

J-dev740 commented Oct 3, 2024

Hi @wesleytodd I think I can work on this issue, can you assign it to me

@wesleytodd
Copy link
Member Author

@bmuenzenmeyer, that is a great improvement. I still think it would be great to just make that modal go away entirely because it is not linkable. It is generally BAD UX to not have something you can link to that is as important as a change log. I would love if someone like @J-dev740 took it on and could make it a normal page with a url like any other.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
accessibility Issues concerning accessibility design good first issue Issues for newcomers help wanted
Projects
None yet
Development

No branches or pull requests

6 participants