Article List Grid
Grid of ArticleCards with an optional featured slot above. The pattern blog index pages reach for: one big featured card (overlay variant) above N tiles. Composes RelatedPosts-style streaming with proper loading + empty states.
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/article-list-grid.jsonnpx shadcn@latest add @interlace/article-list-gridHistory
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.
No release note names this component yet. It shipped with the release above and has not changed since — see the full changelog for what moved elsewhere in the DS.
Import
2 named exports — pull the parts you need.
import { ArticleListGrid, MIN_VIEWPORT } from '@/components/ui/patterns/article-list-grid';Anatomy
Extracted from the primitive's JSDoc header. The source is the only documentation that can't drift.
<section data-slot="article-list-grid" data-min-viewport="320">
<Container>
{featured && <ArticleCard variant="overlay" priority />}
<Grid cols={3}>{posts.map(<ArticleCard />)}</Grid>
</Container>
</section>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.
ArticleCardProps
Also accepts every <section> attribute.
ArticleListGridProps
Also accepts every <section> attribute.
| Prop | Type | Description |
|---|---|---|
| title | React.ReactNode | — |
| lead | React.ReactNode | — |
| featured | ArticleCardProps | Optional featured article (renders as a hero card above the grid). |
| posts | ArticleCardProps[] | Regular tiles. |
| cols | 2 | 3 | 4 | — |
| loading | boolean | — |
| loadingCount | number | — |
| emptyState | React.ReactNode | Custom empty state. Defaults to a small muted line. |
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}.
<ArticleListGrid 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
7 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 el | `React.ComponentProps<'section'>` + props |
| R6 | data-slot on root | `data-slot="article-list-grid"` |
| R10 | Composition seam | `featured` + `posts` arrays of ArticleCard props |
| R14 | Declares min viewport | `data-min-viewport={String(MIN_VIEWPORT)}` + exported const |
| R18 | Tailwind only | Zero inline `style` |
| R25 | Server component | No hooks |
| R26 | A11y | `<section>` landmark |
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
Source
The full implementation — components/ui/patterns/article-list-grid.tsx once installed.
import * as React from 'react';
// @interlace/article-list-grid v1.1.0 — Interlace design system.
// Docs, props and live preview: https://ds.interlace.tools/c/article-list-grid
// What changed since: https://ds.interlace.tools/c/article-list-grid#history
// Generated banner — keep it, the upgrade diff reads this version.
/**
* @interlace/ui — ArticleListGrid
*
* Grid of ArticleCards with an optional featured slot above. The pattern
* blog index pages reach for: one big featured card (overlay variant)
* above N tiles. Composes RelatedPosts-style streaming with proper
* loading + empty states.
*
* ## Anatomy
*
* <section data-slot="article-list-grid" data-min-viewport="320">
* <Container>
* {featured && <ArticleCard variant="overlay" priority />}
…128 more lines…Registry JSON
The raw registry record — what the shadcn CLI fetches.