Source code link looks like a documentation link, causing user confusion

[epage]

Current Behavior

I saw the green "docs" and immediately went to click it, it standing out more than the slightly larger but black headers

I was then confused how I ended up on this page. My first thought was the documentation build was broken. It took me a while to notice the "Documentation" link on the right because that was the opposite of where my eyes were searching for any relevant links to figure out what to do. The recent source code link addition didn't even cross my mind as to how I got there. Even if it had, that still was a road hump in my path to a successful interaction.

Expected Behavior

The main criteria is making the two docs.rs links stand out from each other.

One idea is that instead of header / link, maybe make the headers the link text like on the search results. If people want to know where it goes, they can always hover and have their browser show them.

More ideally, work to integrate crates.io and docs.rs (which I brought up on Internals) so the source code view is just another tab or something.

Steps To Reproduce

1. Go to crates.io
2. Search for a crate (especially if it doesn't have package.documentation set so documentation doesn't show up in the search list)
3. Click on the crate
4. Quickly, without really looking, click on the documentation link

Environment

• Browser: Firefox
• OS: PopOs 24.04

Anything else?

When this was first released, I was confused at the double docs.rs and then noticed the headers.

Today I was trying to get to documentation (didn't remember the exact package name so I started with crates.io) and had this experience.

[epage]

Is there some policy reason that this was moved to a Discussion?

I am not seeing anything about this at either

• https://github.com/rust-lang/crates.io?tab=readme-ov-file#%EF%B8%8F-contributing
• https://github.com/rust-lang/crates.io/blob/main/docs/CONTRIBUTING.md

[epage]

Also, I would feel like the classification as a feature request is incorrect and it is discouraging as a community member to see my own experience navigating the site being treated as a feature request discussion because it makes it feel like this is something that will disappear in the ether.

[Turbo87]

we tend to reserve "issues" for bugs (something not working as designed) and enhancements that are somewhat fleshed out and accepted by the team (i.e. something directly actionable).

[krishkhinchi]

Hi @epage,

Yeah, this is a real UX footgun. The green docs.rs link visually screams “documentation”, but actually drops you into source view, which breaks expectations and causes confusion.

Even a small change like clearer labeling (“Browse source”) or making the headers themselves the links would fix most of this. This feels less like a vague feature request and more like a concrete usability issue with clear impact.

---

If this answer solve your all doubts so can you please mark my answer as solved
or if did not solved yet so please tell me your doubt