Continuing the “portfolio wireframe” series for my HTML5 Project, we’ll be reviewing the main Work page, the three Work subcategory pages and the Niko’s Playlist page. Discussion will focus on the proper use of the tag.
(Important: I’ll be sending the final site to HTML5 Doctor and/or HTML5 Gallery for review when it’s done. While I’m confident that my site conforms to the HTML5 specification, these guys may say it doesn’t. Please keep that in mind when reading this.)
This article is structured as follows:
First, let’s look at all these pages…
The Main Work Page
This page was laid out using methods discussed in great detail in my last article where I discuss tags and
<article> tags. So I’m just going to skim over this page’s explanation:
- While the HTML5 specification (from here on referred to as the spec) encourages you to use as little as possible, it’s fine to use it if it’s your only option. I needed to wrap and position three tags which were not related to each other, so was my only option. Read where I discuss use in greater detail »
- The page displays three subcategory rows: Experiments, Freelance and Day Job. Each row contains samples of my work. Since the samples are of the same type and are related to one another, I’ve put each sample in an tag and wrapped the grouped samples in a tag. Read where I discuss and use in greater detail »
The Three Work Subcategory pages and the
You’ll notice that I highlighted the two phrases above that discuss “related elements”…this was done so I could neatly segue into the discussion about the tag.
The spec says, if page elements are related to each other, code your page so the relationship is obvious to search engines and machine readers.
<aside> does this very well: it’s basically saying the following sentence out loud to the engines and readers:
“All of the content inside of me is related to some main content that’s very close by”
I have an tag containing information about an individual piece of my work. To the right of it is a column of links to my other experiments. Since all these experiments are related to the content in the tag, we can make this column an tag. Lastly, this relationship allows me to wrap up both of these page elements in a tag.
Based on the location of the tag, it’s tempting to treat it like a traditional sidebar and put things like banners and blogrolls inside of it. Let me be clear: the spec says this is bad HTML5 practice because things like that, most likely, do NOT relate to your primary content. On a properly-formatted HTML5 page, sidebar content like banners and blogrolls should be placed into traditional tags.
This article over at HTML5 Doctor was my main reference when laying out the tag.
Niko’s Playlist Page