Skip to content

<head> description of crates.io confusingly refers to Cargo #1777

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

Closed
shiatsumat opened this issue Jul 1, 2019 · 0 comments · Fixed by #1787
Closed

<head> description of crates.io confusingly refers to Cargo #1777

shiatsumat opened this issue Jul 1, 2019 · 0 comments · Fixed by #1787

Comments

@shiatsumat
Copy link

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.

@sgrif sgrif added the E-easy label Jul 17, 2019
bors added a commit that referenced this issue Aug 7, 2019
Adjust branding to reflect what crates.io actually does

To be clear that crates.io is a Rust package registry&mdash;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.
@bors bors closed this as completed in #1787 Aug 7, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants