Tracking issue for RFC 1828: Rust Bookshelf

[steveklabnik]

RFC PR: rust-lang/rfcs#1828

Checklist:

infra

• Create a landing page for the bookshelf. Re-write the doc index page #39593

porting

• Pull mdbook into tree and port the nomicon and book to it Port books to mdbook #39633
  • enable linkchecker for the books Reenable linkchecker for books #39976 (prereq: Update mdbook version #39966)
• Port the reference to mdbook Port the reference to mdbook #39855
• Create a new "Nightly Book" in-tree. Create the Unstable Book #39866

extracting

I think this all looks similar to #39917

• Pull the book out of tree into rust-lang/book Extract book into a submodule #40332
• Pull the nomicon out of tree Extract nomicon to its own repo #40222
• Pull the reference out of tree Move the reference into a submodule #40213
• Pull the cargo docs out of tree and convert them to mdBook. Pull the cargo docs out of tree and convert them to mdBook cargo#4040
• Publish cargo book as part of Rust. Publish Cargo Manual on the bookshelf #44910

[steveklabnik]

@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.

[tshepang]

@steveklabnik Will 2nd edition be moved elsewhere when 1st edition moves to rust-lang/book?

[steveklabnik]

@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.