The Component Gallery
60 UI components cross-referenced against 95 real design systems
The Component Gallery, by Iain Bean, is a reference that answers 'what do other teams call this thing, and how did they build it'. It indexes roughly 60 canonical component types and links each one to about 2,670 concrete implementations across 95 public design systems — Shopify Polaris, IBM Carbon, Adobe Spectrum, GOV.UK, Salesforce, Vercel, Atlassian and the rest — with the alternative names each system uses. It is the naming and prior-art lookup you run before you invent a component API.
Use this at design time, not build time: before you name a prop, an API, or a component, check what 95 shipped design systems named it — it will stop you writing 'ShowyHideyThing' when the industry says Disclosure or Accordion. Each component page links straight to the source system's docs, so it is the fastest hop to Polaris/Carbon/Spectrum prior art for edge cases like tree, segmented control, or empty state. Note that the site returns HTTP 403 to plain server-side fetches, so route a human or a real browser at it rather than a bare HTTP client.
Why it is here. The only maintained cross-system index of component naming and behaviour, and naming is where most design-system arguments actually happen.
- 95 design systems indexed
- ~2,670 linked real examples
- alias names per component
- running and updated since 2019
- links out to each system's own docs
Verified 2026-08-15. HTTP 403. https://component.gallery and https://component.gallery/components/ both returned 403 to direct fetch (twice); content verified through https://r.jina.ai/https://component.gallery/components/ and https://r.jina.ai/https://component.gallery/design-systems/ (full component and design-system name lists read), plus a web search confirming Iain Bean as author and the 60 / 95 / 2,676 counts
