Hero
The above-the-fold section every landing page reaches for: eyebrow, headline, supporting copy, primary + secondary CTAs, optional media slot. Server-component-safe; the calm-confident-technical voice is enforced by Typography variants (no h1 with…
Preview
Rendered from the story the storybook (a11y) CI gate runs axe against — the preview can't show something that hasn't been verified.
Install
Two equivalent paths — the URL works in any shadcn-CLI setup; the alias works once you've registered @interlace in your components.json.
npx shadcn@latest add https://ds.interlace.tools/r/hero.jsonnpx shadcn@latest add @interlace/heroHistory
This component is at v1.1.0, first shipped in @interlace/ui 1.0.0. The version is stamped as a banner into the file the install writes, so the copy in your tree says which one you have — compare it with the number above before deciding whether to re-run the install.
@interlace/ui 1.1.01 entry
- Changedpatch
The fourteen
blocks/*re-export aliases now name the release they disappear in. They previously said "removal scheduled for one release cycle after the architecture PR lands", which is not a date anyone can plan around — so the aliases were, in practice, permanent. They are now@deprecated since 1.0.0 — removed in 2.0.0, and removal will land as a breaking change with a migration note.Components
Import
2 named exports — pull the parts you need.
import { Hero, MIN_VIEWPORT } from '@/components/ui/patterns/hero';Anatomy
Extracted from the primitive's JSDoc header. The source is the only documentation that can't drift.
Hero (section — data-min-viewport=320)
├─ Stack (text column)
│ ├─ {eyebrow} (Typography variant=ui-sm tone=primary)
│ ├─ Typography variant=h1 (headline)
│ ├─ Typography variant=long (subhead, max-w-prose)
│ └─ {actions} (Cluster of Buttons — primary first)
└─ {media} (optional right-column visual slot)API reference
Parsed from the type declarations in the source — the same file the install writes into your tree, so this table can't drift from the component you get.
HeroProps
Also accepts every <section> attribute.
| Prop | Type | Description |
|---|---|---|
| eyebrow | React.ReactNode | Small accent line above the headline — e.g. "v2.0 · February 2026". |
| headline* | React.ReactNode | Big display headline. |
| body | React.ReactNode | Supporting paragraph — max-w-prose by default. |
| actions | React.ReactNode | CTA cluster — typically a primary Button and a secondary link/Button. |
| media | React.ReactNode | Optional right-column visual — image, video, code window, decorative SVG. |
Accessibility
Every story for this component is rendered headlessly and checked with axe-core (wcag2aa, wcag22aa, best-practice, ACT) on every PR. That gate has no continue-on-error, so what ships has zero known violations.
What follows is what static analysis can see. Axe cannot press a key and never sees an overlay open, so the operable-without-a-mouse claim lives in Behavior instead, where the keyboard path is replayed step by step.
- Focus + keyboard behaviour
- Native element semantics — no interaction layer to get wrong.
- Focus ring (WCAG 2.2 SC 2.4.13)
- Not focusable — no focus indicator required.
- Reduced motion
- No animation to gate.
- ARIA in the source
aria-hidden
Examples
2 more states from the same story file.
R-rule compliance
Every primitive in @interlace/ui models to the portable 26-rule floor enforced by the componentApi ESLint preset. The cells below pin exactly where each rule applies in this file.
| Rule | Concept | Where |
|---|---|---|
| R4 | Extends native <section> | `React.ComponentProps<'section'> & HeroProps` |
| R6 | data-slot on root | `data-slot="hero"` |
| R10 | Composition seams | `eyebrow` + `actions` + `media` props |
| R14 | Declares min viewport | `data-min-viewport={String(MIN_VIEWPORT)}` + exported const |
| R19 | Tokens only | spacing/typography from primitives |
| R25 | Server component | No hooks → no `'use client'` |
| R26 | A11y landmark | `<section aria-labelledby>` is the rendered element |
Minimum viewport
This primitive declares MIN_VIEWPORT = 320 CSS px (DESIGN_PRINCIPLES #14). When mounted in a container narrower than this, the preflight contract draws a dev-mode outline so the regression is visible during local development.
<body data-interlace-dev>...</body>
Add the data-interlace-dev attribute to the body in development builds only — preflight then outlines any primitive whose container is below its declared data-min-viewport.
Dependencies
- Base UI primitive
- Native / no Base UI dependency
- Lucide icons
- none
- NPM dependencies
- none
- Registry dependencies
Source
The full implementation — components/ui/patterns/hero.tsx once installed.
import * as React from 'react';
// @interlace/hero v1.1.0 — Interlace design system.
// Docs, props and live preview: https://ds.interlace.tools/c/hero
// What changed since: https://ds.interlace.tools/c/hero#history
// Generated banner — keep it, the upgrade diff reads this version.
/**
* @interlace/ui — Hero
*
* The above-the-fold section every landing page reaches for: eyebrow,
* headline, supporting copy, primary + secondary CTAs, optional media slot.
* Server-component-safe; the calm-confident-technical voice is enforced by
* Typography variants (no h1 with weight=900 anywhere).
*
* ## Anatomy
*
* Hero (section — data-min-viewport=320)
* ├─ Stack (text column)
* │ ├─ {eyebrow} (Typography variant=ui-sm tone=primary)
…91 more lines…Registry JSON
The raw registry record — what the shadcn CLI fetches.