A structured lesson workspace with readable content, hands-on examples, and a clean path to completion.
Warning: invalid or overly permissive markup may still render. Rendering is not proof that the document model is correct.
Field tip: for the html head element, test both the ordinary path and the first case that makes your assumptions false.
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 metadata containers in head and which document information belongs there. 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.
<head><meta charset="utf-8"><title>Admin</title><link rel="stylesheet" href="app.css"></head>
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.
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.
<meta charset="utf-8"><meta name="viewport" content="width=device-width, initial-scale=1">
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.
<link rel="icon" href="/favicon.svg" type="image/svg+xml"><link rel="stylesheet" href="/styles.css"><script type="module" src="/app.js"></script>
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.
Implementation note: Separate user-facing body content from machine-readable document metadata. Keep the browser behavior observable while you work.
Finish the lesson once you have worked through the material. This awards ★ 20 XP.