-
Notifications
You must be signed in to change notification settings - Fork 12.8k
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
Tracking issue for RFC 1828: Rust Bookshelf #39588
Comments
@brson @alexcrichton can we coordinate soon on getting this implemented? We had talked very broadly about it before, now it's time to get concrete 😄 Some of this is blocked by #39431, I believe, which is the blocker for using mdbook to build. The rest of it is blocked on being able to integrate the out-of-tree stuff into the builds. |
Clarify and reorganize. Add the section for the bookshelf. More to come here in the near future! Part of rust-lang#39588
@steveklabnik Will 2nd edition be moved elsewhere when 1st edition moves to rust-lang/book? |
@tshepang the idea is that they will both be in the same repository. The exact strategy isn't totally clear; we'll see as we dig into packaging implementation details. I am imagining sub-folders. |
…, r=frewsxcv Re-write the doc index page Clarify and reorganize. Add the section for the bookshelf. More to come here in the near future! Part of rust-lang#39588
…, r=frewsxcv Re-write the doc index page Clarify and reorganize. Add the section for the bookshelf. More to come here in the near future! Part of rust-lang#39588
Port books to mdbook Part of #39588 blocked on #39431 As a first step towards the bookshelf, we ~vendor mdbook in-tree and~ port our books to it. Eventually, both of these books will be moved out-of-tree, but the nightly book will rely on doing the same thing. As such, this intermediate step is useful. r? @alexcrichton @brson /cc @azerupi
This only really moves the files, there's a lot more work coming in the next commits. Part of rust-lang#39588.
Port the reference to mdbook Part of #39588. This is only a work in progress. Still left to do: - [x] double check contents weren't duplicated/lost with the move to individual pages (I'm going to do this) - [x] fix up links [and footnotes](#39855 (comment)) (@frewsxcv has volunteered to help with this) - [x] change `src/doc/reference.md` to redirect to the book - [x] move the reference on the doc index to be part of the bookshelf
…xcrichton Extract nomicon to its own repo part of rust-lang#39588 same as rust-lang#40213 but for the nomicon r? @alexcrichton
Docs team triage: p-medium. #40332 and cargo work outstanding. |
…ichton Extract book into a submodule Part of rust-lang#39588 We probably don't want to land this till after the beta branches on friday, but would still ❤️ a review from @alexcrichton , since I am a rustbuild noob. This pr: 1. removes the book 2. adds it back in as a submodule 3. the submodule includes both the old book and the new book 4. it also includes an index page explaining the difference in editions 5. it also includes redirect pages for the old book URLs. 6. so we build all that stuff too. r? @alexcrichton
…ichton Extract book into a submodule Part of rust-lang#39588 We probably don't want to land this till after the beta branches on friday, but would still ❤️ a review from @alexcrichton , since I am a rustbuild noob. This pr: 1. removes the book 2. adds it back in as a submodule 3. the submodule includes both the old book and the new book 4. it also includes an index page explaining the difference in editions 5. it also includes redirect pages for the old book URLs. 6. so we build all that stuff too. r? @alexcrichton
Port books to mdbook Part of rust-lang/rust#39588 blocked on rust-lang/rust#39431 As a first step towards the bookshelf, we ~vendor mdbook in-tree and~ port our books to it. Eventually, both of these books will be moved out-of-tree, but the nightly book will rely on doing the same thing. As such, this intermediate step is useful. r? @alexcrichton @brson /cc @azerupi
Extract book into a submodule Part of rust-lang/rust#39588 We probably don't want to land this till after the beta branches on friday, but would still ❤️ a review from @alexcrichton , since I am a rustbuild noob. This pr: 1. removes the book 2. adds it back in as a submodule 3. the submodule includes both the old book and the new book 4. it also includes an index page explaining the difference in editions 5. it also includes redirect pages for the old book URLs. 6. so we build all that stuff too. r? @alexcrichton
A kind of unrelated question here: is there a way to see the https://doc.rust-lang.org/ website for I'm asking to understand how I can actually see the changes when working on migrating Cargo docs to the Bookshelf. (rust-lang/cargo#4040) |
@behnam All the releases and release channels have subfolders on doc.rust-lang.org. So nightly is on https://doc.rust-lang.org/nightly/ and beta is on https://doc.rust-lang.org/beta/. Whenever you link the cargo docs in with the rest of the rust docs, the full doc bundle is made when you run an |
Thanks, @QuietMisdreavus, for the info. So now I know how to test the full docs build locally. |
Update on Cargo docsWe are done with preparing the Cargo docs in book format, which was rust-lang/cargo#4040 I have filed #44910 for the next steps. We can add this to the list in the description here. |
Fixes rust-lang#44910 Fixes rust-lang#39588 See both of those bugs for more details.
This only really moves the files, there's a lot more work coming in the next commits. Part of rust-lang#39588.
RFC PR: rust-lang/rfcs#1828
Checklist:
infra
porting
extracting
I think this all looks similar to #39917
The text was updated successfully, but these errors were encountered: