I’ve just completed designing a blog for work that is based on WordPress. I’m really pleased with it and will write something when it goes live.
Anyway, the first line in
For those of you who have been using HTML4 or (for whatever reason) XHTML this will seem a bit, well, simple. But I think that’s part of the point of HTML5.
Now, the real benefit of HTML5 will be the introduction of several new tags, including
<nav>, which will add more structural meaning to your HTML documents (which using classes and IDS doesn’t). Unfortunately, it’s going to take some time before all browsers recognise these tags, but there are immediate benefits (besides a simple DOCTYPE), such as the ability to nest block level elements within other block level elements. Which means that
<ul><li><h2> is perfectly acceptable (which, ironically enough, is an invalid construct WordPress likes), and you can even wrap divs in a tags (rsulting in some nice, big link areas).
<!DOCTYPE html> all browsers (including IE6) will render your page in standards mode, which avoids any XHTML confusion. The HTML validator will also attempt to parse your document (HTML5 even accepts both
> closing tags with aplomb), so there’s really no reason to not go ahead and replace the first line in your header template file.
- John Resig on using HTML5 to trigger standards mode
- Jon Tan on preparing for HTML5 (I don’t agree that using classes and IDs adds meaning in the same way as using actual tags, but it’s an excellent overview of the new tags and how they should be used)
- Eric Meyer on using HTML for An Event Apart
- Jens Meiert on some advantages of using HTML5