You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When you access https://crates.io, you find that the <title> says "Cargo: packages for Rust" and the description says "cargo is the package manager and crate host for rust" whereas at the top of the page it says "crates.io — Rust Package Registry".
I believe that the package host (crates.io) and the package manager (cargo) should be now distinguished clearly (although they can be linked together), so I would like the description of https://crates.io to be properly updated.
The text was updated successfully, but these errors were encountered:
Adjust branding to reflect what crates.io actually does
To be clear that crates.io is a Rust package registry—in fact the _default_ crate host for Rust---this commit changes the `name`, `short_name`, and `description` fields in the manifest to reflect the nature of the project. crates.io isn't really "Cargo", so it seems logical to me to not mention much about it, at least in the metadata for the site.
I also more explicitly mention that `crates.io` is the "default" package registry to be a bit more neutral; it's the baked-in default in Cargo, but there are others out there. I got the branding "Rust Package Registry" from the tagline in the visible top bar on the landing page.
Also, update the various acceptance tests that I found floating around.
Should resolve#1777, I think.
When you access https://crates.io, you find that the <title> says "Cargo: packages for Rust" and the description says "cargo is the package manager and crate host for rust" whereas at the top of the page it says "crates.io — Rust Package Registry".
I believe that the package host (crates.io) and the package manager (cargo) should be now distinguished clearly (although they can be linked together), so I would like the description of https://crates.io to be properly updated.
The text was updated successfully, but these errors were encountered: