Learn · long-tail answers
Questions the guides answer
18 questions phrased the way people search them, each paired with the essay that answers it and the component that proves it. Every pair is checked at build time: if an essay or asset is renamed, the row disappears from this page and the harness fails, which is the difference between a question map and a list of dead links.
Curated, not generated. Prefixing an essay title with “how to” produces a sentence, not a question, and the gap shows the moment someone reads it. 18 of the 91 guides are the best answer to at least one of these.
01How do I stop a hero section from feeling static?
Read the guide →three cheap layers — a backdrop you can ignore, one typographic moment, one honest action — built in one sitting.
02What is the difference between an easing and a spring?
Read the guide →an easing is a curve you choose; a spring is a system you tune, and the button shows the tuning.
03Which CSS properties can I animate without hurting performance?
Read the guide →only transform and opacity stay on the compositor, and the icons show what that buys you.
04How do I honour prefers-reduced-motion without gutting the design?
Read the guide →the reduced version is designed rather than disabled, which is what the loader handoff does.
05Why does my animation feel janky on a phone but smooth on my laptop?
Read the guide →frame budget, not frame rate, is the number that decides it — and the motes ship a low-end tier.
06Should I use scroll-linked animation?
Read the guide →sometimes yes, often no, and the path shows the version that stays on the compositor.
07How do I write a prompt that produces the same page twice?
Read the guide →constraints, order and an explicit checklist; the template is the output the method produces.
08What does a good prompt for a landing page actually contain?
Read the guide →the brief is the deliverable, and the template is what a well-specified one looks like.
09How do I check if my colour contrast is good enough?
Read the guide →the maths is four lines, and the banner's four tones all clear 4.5:1 on the page background.
10How do I make an empty state that doesn't look broken?
Read the guide →an empty state is a first impression with the content missing, which the trio takes seriously.
11How should a form tell someone they made a mistake?
Read the guide →errors belong next to the field, phrased as a next step rather than a verdict.
12How do I make focus visible without ugly outlines?
Read the guide →a focus ring is a design surface, and the pills treat it as one.
13How do I decide what to put in a sticky header?
Read the guide →the header earns its space or it should scroll away.
14How do I build a personal UI library that survives contact with real projects?
Read the guide →the structure matters more than the count — the palette is the search layer that makes a library usable.
15How do I keep a dark theme from looking like an inverted light theme?
Read the guide →dark mode is a token decision, not a colour swap — the veil is designed for a dark ground from the start.
16How do I size type so it works on a phone without magic numbers?
Read the guide →a clamp() with a stated reason beats a pile of breakpoints, and the numbers hold at both ends.
17When is a glass effect worth the paint cost?
Read the guide →glass reads as a material only when there is something behind it to blur.
18How do I test an interface with a keyboard, honestly?
Read the guide →unplug the mouse and try to finish a task — the palette is the component that survives that test.
Why an answer page beats a keyword page
A page that repeats a phrase answers nothing; a page that answers a question earns the next one. Each row above carries three things a search result can be judged on: the question in its own words, a guide that takes a position, and code you can open to check whether the position survives contact. The FAQ markup on this page is generated from the same rows, so the structured data cannot drift from what a reader sees.
The other direction is on every component page: a “read next” rail of two guides and a prompt, scored by shared tags — the crawlable spine behind this page.