Contains introductory and / or navigational content.
Contains closing, summary information about its parent element. Again, we should have multiple footers in the page, inside both
Probably the most poorly named of the new tags (an aside is a stage direction or a type of dialogue),
Intended for major site navigation containing a series of links. In HTML5, this replaces the unordered list navigation structure we were using previously.
A container for a group of related content. A successor to the generic
A grouping of self-contained content, such as a blog post. New developers tend to get confused between
Adding to the confusion is the fact that articles could also be widgets, or web applications, such as calculators, weather reports, etc. Again, the emphasis is on self-containment: an
Also note that an
Marks up a known time, date, or period. Should include more precise time information as a
Designed to mark up diagrams, illustrations, photos, code samples, etc. May contain an optional
Perhaps best thought of as an in-body meta tag for individual pieces of content. Like meta tags, <details> is not immediately visible to the user by default; unlike meta tags, <detail> is written inside the <body> of the document, not the <head>.
A typical use for <detail> might be inside an article, as the default content for an RSS feed or a way for search engines to summarize what each article about. A Dublin Core description meta tag summarizes the entire document; individual <details> tags (containing <summary> elements) may help summarize each piece of content.
The summary for a particular piece of content. Must be the first child immediately inside a <details> element.
Estimated. reading time: 2 minutes, 55 seconds