html - Marking up the "BBC pattern" in HTML5 -
i'm looking @ bbc site, , putting following similar overall pattern, , determining how mark appropriately stumping me somewhat.
the bbc consists of several considered sites in own right:
- http://www.bbc.co.uk
- http://www.bbc.co.uk/comedy/
- http://www.bbc.co.uk/news/
- www.bbc.co.uk/[a-lot-more-stuff]
(these subdomains instead - indeed, case me - urls not important)
each of these self-contained, own content, menu , , feel. of them tied use of (slightly variable mostly) static header bar. contains header "bbc" along links of various sub-sites.
so question is, how should marked up. see several different options:
the main bbc header site's main
<header>
,<nav>
. sort of correct, because ends de-emphasising importance of sub-site's actual content. when boils down (to use examples above), title "comedy" , associated menu main content of page, not bbc bar.make sub-sites' header , navigation ones marked within
<header>
,<nav>
. feels better, opens question bbc bar is? option use<aside>
, contains own<header>
,<nav>
. far know, fine header having other<nav>
element still weird. better option above?do same number 1 (bbc bar has main
<header>
,<nav>
), mark rest of page inside<article>
element. spec indicates article element used items make sense on own, case here. , it'll make sense have own<header>
(and<nav>
? pushing somewhat?) seems stretching definition of 'article' rather further dictionary definition allows.
to me, having given thought , thrown ideas , forth on twitter, number 2 seems best of these options. idea of putting contents of <aside>
top element on page (visually , in markup, since seems make logical sense way) doesn't quite sit right me.
am overlooking obvious solution or usual enough pattern make difficult seems? , surely can't 1 puzzle on this?
thanks thoughts.
the main header should be, pointed out, marked in <header>
, <nav>
.
i mark each additional page content in <article>
containing it's own <header>
, <nav>
. ignore dictionary definition of article, doesn't apply here. it's fine have more 1 <nav>
element on page, long contents navigate within site, makes sense.
putting top header in <aside>
doesn't seem correct me content isn't stand alone.
just thoughts on subject!
Comments
Post a Comment