-
Notifications
You must be signed in to change notification settings - Fork 2.6k
Generate table of contents for docs at http://doc.crates.io #2694
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
Comments
I like this idea a lot. I think I like the second version better. |
YES love it!! Just to be clear, in the 2nd mockup, the TOC would be |
Yes, that's exactly what I meant ( |
When it comes to cargo docs, I'd vote for this to have the highest priority. The current cargo docs layout has serious usability issues and having a TOC would help a lot. In fact, I'd much rather see cargo docs mimic https://doc.rust-lang.org/book, which makes it much easier (still not ideal, but definitely miles ahead compared to what we have here) to get around and get to the necessary bits. |
Good news! That's exactly the plan, it's just that there's only so much time and not very many people contributing towards this goal at the moment. |
That is indeed good news, thanks for the info. |
Related: #4040 |
This think this can be closed now. The cargo docs now use mdbook, and thus have a sidebar TOC. |
Indeed! |
It would be nice to have TOCs for documentation articles. TOC gives a summary of topics an article addresses and allows to quickly navigate between sections.
How it can be implemented
Place some marker (e.g.
%TOC%
) in a Mardown file:% Cargo Guide Welcome to the Cargo guide. This guide will give you all that you need to know about how to use Cargo to develop Rust projects. %TOC% # Why Cargo exists ...
Use some tool (first hit in google, actually works) to generate TOC.
Replace the marker with the generated TOC.
Mockups
Simple TOC:
Fixed ("sticky") sidebar TOC:

The text was updated successfully, but these errors were encountered: