A structured lesson workspace with readable content, hands-on examples, and a clean path to completion.
Source-reading note: the exact semantics here come from the HTML element/attribute you chose, not its CSS appearance.
Checkpoint: you can now connect the markup for header, navigation, main, section, and footer to a browser behavior and a concrete debugging step.
“A useful way to learn this is to start with the browser's observable behavior, not the tag list. In this lesson, the focus is the core page-region elements and their landmark behavior. That matters because HTML is interpreted by a parser and then exposed to browser features such as navigation, accessibility tooling, form controls, media handling, and script APIs. A correct-looking screenshot can still hide a poor document model.”
Start with the smallest meaningful example. The working snippet demonstrates the core syntax, but the important part is what each piece contributes: the element supplies semantics or behavior, attributes refine that meaning, and surrounding structure gives the browser context. Don't add markup just because a framework or copied example happens to include it.
| Decision | Why it matters |
|---|---|
| Native element | Carries browser semantics and default behavior. |
| Attribute | Refines the element without replacing its meaning. |
| CSS/JS hook | Adds presentation or behavior around the existing structure. |
<header>...</header><nav>...</nav><main>...</main><footer>...</footer>
Now put the same idea under pressure. A realistic failure is: Construct a page shell with one clear main region and navigation that reflects actual destinations. The browser may recover, ignore an invalid combination, or leave the user with a control that appears visually fine but behaves differently than expected. That is why source inspection and keyboard testing belong in the workflow.
<meta charset="utf-8"><meta name="viewport" content="width=device-width, initial-scale=1">
The browser's defaults are part of the behavior you are learning. Prefer native semantics first, then test the exact combination of attributes and content you plan to ship.
You can now explain the browser behavior behind the core page-region elements and their landmark behavior, build the markup deliberately, and diagnose the most common failure mode instead of guessing.
Implementation note: Construct a page shell with one clear main region and navigation that reflects actual destinations. Keep the browser behavior observable while you work.
Finish the lesson once you have worked through the material. This awards ★ 20 XP.