Registry Item Template

Full-page surface for a single registry item's documentation (`/c/[name]` on ds.interlace.tools). Composes the header (item name + description + install snippet), the anatomy diagram, the variants matrix, related-components grid, and a CTA back to the…

blog & long-formserver320pxblockv1.1.0

Preview

Registry Item Template — live rendertemplates-registryitemtemplate--default

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.

Via shadcn URL
npx shadcn@latest add https://ds.interlace.tools/r/registry-item-template.json
With the @interlace alias
npx shadcn@latest add @interlace/registry-item-template

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.

Import

2 named exports — pull the parts you need.

Public API
import { MIN_VIEWPORT, RegistryItemTemplate } from '@/components/ui/templates/registry-item-template';

Anatomy

Extracted from the primitive's JSDoc header. The source is the only documentation that can't drift.

<article data-slot="registry-item-template" data-min-viewport="320">
    <Container size="content">
      <SectionBoundary name="registry-item-header">
        Header: name + description + install command
      </SectionBoundary>
      <SectionBoundary name="registry-item-anatomy">
        Anatomy / API surface
      </SectionBoundary>
      <SectionBoundary name="registry-item-variants">
        Variant matrix (CVA-driven)
      </SectionBoundary>
      <SectionBoundary name="registry-item-related">
        Related components
      </SectionBoundary>
    </Container>
  </article>

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.

RegistryItemTemplateProps

Also accepts every <article> attribute.

PropTypeDescription
name*stringComponent name — rendered as the page h1.
descriptionReact.ReactNodeOne-line description shown under the name.
installReact.ReactNodeInstall command — typically a `<CodeBlock language="bash">npx shadcn add @interlace/<name></CodeBlock>` element. Pass as ReactNode so the template doesn't take a hard dep on CodeBlock.
anatomyReact.ReactNodeAnatomy diagram + API surface (slots, props, R-rule mapping).
variantsReact.ReactNodeVariants matrix — CVA cells, themed in light + dark.
relatedReact.ReactNodeRelated-components grid (e.g. "Often used with…").
footerReact.ReactNodeExtra trailing content (e.g. a CTA back to the index, a "Report an issue" link). Rendered AFTER `related` inside its own SectionBoundary.

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
  • role="status"
  • aria-busy
  • aria-label

Examples

4 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.

RuleConceptWhere
R4Extends native el`React.ComponentProps<'article'>` + template props
R6data-slot on root`data-slot="registry-item-template"`
R7className merged + ...rest`cn(className)` + `{...props}` on <article>
R10Composition seam (slots)`header` / `anatomy` / `variants` / `related` ReactNode props
R14Declares min viewport`data-min-viewport={String(MIN_VIEWPORT)}`
R18Tailwind onlyZero inline `style`; layout via Container + Stack + cn()
R19Tokens only(delegated to composed primitives)
R20AA contrast(delegated)
R25Server componentPure composition — no hooks
R26A11y`<article>` landmark + per-section `<SectionBoundary>` regions

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.

Opt-in to the dev-mode warning
<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/templates/registry-item-template.tsx once installed.

234 lines · TypeScript
import * as React from 'react';

// @interlace/registry-item-template v1.1.0 — Interlace design system.
// Docs, props and live preview: https://ds.interlace.tools/c/registry-item-template
// What changed since: https://ds.interlace.tools/c/registry-item-template#history
// Generated banner — keep it, the upgrade diff reads this version.

/**
 * @interlace/ui — RegistryItemTemplate
 *
 * Full-page surface for a single registry item's documentation
 * (`/c/[name]` on ds.interlace.tools). Composes the header (item name +
 * description + install snippet), the anatomy diagram, the variants
 * matrix, related-components grid, and a CTA back to the registry —
 * each in its own `<SectionBoundary>` so the page streams
 * section-by-section.
 *
 * The DS eats its own dog food here: the registry app's `/c/[name]/page.tsx`
 * uses this template instead of hand-rolling the layout per-item.
 *

…214 more lines…

Registry JSON

The raw registry record — what the shadcn CLI fetches.