Brandon Frohs

Even if you’ve never created a website in your life, you can notice a few major things about the WHATWG’s website.

1. Their blog, which is powered by WordPress, is using the default theme with no noticeable changes.
2. Their FAQ/Wiki, which is powered by MediaWiki, is using the default theme with no noticeable changes. Even the logo looks like it was thrown in there in a hurry. It’s a nice white square with absolutely no transparency. Five seconds would have made it look much more professional.
3. Their forum, which is powered by PHPBB, is using the default theme with no noticeable changes. Once again, they just threw in their logo.

I understand that they would like to rely on a well-tested application rather than a custom build alternative, but can’t they at least make the pages flow together a bit more? It really isn’t that time consuming. I installed and set up this blog (custom theme/widgets/plugins) in one night. So, in 3 nights, they could customize the look and feel of the entire site and make it look less like it was just thrown together. This would help people to take their standard a bit more seriously. Well, that along with ignoring backward compatibility. Just tell people not to use it for 5 years. After the 5 years, browsers should be up-to-date. If they aren’t, I won’t feel bad when people abandon them because their favorite websites don’t work correctly.

I remember when I first learned of the work being done on (X)HTML5. I had mixed emotions toward the entire project. Although I’ve been a fan of Firefox, Opera, and Apple for a long time, I don’t agree with the direction they’re going with (X)HTML5. Along with the creation of the Web Hypertext Application Technology Working Group (or WHATWG) came the return of the slow progression of HTML.

As a designer/developer, I believe (X)HTML5 is a step backward in the development of the primary web language. One of the major reasons for the creation of (X)HTML5 was the fact that many of the websites on the WWW didn’t switch to well-formed XHTML. They blame website owners, but I blame the major browsers (Internet Explorer, Firefox, Opera, and Safari). It may just be a pet peeve, but I’ve always used well-formed HTML. Even before I knew XHTML existed, I was putting quotes around all of my attributes. I’ve also always used lowercase tag and attribute names. When I began using XHTML, closing empty tags made perfect sense. What doesn’t make sense is why others don’t follow suit. And I just can’t get myself to believe that browsers refuse to conform to a standard that’s been around for years.

Read more…