Eat Your Own Cooking

It's funny, but I really haven't used CSS that much over the past years. I've always kept up to speed -- it was one of those things you look at and go, "Oh. That's easy. You just set all the properties in one place"
But in actuality, using Front Page or .NET as a programming environment, I just clicked on the properties page and set things the way I wanted. Oddly enough, this is just the type of behavior that I dislike when I see people doing it in Microsoft Word -- use the styles! Makes for a much better document.
Now that I'm running the blog on a hosted Linux account, the templates that came with it all use CSS extensively. Since I already "knew" CSS, how hard could it be? Tell me something, how many death-march projects have you been on where it all started with somebody saying "How hard could it be?"
"Build a rocket, put a couple guys in it, shoot it up to the moon. How hard could it be?"
Somewhere between the theory and implementation of CSS, however, I have said some ugly things about various people in the computer industry. The "Cascading" is definitely a tricky part -- woe be unto anyone in a large, complex CSS environment. I would not want that job.
Adding a little pain and agony to the pot is IE's inconsistent implementation of CSS. "hover" seems to work on elements, but not other behaviors. "Float" does all sorts of weird and strange things. I could go on, but it's all inside baseball.
So I've re-done the site, used something new, and learned a bit. Now if I could only find the Tylenol. And yes, the heading is too big (and the bottom of the page looks awful) But you probably won't notice. Those users, always causing problems for the rest of us! (grin)