Okay, I no longer like css. It seems like every single web page I try to design requires some combination of relative and absolute sizes that is difficult to impossible to achieve in css. For me, anyway.
Basically this means I don't have anything html-y to show for my efforts, but attached is a suggestion for re-organisation of the hierarchical layout based on my interpretation of comments to date :-) Criticism is encouraged, the more constructive the better. Imagine that the XML is the source for an XSL transformation that would generate the html menu, assuming I ever got my styles working. Basic commentary: * I've incorporated Gary's suggestion that the things that people are most likely to want are highest in the list. * I'm not using the /release/latest symbolic link so people's bookmarks (probably to documentation) will stay correct for the version they are using even if a new version is released. ie- the bookmark points to the version they are using, not the 'latest' version. * Old documentation and old releases are available through the archive links, rather than directly from the menu. Still easy to get to, without cluttering up any pages. With regard to the styles side of things, I was trying to incorporate another of Gary's comments and make the click target areas for both the tree expand/contract widgets and the links larger, to make them easier to click, as well as making links more obvious. I also like the idea of somehow marking external links as such, as the CruiseControl website does (I like _that_ part of the site ;-). Bombs away, -- Troy
menu.zap
Description: Binary data
