Something worth noting is that in HTML5 unlike it’s predecessors, you can use h1 for the first header within a new section (an article constitutes as a new section) rather than using the h3 as you have within the article therefore you can now change your example above to have the article shows as:

Implementing new markup is fun.

I can’t believe how excited I am right now.

Related: I like CSS3 too, but Imma let you finish.

I don’t have a footer. This shouldn’t even be here.

I use element selectors in css. They make resets dramatically more useful, for instance (nav ul {list-style:none;} instead of ul {list-style:none;}).

If you meant targeting with js, then you might run into a separate issue since IE has trouble spotting the new elements in the dom, but that isn’t really an issue of id’s vs. element selectors. And there are ways around the issue.

Agree on modernizr. It’s especially helpful with typography.

Couple of quick questions: Do you have a favorite validation service for html5 that you run through? The ones I found seemed a bit clunky. How big of a buzz-saw do you run into if you try to target the new elements directly instead of using their id’s?

btw – modernizr is wicked.

I laughed at the line “Div’s are for suckers.” It’s so freeing to be able to get to elements semantically. Using classes feels kludgy now and using IDs feels like an outright failure!

From browser stats ( http://www.w3schools.com/browsers/browsers_firefox.asp ) I can see that about 83% of firefox users are 3.5 or above, so capable of enjoying @font-face goodness! :)

Of course it’s good to have a tool like Modernizr for a proper fallback!

@font-face – Introduced in Gecko 1.9.1
(Firefox 3.5 / Thunderbird 3 / SeaMonkey 2)

( https://developer.mozilla.org/en/CSS/@font-face )

I love the simplicity of the markup–it’s a whole lot easier to look for an rather than a nested twenty elements deep. My markup has become cleaner, faster and much easier to maintain.

With IE9 touting native support of HTML5, I see no reason to avoid using it, at least in personal projects, with an eye on larger sites going forward. Now if the W3C working group could settle on how to smartly include RDFa (a much better semantic marker than microdata IMHO), we could make real progress not only on the semantic markup front, but the semantic web as a whole.

Browser choice aside, HTML5 sometimes isn’t the most appropriate choice for what I’m building. Sometimes it’s absolutely essential. I’m building something now that could not be done (the same way) with anything but HTML5.

For the time being I’m using the html5 element names as a class structure for my documents. This should make it pretty easy to upgrade sites to html5.