A structured lesson workspace with readable content, hands-on examples, and a clean path to completion.
Implementation note: Avoid embedding styling and behavior into the markup when a clear external boundary makes maintenance easier. 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.
You'll get more mileage from this topic by asking what information the markup communicates than by memorizing every attribute. In this lesson, the focus is clean boundaries between HTML, CSS, and JavaScript responsibilities. 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.
<button class="save-button" data-action="save">Save</button>
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>Separating Structure, Presentation, and Behavior 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">Separating Structure, Presentation, and Behavior</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.
Keep the markup close to the meaning of the content. Future CSS and JavaScript changes then have a stable surface to work against.
Field tip: for separating structure, presentation, and behavior, test both the ordinary path and the first case that makes your assumptions false.
Finish the lesson once you have worked through the material. This awards ★ 20 XP.