Page Header
The header band at the top of admin / docs / settings pages. Carries a breadcrumb (optional), title, optional description, and a right-aligned actions slot (typically a primary CTA + an optional menu). Renders a `<header>` landmark for screen-reader…
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/page-header.jsonnpx shadcn@latest add @interlace/page-headerBehavior
What this component does — the keyboard path, the measured colour, the text equivalent and the states it can be in. Every figure below is read out of the test or the source that enforces it by scripts/build-behavior-map.mjs, so nothing here can outlive the gate that keeps it true.
Measured contrast
packages/ui/__tests__/theme-contract-lock.test.ts ↗Every semantic colour pair this component's own source uses, measured against the shipped hexes in all 4 theme × scheme combinations. The tightest is muted-foreground on background at 7.82:1 (harbor · light), against a floor of 4.5:1.
| Pair | interlacelight | interlacedark | harborlight | harbordark | Floor |
|---|---|---|---|---|---|
| muted-foreground on backgroundsecondary copy | 9.41:1 | 11.32:1 | 7.82:1 | 9.52:1 | 4.5:1SC 1.4.3 |
| muted-foreground on cardsecondary copy in a card | 9.41:1 | 10.48:1 | 8.25:1 | 8.64:1 | 4.5:1SC 1.4.3 |
Text pairs are held to 4.5:1 (WCAG 2.2 SC 1.4.3); borders, rings and chart axes to 3:1 (SC 1.4.11 non-text). Bold is the worst cell in the row — the one a brand fork has to keep an eye on.
Runtime contract
packages/ui/vitest.config.ts ↗Where it renders, how narrow it survives, and whether its lines are inside the coverage gate — three answers a consumer needs before the paste, not after the bug.
- Render boundary
server componentRenders during SSR / RSC with no hydration cost. It can be imported from a server component without pulling the page into the client.
- Minimum viewport
MIN_VIEWPORT = 480Declared, not assumed. Below 480 CSS px the preflight contract draws a dev-mode outline — how to switch it on.
- Coverage gate
not in the gateThe 100% gate currently covers
src/charts/**/*.{ts,tsx}andsrc/lib/**/*.{ts,tsx}andsrc/primitives/{button-variants,data-state-model,meter-scale,skeleton-variants}.tsandsrc/primitives/{alert,aspect-ratio,avatar,badge,box,breadcrumb,button,callout,card,checkbox,container,data-state,focus-ring,grade-badge,grid,input,label,meter,pagination,published-date,reading-time,section,section-boundary,separator,skip-link,stack,stat-strip,tag,textarea,typography,visually-hidden}.tsx. This file is outside it — the glob widens in phase 7.2.
History
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 { MIN_VIEWPORT, PageHeader } from '@/components/ui/patterns/page-header';Anatomy
Extracted from the primitive's JSDoc header. The source is the only documentation that can't drift.
PageHeader (header — data-min-viewport=480)
├─ {breadcrumb} (optional — Breadcrumb primitive)
├─ <div> (title row — flex justify-between)
│ ├─ Stack (left column)
│ │ ├─ Typography h1 (title)
│ │ └─ Typography body (description — optional)
│ └─ {actions} (right column — Cluster of Buttons)
└─ {meta} (optional — tags / status / dates row)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.
PageHeaderProps
Also accepts every <header> attribute.
| Prop | Type | Description |
|---|---|---|
| title | React.ReactNode | — |
| description | React.ReactNode | — |
| breadcrumb | React.ReactNode | Optional <Breadcrumb> above the title. |
| actions | React.ReactNode | Optional right-aligned actions cluster — typically Buttons. |
| meta | React.ReactNode | Optional meta strip below the title — tags / status / dates. |
| loading | boolean | When true, render a `<Skeleton variant="page-header" />` placeholder. |
Skeleton
Pass loading and the component renders a shape-matched <Skeleton /> in its own place — same box, so nothing reflows when the data lands. Below is the same story with loading={true}.
<MIN_VIEWPORT loading={isPending} />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
- None — semantics come from the element or the Base UI primitive rather than hand-written ARIA.
Examples
3 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 <header> | `React.ComponentProps<'header'> & PageHeaderProps` |
| R6 | data-slot on root | `data-slot="page-header"` |
| R10 | Composition seams | `breadcrumb` + `actions` + `meta` props |
| R14 | Declares min viewport | `data-min-viewport={String(MIN_VIEWPORT)}` + exported const |
| R19 | Tokens only | border/spacing/typography from primitives |
| R25 | Server component | No hooks → no `'use client'` |
| R26 | A11y landmark | `<header>` is the rendered element |
Minimum viewport
This primitive declares MIN_VIEWPORT = 480 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
Source
The full implementation — components/ui/patterns/page-header.tsx once installed.
import * as React from 'react';
// @interlace/page-header v1.1.0 — Interlace design system.
// Docs, props and live preview: https://ds.interlace.tools/c/page-header
// What changed since: https://ds.interlace.tools/c/page-header#history
// Generated banner — keep it, the upgrade diff reads this version.
/**
* @interlace/ui — PageHeader
*
* The header band at the top of admin / docs / settings pages. Carries a
* breadcrumb (optional), title, optional description, and a right-aligned
* actions slot (typically a primary CTA + an optional menu). Renders a
* `<header>` landmark for screen-reader navigation.
*
* ## Anatomy
*
* PageHeader (header — data-min-viewport=480)
* ├─ {breadcrumb} (optional — Breadcrumb primitive)
* ├─ <div> (title row — flex justify-between)
…100 more lines…Registry JSON
The raw registry record — what the shadcn CLI fetches.