After coding a few dozen or more forms, it finally occurred to me one day that I was going about form creation the wrong way. Writing the code from scratch for every new form was a pain. So I created a list of the most common form elements that I can copy-n-paste for quick-n-easy forms.

Since reading Andy Clarke's Transcending CSS, I've come to the realization that I'm a slacker. Reading along as Clarke created superb web pages without a solitary div was an eye-opening experience. Not altogether a comfortable one. Because soon after, I had to open up a file of my own HTML markup and confront The Creature.

Writing valid XHTML markup is not really as difficult as it sounds. If you learn a few new rules, you'll be marking up code in valid XHTML in no time. The best way to familiarize yourself with valid markup is to view source on site pages that have passed one of the validation services, such as W3C's Markup Validation Service. Here is a quick rundown of the basics to help you get started.

I ran across this list on the IEBlog while searching for...ahem, cough, uh, a hack. Microsoft offers this "list of common CSS hacks" and says these are the bugs they're ridding the world of in IE7 and that will soon break any pages you've used them on...

One of the most difficult things I've encountered in CSS layouts is footers. They're hard to understand, and even when you do figure them out, that doesn't guarantee you're always going to know how to get them to behave.

Recently I've been in a battle against large, messy, unwieldy style sheets. I always start out so neatly, organizing my rules by selector and carefully keeping track of them. Then sometime around 3 a.m. one morning, the neatness wears off. I can't remember if I've already written a rule similar to what I need, and frankly I've stopped caring. The heck with it, I grumble, let's just write a new rule and toss it in there.

I'm pretty sure I'm writing the longest style sheet in the history of humankind. I'm thinking of submitting it to the Guinness people. Maybe grab myself a slice of fame while I'm still around and kicking. To give you an idea of its size, I'm considering adding a search feature to it.

I had to edit this a little for sense. Apparently, I'm not at my best at 4 a.m.

For designers who are used to tables, the most frustrating thing about CSS isn't learning new markup or memorizing new style rules. No, the most difficult thing is changing the way we think about designing and building pages.

After a short absence due to being buried under, I'm back to say... I finally finished the beta version of my first all-CSS design for a client. Yay! I'm very proud and tired. Here are my initial thoughts about building a "real" CSS site for the first time.

There are so many things to keep track of when you're learning CSS. I've found it helpful to keep similar tips and examples together so I can find them quickly. Here's my "cheat sheet" on images.

All right. I've done it. Sort of. I finally finished my first CSS designed site. It took me two days and half a bottle of Tylenol to accomplish what I used to whip off, half-asleep, in two hours. I also had to apologize to my kids twice and my husband once for snapping at them. I don't foresee my mood improving anytime soon.

Alright. I'm going to do it. I have a mockup due on Monday and I've been dragging my feet for a week, browsing the web for neat design ideas, lurking in forums, reading tutorials, puttering away. I even cleaned my four year old's room today rather than start, so I must really be desperate. However, I finally figured out why I've been procrastinating.

Here's a terrific CSS beginner's tutorial on 456 Berea Street. It's a two-part series on "CSS Tips and Tricks," with a possible part three somewhere down the road. It's one of the best, most succinct tutorials on CSS I've come across. I actually printed the whole thing out and am keeping it on my desk for qui