A structured lesson workspace with readable content, hands-on examples, and a clean path to completion.
Implementation note: Use heading hierarchy for structure and choose strong/emphasis when meaning matters rather than decoration. Keep the browser behavior observable while you work.
Engineering judgment: prefer the native HTML behavior described here before reaching for a custom widget.
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 headings, paragraphs, and semantic inline text. 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.
<h1>Release notes</h1><p>Version <strong>3.2</strong> is available.</p><p><em>Read this before upgrading.</em></p>
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.
Don't confuse browser-side convenience with a security boundary. The markup in headings, paragraphs, and text formatting should improve behavior, but authoritative validation and policy belong at the trust boundary that processes the request.
<label>Email<input type="email" name="email" required></label>
Now put the same idea under pressure. A realistic failure is: Use heading hierarchy for structure and choose strong/emphasis when meaning matters rather than decoration. 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.
<form method="post" action="/account"><fieldset><legend>Account details</legend><label for="email">Email</label><input id="email" name="email" type="email" required></fieldset><button type="submit">Save</button></form>
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.
Keep the markup close to the meaning of the content. Future CSS and JavaScript changes then have a stable surface to work against.
Checkpoint: you can now connect the markup for headings, paragraphs, and text formatting to a browser behavior and a concrete debugging step.
Finish the lesson once you have worked through the material. This awards ★ 20 XP.