Geek Answers Handbook

The designation of the "BBC template" in HTML5

I look at the BBC website and collect something, following a similar general pattern, and determining how to mark it appropriately bothers me a bit.

The BBC consists of several that could be considered own sites:

(all of them could be subdomains - in fact, it concerns me, but URLs are not important)

Each of them is essentially autonomous, with its contents, menu and appearance. However, they are all related to each other using a (slightly modified, but larger) static header line. It contains the heading "BBC" along with links to all the various sub-sites.

So the question is how this should be noted. I see several different options:

  • The main heading of the BBC is the main site <header> and <nav> . This seems to be correct because it happens, but it ultimately emphasizes the importance of the actual content on the subsite. When it comes down to this (to use the examples above), the "Comedy" headline and its associated menu are the main content of the page, not the BBC panel.

  • Make the sub-site header and navigation the ones that are marked within the <header> and <nav> . It feels better, but then the question is, what is the BBC bar now? The option is to use <aside> , which then contains its own <header> and <nav> . As far as I know, this is normal for the header, but the presence of this other <nav> element is still strange. Better option, the higher?

  • Do the same as number 1 (the BBC has the main <header> and <nav> ), but mark the rest of the page inside the <article> element. The specification indicates that an article element should be used for elements that make sense on their own, which is the case here. And it also makes sense for him to have his own <header> (and <nav> ? Does this push him somewhat?) But this seems to stretch the definition of "article" much further than his definition of the dictionary allows.

For me, thinking and throwing some ideas on Twitter, number 2 seems to be the best of these options. However, the idea of ​​essentially placing the <aside> content as the top element on the page (visually and in markup, as it seems to be the most logical), does not quite suit me.

Can I ignore the obvious solution, or is it a regular enough template that it makes as hard as it seems? And, of course, I cannot be the only one who could solve this problem?

Thanks for any thoughts.

+4
source share
1 answer

The main title should be specified, as you indicated, in <header> and <nav> .

Then I would put each additional page content in an <article> containing its own <header> and <nav> . Ignore the definition of the article dictionary; it is not applicable here. This is great to have more than one <nav> element per page, if its content moves inside the site, which makes sense.

Putting the top header in <aside> also doesn't seem right to me, as the content is not self-contained.

Just my thoughts on this!

+1
source

More articles:


All Articles