Hello Corey, Thanks for your work on this. The live search is especially welcome.
> The relative weights of fonts on the page don't correspond to their > importance. That is, the "TUTORIAL | MANUAL" bit is the largest, boldest, > most whitespaced piece of the page but they're only links you're really > looking for when you first open the docs, not something you need at the > forefront > when you're digging into the details of some random function. That was my first impression as well, possibly because of the contrast with the manual and Github interfaces. I'd suggest lightening the font weights and sizes in general. Regards, Rob. On 12 August 2013 17:20, Corey Richardson <co...@octayn.net> wrote: > On Mon, Aug 12, 2013 at 12:15 PM, Evan Martin <mart...@danga.com> wrote: >> I love that there are cross-references within the code snippets. It's great >> to be able to quickly look up what a trait means. I noticed that "prelude" >> in the discussion on http://seld.be/rustdoc/master/std/index.html isn't a >> link, is that easy to make work or is it too Javadoc-y to need to mark up >> cross references in free text like that? >> > > Sure, a plugin could implement this. It would not be very easy, > though, it'd need to hook into `resolve`, which I don't know how to > do. > >> >> Speaking of the prelude, I noticed that these docs, like the old rust docs, >> don't say anything in the prelude. Is that possible to fix? That was one >> of the first places I wanted to skim when I was trying to get a handle on >> the language. >> > > As I said, documentation of `pub use` (which is all the prelude > consists of) is the last missing piece of functionality. > _______________________________________________ > Rust-dev mailing list > Rust-dev@mozilla.org > https://mail.mozilla.org/listinfo/rust-dev _______________________________________________ Rust-dev mailing list Rust-dev@mozilla.org https://mail.mozilla.org/listinfo/rust-dev
