Few CSS Reboot Sites Validate

Sean Fraser from The Elementary Group Standards reveals that more than 70% of the sites participating in the most recent CSS Reboot don’t validate. He provides lots of interesting details, such as the breakdown between XHTML and HTML doctypes, and whether or not the CSS validates.

After installing the HTML Validator extention for Firefox, I managed to confirm that while our upcoming Detroit Diesel redesign is valid, none of our DNN sites validate, due to the extra garbage code that DNN inserts into the rendered pages. Combine that with the horrible editor it comes with, and I’m getting less and less happy with DNN as a solution.

Posted on June 29, 2006. Filed under Uncategorized, , , , , .

Scott Vandehey

By Scott Vandehey, Front-End Web Developer

One Comment on Few CSS Reboot Sites Validate

  1. I’ve been in on a few meetings and some water cooler chat about the problems DNN has been serving up on some projects. Some of the complaints seem a little off base though. I’m not certain that the DNN core is responsible for the extraneous HTML garbage. The skin files and container files are hand written. I’m not aware of anything horrible that’s added by an instance of the Text/HTML module, but I could be wrong here. The HTML editor provided out-of-the-box seems ok for what it advertises. If you want raw HTML access, go for it. We replace the out-of-the-box editor with Telerik, but we don’t have to. While its a top editor in the industry, we could easily use another via the ASP.Net provider model. Whenever you open the WYSIWYG door, something ugly is bound to come out after a while. I’m open minded about alternatives to DNN, but I don’t see the two issues of skins and Text/HTML modules as actual faults of DNN on an XHTML and CSS level. I would expect to see these challenges regardless of DNN.

    Posted on Jul 2, 2006.

    By andrew hay