MeyerBros

i wrote the code for the new world arts site way back in the day, before i knew much about css layout or semantic markup. it includes one table and loads of poorly named classes (several of which should be IDs). while the text-file database system for events is fairly robust (for a text-file events database), the front end isn’t nearly as tightly coded.

today we got a lesson in that - the hard way. our css file was lost and has to be rebuilt.

with the beauty of css i rebuilt the front page structure farily quick - cursing the poorly named sections, the entirely unnecessary table and the general mess of spans serving for strong and em tags - pausing every other line to hack through markup code for the right names to reference. from there i was lost. the back pages use different names and structures and none of the styling markup makes any sense at all.

let that be a lesson to me. this page, for example, i could rebuild to look decent in minutes without even looking at the html code. it’s simple, it all makes sense, and it’s entirely flexible.

This entry was posted on Tuesday, August 15th, 2006 at 3:00 pm by eric and is filed under web design, geeky, css, web standards. You can follow any responses to this entry through the RSS 2.0 feed. Both comments and pings are currently closed.