HTML and CSS Reference
In-Depth Information
<h2>Recent comments</h2>
<ul> ... </ul>
<h2>blah blah</h2>
<a href=”...”>Web hosting by LovelyHost</a>
<img src=”...”>
<p>Powered by <a href=”...”>WordPress</a></p>
<p><a href=”...”>Entries (RSS)</a> and <a href=”...”>
¬ Comments (RSS)</a></p>
Note that the “Blah blah” section is not marked up as <nav> , as
the link to my web host, a picture of me, and two RSS links are
not “sections that consist of major navigation blocks” as the
spec defi nes <nav> . It's wrapped in a <section> in order that
the sidebar headings remain the same level in the outlining
algorithm (see Chapter 2 for more). Another way to mark up this
sidebar would be to use one single over-arching <nav> rather
than multiple <nav> elements. As any feline taxidermist will tell
you, there is more than one way to skin a cat.
The <footer> element is defi ned in the spec as representing “a
footer for its nearest ancestor sectioning content or sectioning
root element.” (“Sectioning content” includes article, aside, nav,
section, and “sectioning root elements” are blockquote, body,
details, fi eldset, fi gure, td).
Note that, as with the header element, there can be more than
one footer on a page; we'll revisit that in Chapter 2. For now,
we're just having one footer on the page that is a child of the
body element. As the spec says, “When the nearest ancestor
sectioning content or sectioning root element is the body ele-
ment, then it applies to the whole page.”
The spec continues “A footer typically contains information
about its section such as who wrote it, links to related docu-
ments, copyright data, and the like.”
Our footer holds copyright data, which we're wrapping in a
<small> element, too. <small> has been redefi ned in HTML5;
Search WWH ::

Custom Search