Uh oh!
There was an error while loading. Please reload this page.
Add logo to HTML docs - #2562
Conversation
brson
commented
Jun 11, 2012
This is a worthy idea but in my opinion the proposed style is not an aesthetic improvement (not that the existing style is attractive to begin with) because it adds too much useless whitespace. It also adds the rust logo to all subpages, so for example For others' reference here's a screenshot: https://imgur.com/BJLkU |
killerswan
commented
Jun 11, 2012
I do think it is an improvement, and I did intend it to show up on the subpages. Compare this with other projects' HTML documentation, which typically includes a logo and much more graphical customization: There are a lot of invasive changes we could make to more comprehensively style the pages, but I think just sticking a simple monochrome logo at the top goes a long way with minimal trouble. It will be trivial for us or other projects to replace or modify this small stylesheet later. |
graydon
commented
Jun 13, 2012
I think if you want to put an em-height logo at the right hand side of the main header or something (more like the size of the python and haskell logos embedded in their pages), that'd be ok. I agree with @brson though that the proposed change chews up too much blank space. |
killerswan
commented
Jun 16, 2012
brson
commented
Jun 20, 2012
That's kind of cute! |
brson
commented
Jun 20, 2012
Thanks for your patience! |
Add flag to specify the number of cpus Apparently you can't rename a branch from github's website without it closing all your PRs with that branch. So this is just rust-lang#2545
Add flag to specify the number of cpus Apparently you can't rename a branch from github's website without it closing all your PRs with that branch. So this is just rust-lang#2545
Document rustdoc frontend CI checks
Document rustdoc frontend CI checks
2562: Fix NavigationTarget ranges r=matklad a=edwin0cheng Fix the issue described in rust-lang/rust-analyzer#2544 (comment) This PR change the order for finding `full_range` of `focus_range` in following orders: 1. map both ranges to macro_call 2. map focus range to a token inside macro call, and full range to the whole of macro call 3. map both ranges to the whole of macro call And fix the corresponding tests and make these tests easily to follow. Co-authored-by: Edwin Cheng <edwin0cheng@gmail.com>

This adds the logo to the HTML versions of the docs, via CSS.
