Hi Terence, > Seeing your other message on your upgrade, one of the more non-obvious > changes is that there's an additional <div class="dokuwiki"> that > might fix some of the problems you're having... I did notice that and was trying to work that it. I think I'm still missing the principle here, though, so I'm not sure how I *should* proceed. Should I be redefining the div.dokuwiki stuff? Why is all the CSS selected for under div.dokuwiki? What is supposed to go outside of div.dokuwiki? Adding div.dokuwiki to my CSS did help a bit, but I'm wondering if I should have gone the other way and further isolated my CSS classes from the dokuwiki ones, so I don't have this div.dokuwiki overlap. For now I'm doing whatever gets things working fastest. It would be nice to see a splitbrain page describing the CSS class philosophy, outlining the suggested way to customize it. > http://chrispederick.com/work/webdeveloper/ What an amazing tool! I'm solving problems lickety-split. Mostly it's been a case of my classes aren't being used at all and the dokuwiki ones are, or the dokuwiki classes are being applied after mine are (due to more specific selectors). The option showing me all the CSS on the page was a bit overwhelming though. I really don't think that page needs that much CSS. I guess trying to factor things out better and dyamically assemble the CSS would be a bit too overwhelming. Thanks for the pointers. I now love Firefox twice as much as I did before. ~joe -- DokuWiki mailing list - more info at http://wiki.splitbrain.org/wiki:mailinglist