Skip to content
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

Closed
9 of 10 tasks
steveklabnik opened this issue Feb 6, 2017 · 15 comments
Closed
9 of 10 tasks

Tracking issue for RFC 1828: Rust Bookshelf #39588

steveklabnik opened this issue Feb 6, 2017 · 15 comments
Assignees
Labels
A-docs Area: documentation for any part of the project, including the compiler, standard library, and tools B-RFC-approved Blocker: Approved by a merged RFC but not yet implemented. C-tracking-issue Category: A tracking issue for an RFC or an unstable feature. P-medium Medium priority

Comments

@steveklabnik
Copy link
Member

steveklabnik commented Feb 6, 2017

RFC PR: rust-lang/rfcs#1828

Checklist:

infra

porting

extracting

I think this all looks similar to #39917

@steveklabnik steveklabnik added A-docs B-RFC-approved Blocker: Approved by a merged RFC but not yet implemented. A-docs Area: documentation for any part of the project, including the compiler, standard library, and tools labels Feb 6, 2017
@steveklabnik steveklabnik self-assigned this Feb 6, 2017
@steveklabnik
Copy link
Member Author

steveklabnik commented Feb 6, 2017

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

steveklabnik added a commit to steveklabnik/rust that referenced this issue Feb 6, 2017
Clarify and reorganize.

Add the section for the bookshelf. More to come here in the near future!

Part of rust-lang#39588
@tshepang
Copy link
Member

tshepang commented Feb 6, 2017

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

@steveklabnik
Copy link
Member Author

steveklabnik commented Feb 6, 2017

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

frewsxcv added a commit to frewsxcv/rust that referenced this issue Feb 8, 2017
…, 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
frewsxcv added a commit to frewsxcv/rust that referenced this issue Feb 8, 2017
…, 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
bors added a commit that referenced this issue Feb 15, 2017
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
steveklabnik added a commit to steveklabnik/rust that referenced this issue Feb 20, 2017
steveklabnik added a commit to steveklabnik/rust that referenced this issue Feb 21, 2017
This only really moves the files, there's a lot more work coming
in the next commits.

Part of rust-lang#39588.
bors added a commit that referenced this issue Feb 21, 2017
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
steveklabnik added a commit to steveklabnik/rust that referenced this issue Feb 22, 2017
arielb1 pushed a commit to arielb1/rust that referenced this issue Mar 8, 2017
…xcrichton

Extract nomicon to its own repo

part of rust-lang#39588

same as rust-lang#40213 but for the nomicon

r? @alexcrichton
@steveklabnik steveklabnik added A-docs Area: documentation for any part of the project, including the compiler, standard library, and tools and removed A-docs Area: documentation for any part of the project, including the compiler, standard library, and tools labels Mar 10, 2017
@steveklabnik steveklabnik added the P-medium Medium priority label Mar 15, 2017
@steveklabnik
Copy link
Member Author

Docs team triage: p-medium. #40332 and cargo work outstanding.

frewsxcv added a commit to frewsxcv/rust that referenced this issue Mar 17, 2017
…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
frewsxcv added a commit to frewsxcv/rust that referenced this issue Mar 21, 2017
…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
anatol pushed a commit to anatol/steed that referenced this issue Mar 31, 2017
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
anatol pushed a commit to anatol/steed that referenced this issue Mar 31, 2017
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
@Mark-Simulacrum Mark-Simulacrum added the C-tracking-issue Category: A tracking issue for an RFC or an unstable feature. label Jul 27, 2017
@behnam
Copy link
Contributor

behnam commented Aug 12, 2017

A kind of unrelated question here: is there a way to see the https://doc.rust-lang.org/ website for beta and nightly channel? Maybe on a different domain?

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)

@QuietMisdreavus
Copy link
Member

@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 ./x.py doc on the rust repo, and placed in build/$TARGET/doc.

@behnam
Copy link
Contributor

behnam commented Aug 12, 2017

Thanks, @QuietMisdreavus, for the info. So now I know how to test the full docs build locally.

@behnam
Copy link
Contributor

behnam commented Sep 28, 2017

Update on Cargo docs

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

steveklabnik added a commit to steveklabnik/rust that referenced this issue Nov 14, 2017
Fixes rust-lang#44910
Fixes rust-lang#39588

See both of those bugs for more details.
bors added a commit that referenced this issue Nov 16, 2017
 Start shipping the Cargo book

Fixes #44910
Fixes #39588

See both of those bugs for more details.
dlrobertson pushed a commit to dlrobertson/rust that referenced this issue Nov 29, 2018
This only really moves the files, there's a lot more work coming
in the next commits.

Part of rust-lang#39588.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-docs Area: documentation for any part of the project, including the compiler, standard library, and tools B-RFC-approved Blocker: Approved by a merged RFC but not yet implemented. C-tracking-issue Category: A tracking issue for an RFC or an unstable feature. P-medium Medium priority
Projects
None yet
Development

No branches or pull requests

9 participants