On Mon, 19 Mar 2007, Kake L Pugh wrote:
Sorry, I didn't explain myself very well. What I
mean is: why do you
care about people who want to put the categories/locales somewhere else,
but not about people who want to put the help links somewhere else, or
people who want to put the Tools somewhere else, or etc etc?
If you want to put categories AND locales somewhere else BUT the same
somewhere else, life is significantly easier if they share the same
parent, and nothing else does.
So, Dom and I have added a div with a special id around the pair of them,
but still leaving them within navbar. That way, they will sit in the
navbar by default, but if you wanted to put them elsewhere (but together),
it's very easy to do.
Even if that is the case (I don't know enough CSS
to tell), judging by
existing Guides, nobody seems to want to do this anyway.
I want to do it for the cotswolds openguide. I just need to find 5 minutes
to tweak the css I've got that does that (now a few of the ids and classes
have changed), then I can put it live.
Who was it that asked for it?
We did some useability testing on the cotswolds guide, and the lack of an
easy way to get from a node page to the most commonly used locales and
categories was identified as a failing. When we tried a few designs for
where to put those lists, we found that having them next to the navbar, in
a 3rd column, worked well for a lot of designs.