iWeb, the new tag soup generator
Ok so I’m a little late to this because of my recent connection problems, but I can’t not say anything about it: I’m seriously disappointed by the markup Apple’s iWeb generates. It is the tag soup generator of 2006.
I haven’t played with iWeb myself, but after reading Todd Dominey’s iWeb’s HTML markup. Not so good. and Mike Rundle’s iWeb-Generated Source Code is Awful, and taking a look at the example sites they created, I don’t want to.
The code iWeb spits out is on par with that of a certain commercial CMS I have taken a closer look at recently. In fact, all that inline-CSS makes them look quite similar. It’s so bad I would have preferred Apple to be honest and just use tables and spacer GIFs instead. Valid markup does not necessarily equal good markup.
A few examples:
<div class="paragraph Title_Red" style="line-height: 31px; padding-bottom: 0pt; padding-top: 0pt; ">
<div class="paragraph Body" style="line-height: 20px; text-decoration: none;"> </div>
<div style="background: transparent; border: 1px #000000 none; float: none; margin: 0px; vertical-align: top; height: 41px; left: 40px; position: absolute; top: 61px; width: 620px; z-index: 1; " id="id3"><div><div><div style="margin: 4px; "><div class="paragraph Date" style="line-height: 34px; padding-bottom: 0pt; padding-top: 0pt; ">Wednesday, January 11, 2006</div>
Wow. That’s quite impressive.
After reading the comments on Todd’s and Mike’s posts I am amazed by the number of people coming up with excuses for the shoddy markup this application generates. No, iWeb is not meant for web professionals, but that kind of makes it even more important for it to generate decent markup since the people who use it won’t be doing anything to clean things up. Yes, iWeb is at version 1.0, but Apple should be able to do better than this. Anybody should.