Common Semantic Structure Patterns
You'll learn: How to combine semantic HTML elements into recognizable, real-world page layouts.
Now that you know individual semantic elements, it's time to see how they work together in actual websites. Just like rooms combine into familiar floor plans (bedroom, kitchen, bathroom), semantic elements combine into common page patterns.
Blog Post Pattern
A typical blog post uses:
<header>with an<h1>for the post title, author info in<address>, and<time>for publication date<main>wrapping the entire post content<article>inside<main>containing the actual post text<figure>and<figcaption>for images within the article<aside>for related links or author bio (outside<article>but inside<main>)<footer>with copyright and sharing links
Marketing/Landing Page Pattern
Marketing pages typically structure like this:
<header>with logo and<nav>for menu<main>containing multiple<section>elements, each with its own<h2>(features, pricing, testimonials)- Each benefit might be an
<article>within a section <aside>for promotional callouts<footer>with contact info in<address>, site links, and legal information
Documentation Site Pattern
Documentation uses deep hierarchy:
<header>with site navigation<nav>for table of contents (sometimes in<aside>)<main>with nested<article>and<section>elements following the heading hierarchy (h1→h2→h3)- Code examples don't need special semantic tags (use
<div>when semantics don't fit) <footer>with version info and links
Key Takeaway: Real websites combine semantic elements in predictable patterns—blogs wrap articles, marketing pages stack sections, and documentation nests deeply. Choose your structure based on your content's actual meaning, not just visual layout.