What is this?
A reference for the parts a web page is made of: the components you meet everywhere — navbars, modals, accordions — and the ideas underneath them, like the box model or how events travel.
Every component here is a wireframe. Click it and it opens its own card: what it's for, the parts it's made of, the technology holding it up, one real snippet, and a note with the thing that usually goes wrong.
The name is the promise. Field 02 of every card is the anatomy: the thing taken apart, with each piece named the way the rest of the industry names it.
Who it's for
People learning to build for the web, and people who already build but can't remember what the thing is called. Those are the same problem: the web has a lot of names, and most of them were somebody else's choice.
That's why the search looks at the other names too. Type FAQ and you get Accordion. Type disclosure — also Accordion. Type popup and you get Modal. Nobody agrees on these words, so the glossary keeps the ones people actually say.
Why it asks you a question first
Open a card and a question arrives before the answer does. It isn't a quiz: there's no score, and being wrong costs nothing.
It's there because of something that has been measured repeatedly and is easy to disbelieve: reading a good explanation, or looking at a good diagram, teaches you much less than it feels like it does. What actually moves is being asked to answer before you're told. Those few seconds of "hm, which one is it" do more work than the paragraph that follows them.
If it gets in the way, Stop asking turns it off for good, and the Predictions switch at the top turns it back on.
What it's made of
Plain HTML, CSS and JavaScript. No framework, no build step, nothing to install. Every entry lives in one data file and everything you see is built from it — including the questions, which is why adding an entry costs one object and no extra work.
The look is a blueprint: technical drawing, Klein blue on white, code in negative. A component is a drawing before it's code.
What it doesn't do
This helps you recognise things and remember what they're called. It does not make you able to build them. Knowing that an accordion's clickable row is called a header is not the same as having built one that works with a keyboard, and the honest research says that gap is wide.
Use it as a map, not as a course.