UIAtlas · website UI style library

Choose the design style before you write the first component.

Ten named UI styles, each with a typography suggestion, card architecture, button and navigation pattern, radius scale, elevation model and motion rule. Preview the same dashboard component in every style, then copy the specification straight into your project README.

  • 10named styles
  • 5in-depth guides
  • 11spec fields per style

The style lab

One component. Ten design languages. Switch a style and the same markup changes surface, radius, elevation, type and motion — currently showing Liquid Glass.

Atlas Overview Metrics Docs

Dashboard module

Deployment health

Build 4.2.0 is live on every regional edge. Response times stayed inside the target window during rollout.

Live 3 regions
View report Dismiss

Design specification

style: liquid-glass
typography: Inter / SF Pro — 600 headings, 400 body
radius: 24px cards, 999px pills
border: 1px rgba(255,255,255,0.35)
surface: rgba(255,255,255,0.14) + blur(14px) saturate(140%)
elevation: 0 18px 40px rgba(10,15,40,0.45)
buttons: translucent pill, light hairline border
nav: floating blurred pill bar, 16px inset
motion: 220ms ease-out, 8px rise on enter
cards: stacked media + body, full-bleed top image
best-for: SaaS dashboards, AI tools, device pages

Every field maps to a CSS custom property in the guides. Paste the block into your design tokens file and replace the placeholder values as you build.

Five guides, ten styles

Each guide pairs two related styles, breaks down their card architecture and component rules, and lists the trade-offs you will hit in production.

Layered translucent panels over a violet and teal gradient, illustrating the Liquid Glass interface family

Guide 01

Liquid Glass & Futuristic 3D

Translucent surfaces, blur, rim light and depth. The most expensive family to get right — and the easiest to ruin with poor contrast.

  • backdrop-filter
  • radius 22–24px
  • dark ground
Read guide 01
Muted pastel and sage shapes with rounded edges representing the Soft Minimal and Organic Modern styles

Guide 03

Soft Minimal & Organic Modern

Calm surfaces, one accent hue, generous line-height. The safest default for forms, onboarding and anything regulated.

  • radius 18–26px
  • micro-shadow
  • 44px targets
Read guide 03
Warm paper tones with fine rules and column structure evoking Swiss Grid and Editorial Luxury layouts

Guide 04

Swiss Grid & Editorial Luxury

Typography does the work. No shadows, no gloss — just scale, rules, whitespace and a disciplined twelve-column baseline.

  • radius 0–2px
  • no elevation
  • serif pairing
Read guide 04
Grid of rounded tiles in varying sizes with soft moulded surfaces, representing Bento Fusion and Sculptural UI

Guide 05

Bento Fusion & Sculptural UI

Tile grids and moulded surfaces. Excellent for feature pages, risky for dense data and for anything that needs crisp focus rings.

  • radius 20–30px
  • tile spans
  • dual shadow
Read guide 05

Pick a style in fifteen minutes

A style decision is a constraint decision. Work through these four questions before you open a design file, and the rest of the build stops arguing with itself.

  1. 1 · Name the content density

    Dashboards, tables and long forms punish decorative surfaces. If a single screen carries more than about twelve data points, start in the Soft Minimal or Swiss Grid families and add personality in the marketing pages instead.

  2. 2 · Check the contrast budget

    Translucent and neumorphic surfaces reduce the contrast between text and background. If you need to meet the WCAG 2.2 contrast criteria comfortably, choose a style with opaque panels — or commit to a fixed scrim behind every blurred panel.

  3. 3 · Decide who maintains it

    Neo-Brutalist and Swiss Grid are mostly borders, spacing and type scale, so a small team can keep them consistent. Futuristic 3D and Sculptural UI need someone who will own gradients, light direction and shadow pairs for the life of the product.

  4. 4 · Lock the tokens, then build

    Copy the specification from the style lab into a tokens file: radius scale, elevation pair, border width, type scale ratio, motion duration. Once those five values are fixed, component work becomes assembly rather than negotiation.

Reference material we point people to

For the mechanics behind the glass family, read the MDN documentation for backdrop-filter. For contrast and focus requirements, use the W3C WCAG 2.2 quick reference. Our guides describe style patterns; those two sources define what the browser and the standard actually require.

Need a second opinion on a direction before you commit? Send us the brief and we will reply with the two styles we would shortlist and why.