A structured lesson workspace with readable content, hands-on examples, and a clean path to completion.
Implementation note: Combine headings, links, image alt text, and semantic sections into one focused page. 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.
Production signal: 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.
Treat the markup here as a contract with the browser. The more precisely you express the contract, the less repair work the browser has to invent. In this lesson, the focus is project architecture for a simple profile page. 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.
<main><header><h1>Lena Hassan</h1><p>Frontend engineer</p></header><section>...</section></main>
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>
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.
Don't confuse browser-side convenience with a security boundary. The markup in building a personal profile page should improve behavior, but authoritative validation and policy belong at the trust boundary that processes the request.
<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>
For this topic, the edge case is worth remembering: HTML has legacy parsing and compatibility behavior, so invalid markup does not always fail loudly. If you are debugging a strange result, reduce the page to one element at a time, validate the source, and inspect the resulting DOM. Small reproductions beat guessing at the full application.
Warning: invalid or overly permissive markup may still render. Rendering is not proof that the document model is correct.
Finish the lesson once you have worked through the material. This awards ★ 20 XP.