Jimmy, there is just no way that Adobe can anticipate how you want to do things.

Yes, <nav> is a new thing under HTML5 and it is more semantic than <div id="nav"> And what happens when you have navigation on both the top of the website and the bottom within a footer, each styled differently?

With CSS3 and HTML5, you can style nav thusly:

nav {

display: block;

text-transform: uppercase;

}

Then do your navigation in HTML

And have a class for nav thusly:

nav .top {

color: #fff;

}

footer nav {

color: #000

}

There, you have black navigation text in the footer, white (where it is presumably going to stand out) on a top navigation. Both are display: block and both transform the text to uppercase.

And Dreamweaver ought not to assume that is what you are going to do—or not. So they're laying out div containers that work with HTML5 and also HTML4. It's not like you can't use anything you used to use in HTML4.

Here's another fun thing you can to in HTML5:

You can style sections and articles. Articles can fit into sections and vice-versa. You can also style aside tags—I'm doing that now. Or, you can just do the stuff you were doing in HTML4 and XHTML in an HTML5 document. And, by the way, it's perfectly legitimate to put Flash into an HTML5 document (gasp!!). One should have a good way for mobile devices to degenerate if one is using Flash in HTML5, though.

I was pointing out that, even though the earliest HTML5 devices (mobile) do not do Flash (especially iOS), you can still put it into the website. I did that as an alternative (in one website) to support older browsers.

I agree, Flash is dead. But it is perfectly plausable to put it into an HTML5 document to support old stuff.