<div class="gmail_quote">On 14 June 2011 19:05, Brian Granger <span dir="ltr"><<a href="mailto:ellisonbg@gmail.com">ellisonbg@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div id=":1r7">In terms of splitting up the links, I think there are some natural<br>
divisions on links:<br>
<br>
* Internal links to other places on the website.<br>
* Links to the "community": lists, github, wiki, IRC<br>
* Downloads.<br>
* Links to the documentation.<br>
<br>
I think it does make sense to put the internal links in the horizontal<br>
navigation bar, but there could be something else in this horizontal<br>
divider.<br></div></blockquote><div><br>Alright, I'll look into choosing a subset of links to try putting in a navbar.<br> </div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div id=":1r7">
<br>
Currently, these different types of links are all grouped together in<br>
the R panel, which creates a disorganized look. Splitting the R panel<br>
vertically and using visual elements to partition the different types<br>
of links makes sense - not because that is what Sphinx does by<br>
default, but because it organizes the material in a way that helps<br>
users.<br></div></blockquote><div><br>I don't think there are such clear divisions - the wiki is between community and documentation, github is between downloads and community, and the pages on the website are kind of a miscellany - things which don't need to be on the wiki, but don't quite belong in docs, like the FAQ.<br>
<br>At present, I've tried to divide links into a key group - docs, bug tracker, mailing list, and so on, and a secondary group, with a gap between them. Then the downloads and github links were pulled out to sit with the version info at the top. I think subdividing them into more than 2-3 groups will just make it slower to scan through them. I'll see if I can come up with a better arrangement when I try the navbar.<br>
</div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"><div id=":1r7">
This is what I meant to communicate: I don't think the current layout<br>
works technically and aesthetically.<br></div></blockquote><div><br>While there's room for improvement, I'm happy enough with the current layout that I would prefer to build on it rather than reverting to the default Sphinx output and starting afresh.<br>
</div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"><div id=":1r7">
* The width of the content needs to be made smaller than the browser<br>
Window to frame the content. Using an alternate color in the R and L<br>
page margines is one option (what Sphinx does), but we could simply<br>
leave it as white space. With todays wide screen monitors, content<br>
looks awkward if it spans the entire width of the Window - like<br>
reading a book without margins.<br></div></blockquote><div><br>I know, and the width is already constrained, although maybe it should be a bit narrower. The whole thing is limited to 80em, and the main text block to 60em. Obviously whether this fills the window depends on the width of your monitor/window.<br>
</div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"><div id=":1r7">
* We need to use a single font for the entire website, not counting<br>
the one used for the banner. Mixing serif and sans-serif fonts<br>
creates a look that is visually disjoint.<br></div></blockquote><div><br>I'm sure I've seen serif titles used with sans-serif text elsewhere, but I'll admit again that I'm not a designer, and agree to try your suggestion.<br>
<br>I'll fiddle with the layout a bit, and let you know when I've got a preview.<br><br>Thanks,<br>Thomas<br></div></div>