Links in root README go to docs.rs site with no filter. Link should include filtered results

[gearama]

How is this relevant to the SDK?

Need help?
For reference documentation visit docs.rs.

[heaths]

That's where all our crates go. Where did you find this? If it's in the top-level docs, we can't link to a specific crate for any crate. You can search for crates from that site, though, just like on npmjs.org, nuget.org, etc. Each crates' README will have a specific link (they do already).

Please clarify in the bug details where you saw this so we can triage appropriately.

[ronniegeraghty]

Searching the repo the Docs.rs homepage link appears in our root README.md twice.
Line 3
Line 40

Since this is in the root README.md it's not really tied to a specific crate. Is there a way to curate a list of crate docs on the site like we do for azure crates on crates.io?

Maybe if the "crates as namespaces" feature lands we can switch this to be the Docs.rs link for the azure crate.

In the meantime, is it better to leave as a link to the Docs.rs homepage or maybe link to azure_core's docs?

My thought is that most people will be using a specific service crate and not using core directly so linking them to core would just mean that have to go back to the homepage then search the crate they are working with.

[RickWinter]

We could have the link go to azure_ so the results are our crates. Unfortunately right now the results are mostly all Previous Version crates.

https://docs.rs/search?q=azure_

[ronniegeraghty]

This would be the link syntax: https://docs.rs/releases/search?query=azure_
The only issue is this shows a lot of crates that are not ours.

[heaths]

That shows way too many crates that aren't us, or that we don't support (track 1s). Let's just remove the generic links to https://docs.rs and keep the specific one in the crates' READMEs.