Prev Next Post

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/prev-next-post.json

npx shadcn@latest add @interlace/prev-next-post

Import

3 named exports — pull the parts you need.

import { MIN_VIEWPORT, PrevNextPost, PrevNextPostLink } from '@/components/ui/patterns/prev-next-post';

Anatomy

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

PrevNextPost                       (nav — data-min-viewport=480)
    ├─ a [data-slot="prev-next-prev"]   (left card — ArrowLeft + kicker + title)
    └─ a [data-slot="prev-next-next"]   (right card — kicker + title + ArrowRight)

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.

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)

Inherited from the preflight focus contract shipped in @interlace/theme.

Reduced motion

No animation to gate.

ARIA in the source

• aria-busy
• aria-label

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.

Dependencies

Base UI primitive

Native / no Base UI dependency

Lucide icons

• ArrowLeft
• ArrowRight

NPM dependencies

• lucide-react

Registry dependencies

• @interlace/theme
• @interlace/cn
• @interlace/skeleton

Source

The full implementation — components/ui/patterns/prev-next-post.tsx once installed.

import * as React from 'react';

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

/**
 * @interlace/ui — PrevNextPost
 *
 * Paired previous / next link cards rendered at the foot of an article. The
 * canonical "what to read next" surface — improves session depth, reduces
 * bounce, and gives keyboard / screen-reader users a deterministic exit ramp
 * from long-form content. Wrapped in a `<nav aria-label="Article navigation">`
 * so AT users can jump to it from the landmarks rotor.
 *
 * Either side is optional: a series-start post passes only `next`, a
 * series-end post passes only `prev`. When only one side is supplied the
 * grid still reserves two columns at `md` so the surviving card keeps its
 * column width — no layout shift between pages.

…148 more lines…

Registry JSON

The raw registry record — what the shadcn CLI fetches.