Geek Answers Handbook

HTML5 article or section for a list of favorite books?

Dummy book site. Each book has its own page. Now I want to add a page that lists all my favorite books. What HTML5 sectioning elements would you use for the "container" and which for each book? Should the MARQUEE placeholder and BLINK placeholder be section or article ?

The page might look like this:

 <body> <h1>Books!</h1> <nav> <h1>Navigation</h1> </nav> <MARQUEE> <!-- section or article? --> <h1>My all time favorite books</h1> <BLINK> <!-- section or article? --> <h1><cite>The Hobbit, or There and Back Again</cite></h1> <p>…</p> <nav><a href="books/hobbit">see the page about "The Hobbit"</a></nav> </BLINK> <BLINK> <!-- section or article? --> <h1><cite>Alice Adventures in Wonderland</cite></h1> <p>…</p> <nav><a href="books/alice">see the page about "Alice in Wonderland"</a></nav> </BLINK> </MARQUEE> <footer>☺ 2012 books.example.net</footer> </body>

My thoughts

I think that each listed book should be an article element. spec says "autonomous composition in a document", "in principle, independently redistributable or reusable", "blog entry, [...] independent content element". I think all this is here.

But what about the container? Should I use section or article ? article with nested article elements is that blog comments should be noted:

For example, a blog post on a site that accepts comments submitted by the user may present comments as article elements embedded in the article element for a blog post.

The general definition reads:

When article elements are nested, internal article elements are articles that are basically related to the contents of an external article.

“basically connected” seems to fit my example too?

The way I see it: This page about my favorite books is a "stand-alone composition." This is an article that I could print and give someone to read, and he will have all the information he needs, it makes sense in itself, nothing is missing. In addition, each of your favorite books is an “autonomous composition”, because I can print only one of these favorite books, and the reader will still have all the necessary information (about this book), it makes sense in itself, etc. d.

I am wondering if anyone is here?

For those who agree, my next question is: will the list of favorite books be semantically different from the list of recent blog posts in terms of markup choices? So, you could say, “okay, an article for a list of favorite books is OK, but not for a list of recent blog posts?” The only difference that I see is that most people are not interested in reading a list of snippets of recent blog posts, so this is not a "stand-alone" in the colloquial sense.

+7
source share
2 answers

Ideally, you will use a list with articles inside it. Because it's, well, a list of your favorite books, isn't it?

But personally, I use a section containing articles. I would not consider that the list is comparable to an article, which is essentially what you have. If you expanded it to include information about how you came up with the list, making it look more like a blog entry, then it would be wiser to become an article containing articles (and, again, ideally, an article containing a list of articles )

In any case, using sections for each individual book you link makes no sense.

+1
source

I will have all the content in the article , with each book in a section .

This would make it extremely compatible with the third example provided by W3C.

+1
source

More articles:


All Articles