Get started
The Fair Case design system is the shared set of tokens, faces, icons and components that every Fair Case page is built from.
- BrandThe Balance mark is two equal upright panels, each with a round opening: two people finding a fair fit.
- ColorOur colours as roles for light and dark, and the palette they read.
- TypographyType is set by role, never by pixel size.
- IconsOne house icon set: line glyphs with a 1.5px line at every size, and solid glyphs for transport controls only.
- Spacing and radiusSpacing uses one 4px unit, in whole and half steps.
- AppSidebarThe sidebar signed-in and reference pages share: a brand, a sectioned page list and a foot.
- AppSurfaceThe inset surface an app shell draws its pages on, and the only thing that scrolls from 1024px.
- ButtonA pill that does something on this page.
- ButtonLinkThe button's classes as a link, for navigation that reads as a button.
- ChipA pill holding an icon and a short label: inline in a field, or outlined on its own.
- IconButtonA round icon-only button whose label is its name and its tooltip.
- IconsThe icons module's API: one function per glyph, four sizes, a 1.5px line and the current colour.
- Info iconThe outline circle with an i, on its own so /ask loads no other glyph, in the info colour roles.
- LogoLockupThe Balance mark and the outlined wordmark as one link home, with the once-per-tab entrance.
- Mail iconThe envelope on Join's form and link pages, on its own so only Join ships it.
- ScrollAreaA native vertical scroller with an eased fade at each edge while more content lies beyond it.
- SkeletonA loading state drawn from the content's own layout, so nothing moves when the data arrives.
- StepperDots that autoplay through steps and loop, with a pause button; they hold on hover and focus.
- TooltipA small inverse label that names a control, opening on hover and keyboard focus.
What it is
One package, @repo/ui. It holds the tokens, the fonts, the icons and the components, one component per file.
Pages import its stylesheet and its components. They keep their own words, content and behaviour.
How it's built
TypeScript
Every component and its props are typed, so a wrong variant fails the build, not the page.
Tailwind, on our tokens
Three tiers: raw values, then roles for light and dark, then utilities. Components use the utilities only, so they follow the colour scheme with no extra classes.
Base UI where focus or keyboard handling matter
Buttons and tooltips get their focus and keyboard handling from Base UI. We style them; we don't rewrite what it already does.
One table of variants per component
A size or a style is a prop, declared once, not a one-off class at each call site.
Why this site exists
So anyone building a Fair Case page can see what already exists, how it looks in light and dark, and how to use it, before writing something new.
Each component has light and dark stories, checked for accessibility in the package's tests. This site shows the same components, as they stand on staging.
The faces
Schibsted Grotesk for text and controls, and Montagu Slab for headings. Both are open-license and ship with the package. Where a build supplies the licensed sans, the main site draws text in that face; this site always shows the open faces.