Learn
Understand the production reason and the tradeoff behind the pattern.
2–4 minFocused lessons for the stacks developers use every day — each with a production reason, a copy-ready example, and notes for the platforms you actually deploy on.
Stacks
7
Field notes
80
Depth
Beginner to advanced
If it changes state, use button. If it navigates, use a link.
<button type="button" aria-expanded={open} onClick={toggleMenu}> Toggle filters</button> <a href="/pricing"> View pricing</a>HTML field notes
Semantic structure, forms, buttons, and accessible defaults. Each note includes production context, copy-ready examples, and platform-specific advice.
If it changes state, use button. If it navigates, use a link.
Visible or screen-reader labels make forms better for users and automated tests.
Headings should describe document structure, not only match a visual size.
details and summary are excellent for simple FAQ and help interfaces.
Use header, nav, main, aside, and footer so users and assistive tech can jump around quickly.
Describe useful images and leave decorative images empty so screen readers get the right signal.
Use aria-describedby so validation messages are announced with the input they explain.
Use email, url, number, date, and search inputs to get better keyboards and validation for free.
A repeatable workflow
Every field note follows the same short path, so you can understand it, use it, and verify the result without reading a long tutorial.
Understand the production reason and the tradeoff behind the pattern.
2–4 minCopy the focused example, adapt the values, and use it in your stack.
Copy-readyCheck the real result, keep what works, and move to the next bottleneck.
Measure it