HTML5: The section element

This article is one in a series of brief discussions about the proposed specifications for HTML 5. View the Working Draft for HTML 5 at the W3C.

The section element is a new semantic element. It groups related content. This might be a part or chapter in a book, a section in a chapter, or  anything that had its own heading in HTML 4. Each section may include other new semantic elements such as header and footer, and well as various kinds of HTML elements such as images, paragraphs, list, etc.

The section element essentially replaces the generic container div element, which in past practice has been identified with an id or class attribute for styling purposes. The div element carries no structural meta information with it, however. Presumably, one would now assign ids or classes to sections of the page for styling purposes. As you’ll see in the next example, a page can now have more than one  header and footer element, so the old habit of identifying these parts of a page with an id may be less useful than using class designations or descendant selectors based on the ID of an individual article.

A page could have a number of sections, each with header and footer elements.

Here’s some W3C example code showing how an article (another new semantic element in HTML5) could include some section elements. The code:

<article>
<header>
<h1>Apples</h1>
<p>Tasty, delicious fruit!</p>
</header>
<p>The apple is the pomaceous fruit of the apple tree.</p>
<section>
<h1>Red Delicious</h1>
<p>These bright red apples are the most common found in many
supermarkets.</p>
</section>
<section>
<h1>Granny Smith</h1>
<p>These juicy, green apples and make a great filling for
apple pies.</p>
</section>
</article>

Here’s how that displays, unstyled:

Apples

Tasty, delicious fruit!

The apple is the pomaceous fruit of the apple tree.

Red Delicious

These bright red apples are the most common found in many
supermarkets.

Granny Smith

These juicy, green apples and make a great filling for
apple pies.

The Opera browser, Safari, Firefox, and, to a more limited extent Internet Explorer, support some or most of the HTML5 specifications, including the section element.

One section element can be nested inside another section, in a similar manner to the way div elements are now nested. Or, using the chapter analogy, one section of a chapter might have several nested sections, each with its own header and possibly footer.

See also HTML5: The Doctype Declaration, HTML5: The nav element

HTML5: The nav element

This article is one in a series of brief discussions about the proposed specifications for HTML 5. View the Working Draft for HTML 5 at the W3C.

The nav element is a new semantic element. It is meant for navigation or a table of contents. Each nav may include other  HTML elements, particularly lists of links.  The nav element is meant for blocks of links, not for individual links mentioned in textual content or for links in the footer area of a section or article.

It replaces the concept of a <div id=”nav”> element with a semantic element meant specifically as a navigation area.

As with other new semantic elements in HTML5, there may be more than one nav element on a page. Perhaps global site navigation and secondary level navigation blocks for subsections of a site.  They can be styled with hooks like individual id or class attributes, or using descendant selectors based on where they are nested on the page. The HTML5 replacement for what we have commonly thought of as a sidebar is the new aside element, which is meant to hold content such as the nav element.

Here is sample HTML for a nav element:


<nav>
<h1>The Navigation</h1> <ul>
<li><a href="/">Home</a></li>
<li><a href="/software">Software</a></li>
<li><a href="/support">Support</a></li>
<li><a href="/about">About</a></li>
</ul>
</nav>

The Opera browser, Safari, Firefox, and, to a more limited extent Internet Explorer, support some or most of the HTML5 specifications, including the nav element.

See also HTML5: The Doctype Declaration

HTML5: The DOCTYPE Declaration

This article is the first in a series of brief discussions about the proposed specifications for HTML 5. View the Working Draft for HTML 5 at the W3C.

The DOCTYPE declaration for HTML5 is very simple.
<!DOCTYPE html>

This DOCTYPE declaration can be used for documents that use either HTML and XHTML syntax. It is not case sensitive.

The proposal currently includes “legacy” DOCTYPES for software that expect a DOCTYPE to include either a PUBLIC or SYSTEM identifier, and is unable to omit them. That is,
<!DOCTYPE html SYSTEM "about:legacy-compat">

In this example, the about:legacy-compat must be in lowercase. It can be use with either single or double quotes.

The W3C states that no DOCTYPE is needed with XHTML, however, if you use one it must be in a form like the second example given.

The Opera browser, Safari, Firefox, and, to a more limited extent Internet Explorer, support some or most of the HTML5 specifications, including the simplified DOCTYPE declaration.

Useful Links: Aviary, What not to do on Facebook, HTML5 Cheat Sheet

5 Things You Can Do with Aviary Screen Capture at Web Worker Daily gives a good summary of a new feature of Aviary. I’ve written about Aviary before in Updates on Aviary and An Early Look at Aviary.

In case anyone in your life or classroom needs a reminder that everything you say and do on the Internet can come back to haunt you, here’s a little morality story to that effect. Wife blows MI6 chief’s cover on Facebook. Well, hmmm, didn’t Facebook just make a big announcement about changes to their Privacy Policy—guess she missed the news.

Smashing Magazine put together a nice handout for your classroom. An HTML5 Cheat Sheet in PDF format.

Useful links: WaSP OWEA announcement, HTML 5,

Introducing the Open Web Education Alliance at WaSP’s Buzz page. See also The Big Reveal for a link to the public mailing list for this group. Follow news on the group on Twitter @waspinteract.

html5doctor is a new group blog working to bring information about the proposed specs for HTML 5 to the masses. They encourage questions from readers about what it all means.

Useful Links: Online Lectures, CSS3 modules, the canvas element, menu possibilities, Boagworld

Be a better teacher, look at some proposed CSS3 modules, see some use cases for the canvas element, menu system tests, and an interview with Aarron Walter. More. . .

100 Free Online Lectures that will make you a better teacher is from Best Universities, which is amassing some intresting link resources such as this one on its blog.

Four new W3C modules for CSS3 are in the proposal stage and would support the canvas element. Links to each module are availble here, at CSS3.info.

Speaking of the canvas element, Laura Carlson put together some Use Case examples on the ESW Wiki. If you have a browser other than Internet Explorer, you can take a look at some of the possible uses of the canvas element.

Project Seven is testing a new menu system which is very exciting in terms of the design possibilities it may open up.

Boagworld interviewed Aarron Walter this week. Paul gave Aarron a chance to talk about how the WaSP InterAct came into being, where it’s going next and what it means.