Related Posts

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/related-posts.json

npx shadcn@latest add @interlace/related-posts

Import

2 named exports — pull the parts you need.

import { MIN_VIEWPORT, RelatedPosts } from '@/components/ui/patterns/related-posts';

Anatomy

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

RelatedPosts                       (section — data-min-viewport=480)
    ├─ Typography h3                 (title — "Related posts" by default)
    └─ Grid cols=1 md:2 lg:3 gap=md  (one ArticleCard per post)
          └─ ArticleCard

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)

Not focusable — no focus indicator required.

Reduced motion

No animation to gate.

ARIA in the source

• aria-busy
• aria-label

Examples

5 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

none

NPM dependencies

none

Registry dependencies

• @interlace/theme
• @interlace/article-card
• @interlace/cn
• @interlace/grid
• @interlace/skeleton
• @interlace/typography

Source

The full implementation — components/ui/patterns/related-posts.tsx once installed.

import * as React from 'react';

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

/**
 * @interlace/ui — RelatedPosts
 *
 * "Keep reading" surface that sits at the foot of an article page (or any
 * long-form route). Renders an h3 section heading followed by a responsive
 * grid of ArticleCards: one column on phones, two from `md` up, three from
 * `lg` up — the same 1/2/3 cadence the homepage feed uses, so a reader who
 * scrolls between an article tail and the index sees the same rhythm.
 *
 * The block is intentionally a pure composition over `ArticleCard` (the
 * stacked grid tile): every metric this block could surface (date, kicker, summary)
 * already lives on ArticleCard's props, so this file owns ONLY the heading,
 * the grid, and the field mapping from the editorial-friendly post shape

…181 more lines…

Registry JSON

The raw registry record — what the shadcn CLI fetches.