A structured lesson workspace with readable content, hands-on examples, and a clean path to completion.
The trap with this topic is that the markup looks simple while the browser is doing more work underneath. In this lesson, the focus is readability, source order, meaningful structure, and local clarity. 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.
Implementation note: Write markup that a teammate can modify months later without reconstructing the author's intent. Keep the browser behavior observable while you work.
<article><h2>Release 3.2</h2><p>...</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.
<!-- Contrast the weak version --><div>Writing Maintainable HTML used as a generic container</div>
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.
<section aria-labelledby="topic-title"><h2 id="topic-title">Writing Maintainable HTML</h2><p>Use the element that matches the content's meaning.</p></section>
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.
Source-reading note: the exact semantics here come from the HTML element/attribute you chose, not its CSS appearance.
Engineering judgment: prefer the native HTML behavior described here before reaching for a custom widget.
Engineering judgment: prefer the native HTML behavior described here before reaching for a custom widget.
Finish the lesson once you have worked through the material. This awards ★ 20 XP.