Sent by Russ Baldwin on 30 July 2004 08:08
I agree with Marcus, if you need to keep a single menu for a lot of pages
then putting the 'active menu' into the body tag seems like a good option.
You can then pump the same menu into all your pages, either via
pre-processing or via server side includes and merely alter the body tag for
each page. The only downside of this approach is that if you use meaningful
words in your body tag and have a big site you may well run out of words!
and perhaps would be better numbering them line page1/page2 etc - not so
stylish but it may be more practical?
I just had a second thought, which perhaps is more to do with accessibility
than anything else. In the above approach for example, if you have a really
big nested list for a menu, then someone may have to plough through this on
every page in their speech browser - 'there are 500 links etc' This may or
may not be a good thing :) Perhaps section menus with just the top heading
for all sections and the links to the current section may help here, you can
still use the same idea for the body tag mark-up and the relevant CSS.
Slightly off topic - sorry, but this is the way we use lists and css for
menus on larger sites.
Russ
______________________________________________________________________
css-discuss [EMAIL-REMOVED]]
http://www.css-discuss.org/mailman/listinfo/css-d
List wiki/FAQ -- http://css-discuss.incutio.com/
Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
