On Tue, 2011-02-22 at 10:59 +0000, Ian Dickinson wrote: > Hi all, > I've been playing a bit with how we can get a balance of useful > navigation support from the Jena site while retaining use of the Apache > CMS ... which is rather limiting. Since we've not agreed to any of this > yet, I've done my experiments outside the svn, and put the prototype here: > > http://www.iandickinson.me.uk/jena/about/index.html > > This uses a fairly simple two-level navigation hierarchy: major sections > in the top menu, sub-sections on the left. Since one of the main > problems with the CMS is that the same page skeleton and navigation > SSI's are used on every page, I've added some javascript to manage the > complexity. With Javascript and CSS enabled, each page should show > feedback on the currently selected section and page, and only the > section sub-menu relevant to the current section (hiding the long list > of other section pages). With Javascript turned off, the navigation > still works but readers dont' get the "you are here" feedback or the > simplified menus.
Looks good to me. The quick links part of the side bar is useful and gives a way of addressing the various bits that people want to have "easy to get to" but not necessarily separate top level sections. Aesthetically (he says, wary of starting a long discussion) it mostly works really well. I especially like the side bar and overall page layout. There's something about the top bar that clashes a little for me - I'd be inclined to try having the tabs round both top corners and the blue bar with flat top corners. I see the occasional slight flicker when switching sections, no big deal. It would be nice if the sections could start as hidden then get revealed by the javascript but can't see a way to do that that is robust against no-js. > One other suggestion from Dave that I implemented was to include script > to move a "table of contents" from a given page into the navigation > menu. This is illustrated in the in_depth/ontology section (you can see > the before/after by looking at the page source). Seems to work nicely. > I've loosely based the structure on current suggestions around the IA, > but it's by no means complete: this was just a quick prototype to test > one way of getting what we need from the CMS, and there's a limit to the > number of times I was willing to create lorem ipsum pages :) http://www.lorizzle.nl/ for some alternative lorem ipsum :) > I've tested this on firefox 3 and chromium (which manifested an annoying > out-by-one pixel bug I've tried to mask as best I could). Feedback on > whether it works on other browsers would be welcome. Works fine under chrome (no surprise given it works with chromium). Dave
