12th July, 2004

Call yourself a web developer?

Let’s take a close look at a popular blog and it’s sins. I won’t hold back here. Sketchy image-replacement, an overdose of div tags, extraneous class declarations, improper use of phrase elements, flickering roll-overs, barely semantic.

It validates as transitional XHTML, but then that hides a multitude of sins. Seems the site was launched in a rush, resulting in tired and heavy code. The site needs work. Dare I name the offending developer? I suppose I should.

It’s me.

I admit it. I’m not perfect, and neither is CollyLogic’s XHTML. So, after an enlightening trawl through Dan Cederholm’s new book, I have begun the great repair job. All the action is currently taking place on one test page, and I’ve already implemented a plethora of changes, creating considerably more semantic code, and shaving kilobytes off the page size in the process.

Keep an eye on the testing page.

The testing page carries more details of what’s been done so far, and what the next steps will be. Eventually, I’ll implement the changes site-wide, and will be detailing all the key changes made to the markup, outlining the benefits of each move. You can plot the progress on the test page, and drop some comments here if you need to bring my attention to something. In the meantime, don’t you dare judge me by the current markup, darn you!

Prev / Next


If you enjoyed this article, please subscribe to my Internet of Natural Things letter, and maybe grab the RSS feed. Thank you.