The quest for valid XHTML...

by Justin Clarke

Recently I decided for some reason to run my site (also, like the O'Reilly blogs, based on Moveable Type) through the W3C Validator to check to see if I was generating valid XHTML. If you've ever done this, you shouldn't be surprised to find out that my site was anything but compliant. Why is this important? Well, it's probably not going to break most modern browsers as they are quite tolerant of non-compliant code, but it's bad coding - if your code is valid then you should be displayed well by any compliant browser or parser in use. Non-compliant code can also do bad stuff to dual use content, such as if where you're using the web entries to provide RSS feeds for your site.

Some of the things that I wasn't doing correctly included: