Broken link to "guide text" (rendered style guide) in RFC 2436-style-guide
Nobody has claimed this yet.
- Dominant language
- Markdown
- Stars
- 6.6k
- Forks
- 1.7k
- Avg merge
- 16h 14m
- Merged PRs (30d)
- 1
Description
Under https://rust-lang.github.io/rfcs/2436-style-guide.html#guide-level-explanation there is a link to "guide text", which points to https://rust-lang.github.io/style-guide/README.html - however I get HTTP 404 when trying to follow it. Neither I was lucky with https://rust-lang.github.io/style-guide/ or other variants.
The link probably wants to point to a rendered version of https://github.com/rust-lang/rfcs/blob/master/style-guide/README.md - but I was unable to find a rendered version of this anywhere on the net. (there is another repo which contains the same style guide https://github.com/rust-dev-tools/fmt-rfcs/blob/master/guide/guide.md - but probably the version here in rust-lang/rfcs is the canonical one?)
This might be the reason the style guide is not easily discoverable. Searching "rust style guide" currently still shows the old https://doc.rust-lang.org/1.0.0/style/README.html most prominently.
(I was not at all sure where to file this issue, please feel free to direct me at the correct place; I chose this repo because https://rust-lang.github.io/rfcs/ appears to be generated from it.)
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the “guide text” link in RFC 2436’s guide-level explanation and compare it with rust-lang/rfcs/style-guide/README.md. Verify the generated rust-lang.github.io destination for the style guide, then update the broken link and check that the rendered RFC points to an existing page.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- markdown
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100