A structured lesson workspace with readable content, hands-on examples, and a clean path to completion.
Implementation note: Build a catalog where each product remains identifiable and linkable without relying on CSS. Keep the browser behavior observable while you work.
Source-reading note: the exact semantics here come from the HTML element/attribute you chose, not its CSS appearance.
In production, this piece of HTML is rarely isolated; it sits between content, navigation, user input, and browser defaults. In this lesson, the focus is semantic product listings, price data, images, and calls to action. 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.
<article><img src="keyboard.jpg" alt="Compact mechanical keyboard"><h2>KB-60</h2><p>$129</p></article>
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.
<header><h1>Acme Studio</h1><nav><a href="/">Home</a><a href="/work">Work</a></nav></header><main>...</main>
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.
<article><header><h2>Project Atlas</h2><p><time datetime="2026-08-22">22 Aug 2026</time></p></header><figure><img src="atlas.webp" alt="Atlas dashboard on mobile"><figcaption>Responsive checkout redesign.</figcaption></figure></article>
In a team codebase, the expensive bugs usually come from assumptions. Someone assumes an anchor is just a button with a different visual style, that a placeholder is a label, that an iframe is only a rectangle, or that a client-side constraint is security. The safe engineering move is to name the browser behavior you actually depend on and encode it directly in HTML.
The practical test is simple: remove the CSS, resize the viewport, and try the page with a keyboard. The structure should still make sense.
Checkpoint: you can now connect the markup for creating a product catalog page to a browser behavior and a concrete debugging step.
Finish the lesson once you have worked through the material. This awards ★ 20 XP.