The model
A pattern is a recurring solution to a recurring dashboard problem, described at the widget, layout, or interaction level. A product is a shipping application, and a capture is one dated screenshot of one of them, hot-spotted to the patterns it shows.
Patterns are the canonical pages. Nothing else here is written by hand—the product, domain and genre pages are generated out of the captures. Right now that's 109 patterns, 32 products and 39 captures.
The taxonomy
Eight of the nine groups come from Bach et al., Dashboard Design Patterns (IEEE VIS 2023). It appears to be the only peer-reviewed dashboard pattern language there is. Read it first.
The ninth group is an addition. Bach's corpus was visualization-research dashboards, so the taxonomy stops where the charts stop. It has nothing to say about the filter bar, the time-range picker, the empty state, the loading state, the error state, the builder, the share sheet, or the alert rule. Those have recurring problems and recurring solutions like anything else on the page, and a dashboard doesn't ship without them, so they get a group here: product mechanics, ten entries.
Facets are closed vocabularies. You add a value by editing the enum, never by free-typing a tag, which is the difference between a taxonomy and a tag cloud.
How an entry gets built
The pattern comes first, written against the same nine-part template every time: problem, solution, when to use it, when not to, trade-offs, checklist, compare, related, sources. The template is boring on purpose. What takes the time is everything after it, because a caption only earns its place if it says what that product's version does differently from the other two, and finding that out means opening two or three live demos and capturing the pattern at 2x. Those comparisons are the part of an entry that can't be looked up anywhere else.
What happens to a capture once the product redesigns is unresolved. One dated September 2026 is evidence of something that may not exist by the time you read this, and whether that makes the entry weaker or more interesting is an open question.
Screenshots and fair use
Screenshots here are reproduced for commentary and criticism. Every capture is dated, names the product version where one was visible, and links back to the product. Product branding stays in the frame. Cropping the logo out would misrepresent whose work is being discussed, and the whole argument of this site is that it's somebody's real work.
If you own something shown here and want a capture pulled or refreshed, say so and it comes down.
For machine readers
There's an llms.txt with the full pattern list, and every pattern
page has a markdown twin at /<library>/<slug>.md. Both carry the
aliases, which is the point: "KPI tile" is also "stat card", "big number", "BAN", and
"metric card", and a citation should hit all five.