HTML and CSS Reference
In-Depth Information
email client, maps, and reusable web widgets. For <article>
don't think newspaper article, think article of clothing—a discrete
item. Note that, as with <nav> , the heading is part of the article
itself, so it goes inside the element. Thus
<h1>My article</h1>
<article>
<p>Blah blah</p>
</article>
is incorrect; it should be
<article>
<h1>My article</h1>
<p>Blah blah</p>
</article>
There are many more interesting facets to <article> which
(you've guessed it) we'll look at in the next chapter.
What's the point?
A very wise friend of mine, Robin Berjon, wrote, “Pretty much
everyone in the Web community agrees that 'semantics are
yummy, and will get you cookies,' and that's probably true. But
once you start digging a little bit further, it becomes clear that
very few people can actually articulate a reason why.
“The general answer is 'to repurpose content.' That's fine on the
surface, but you quickly reach a point where you have to ask,
'Repurpose to what?' For instance, if you want to render pages
to a small screen (a form of repurposing) then <nav> or <footer>
tell you that those bits aren't content, and can be folded away;
but if you're looking into legal issues digging inside <footer>
with some heuristics won't help much . . .
“I think HTML should add only elements that either expose
functionality that would be pretty much meaningless otherwise
(e.g., <canvas>) or that provide semantics that help repurpose
for Web browsing uses.” www.alistapart.com/comments/
semanticsinhtml5?page=2#12
As Robin suggests, small screen devices might fold away non-
content areas (or zoom in to the main content areas). A certain
touch or swipe could zoom to nav, or to footer or header. A
 
 
Search WWH ::




Custom Search