Yay, webmonkey! I loved it back in the day, and when just puttering around for some CSS quick fixes was quite frustrated by dead links that ended there.

Jon, did you get a chance to poke at the nesting of the containers of the main_left panel?

Sorry, no, not yet. I did update the voting page though! :)

No problem. I'm just about to dive into what Deena wrote--do you have a framework page to drop that into?

do you have a framework page to drop that into?

Sorry, no, not yet. I did update the voting page though! :)

From looking at it, Deena, I think it could stand to be dumbed down a bit in the beginning, and I'm wondering if we shouldn't tidy up buffista.css a little. Not in any huge way, in any way that should break anyone's custom CSS. Just to make it more legible.

Like saying

body {
text-align: center;
background-color: #fff;
min-width: 700px;
font-family: verdana, tahoma, arial, sans-serif;
}

instead of

body {
text-align: center;
background: #fff;
min-width: 700px;
font-family: verdana, tahoma, arial, sans-serif;
}

Making all our hex codes 6 digits long.

Adding comments.

You know, polite stuff. And we should definitely link to it from both the CSS entry page and the how-tos.

I agree, ita. background-color, especially, threw me. I'll ease into it a little slower and send you a new version tomorrow.

Yeah--there's some shorthand there, and it's doing no one any favours. Why don't you assume that there won't be any shorthand in it, and I'll take it out? And then maybe Jon can verify I actually accomplished it.

Also consider that I think there should be a separate page that describes containers (better terminology than block, IMO, since block has an explicit CSS meaning) both in general HTML ( t div and t span and the like) as well as our own classes and IDs and styles. So hopefully we won't be pushing people down the view source pathway.

Okay ita, I can do that.

Sounds like a plan.