Articles hub

Every article as a row with its kind and reading time.

Page · stable · v1.0.0 · owner: Site system lead · contract 19 of 20 points (open: figma)

Do and don't

Do: Source-linked article rows

Declared by articles.ts

Authored page specimen; not a captured route or acceptance result. Open associated page (declared association; rendered-page verification is separate).

Open example: Articles hub · Do: Source-linked article rows Use the full-page example to follow page links.

Native templates render the manifesto's title, description and source reading estimate; authored main content, not a captured route or acceptance result.

Do: Long-content layout alternative

Declared by articles.ts

Authored page specimen; not a captured route or acceptance result.

Open example: Articles hub · Do: Long-content layout alternative Use the full-page example to follow page links.

Different labelled sample text and real destinations exercise the same native row layout without creating a page instance.

Don't: Missing the closing action

Declared by articles.ts

Authored page specimen; not a captured route or acceptance result.

Refused by the element. page-articles: page-articles.sequence: page-head → tile-grid does not follow page-articles (page-head → tile-grid → cta-section).

Native content still renders, but observed composition lacks the required closing CTA and fails this page's sequence.

Don't: Two fields with no cotton body

Declared by articles.ts

Authored page specimen; not a captured route or acceptance result.

Refused by the element. page-articles: D-SITE-002: compose page-articles: a teal field touches a saffron field (D-SITE-002: a field is always followed by cotton)

The native composer refuses the page-head field touching the CTA field before a sequence can be accepted.

Rules

RuleWhyCheck
Built pages follow: header, page-head, tile-grid, cta-section, footer.A declared composition is what makes the page checkable and the site consistent.Automated: scripts/site/system/check-pages.ts (check_composition per page)

API

No props.

Contract details

The full contract: identity, anatomy, variants, states, tokens, layout, motion, accessibility, content, tests

Identity

AspectValue
Idpage-articles
LayerPages
Categorypage
OwnerSite system lead
Statusstable
Version1.0.0
Sourceapps/showcase/site/system/pages/articles.ts (private repository; the contract and the render function are this one module)
VersionDateChange
1.0.02026-10-26Articles hub as one module: its markup moved out of the page builder (scripts/site) into the system.

Use when

  • Paths matching /^\/articles\/$/. Why: Every page of this kind is composed the same way, so readers learn it once.

Do not use when

  • For a page with a different job. Why: A new kind of page gets its own declaration and review.

Anatomy

PartWhat it is
1page-head
2tile-grid
3cta-section

Made of: header, page-head, tile-grid, cta-section, footer.

Used in: pages directly.

Variants

VariantWhenWhy
defaultWherever the page declaration places it.One shape per job keeps pages predictable.

States

StateRendered or not applicable
defaultdefault
hoverNot applicable: The articles hub is not interactive, so it has no hover state.
focus-visibleNot applicable: The articles hub does not take focus; links and buttons inside it carry their own focus ring.
activeNot applicable: The articles hub cannot be pressed.
disabledNot applicable: The articles hub has nothing to disable.
loadingNot applicable: The articles hub is rendered at build time and is complete when the page loads.
emptyNot applicable: The articles hub is not rendered without content; the builder skips it.
errorNot applicable: The articles hub shows no data that can fail.
currentNot applicable: The articles hub has no current item.
visitedNot applicable: The articles hub is not a link.
expandedNot applicable: The articles hub does not open or close.

Tokens

PartToken
page.ground--cotton

Layout

AspectValue
breakpointsRequired review at 390, 768, 1024 and 1440 px; execution is not implied by this declaration; columns stack under 768 px; the wrap keeps a 16 px gutter on phones.
wrappingText wraps; nothing scrolls sideways.
textExpansionJapanese runs 20 to 40% longer; headings break between phrases (jaBreaks) and blocks grow downwards.

Spacing and rhythm

AspectValue
internalEach template's own padding.
externalNone.
rhythmField, cotton, field: never two fields touching; the woven edge at each join (D-SITE-002, D-SITE-003).

Motion

AspectValue
NoneNo intrinsic element animation. The optional claude-entrance consumer profile may translate below-fold structure once (20px, --dur-weave, --ease-enter, --stagger); reduced motion disables it. This preserved baseline entrance is separate from element playback.

Runtime and reuse

  1. Render-only element; mount any registered child enhancements separately. Preserve required Site CSS, fonts, responsive and locale rules from nativeElement.

Accessibility passport

AspectValue
rolea landmark or list, as stated in its parts
nameIts visible text
keyboardLinks and buttons inside, in reading order.
focusThe --focus ring on every link and button inside.
screenReaderRead in source order; decorative weaving is aria-hidden.
contrastInk on cotton 14:1; text on every dye field 4.5:1 or better (checked by check-brand).
targetLinks and buttons are 44 px tall.

Content

SlotLengthVoice
page-head: title and ledeOne hub title and short explanation, within Page head limits.Explain what the reader can learn.
tile-grid.rows: article linksOne row per article, with its actual destination, description, kind and reading time; then the standard closing action.Use the article's title and a concrete description, not a sales claim.

Good: “Your design system needs an operator, not more documentation · 7 min — title and reading time from docs/launch/articles/manifesto.md, linking to /articles/manifesto/.”

Bad: “Read more — repeated rows with no article title or reading context.”

Japanese: The actual articles hub route is English. Do not invent a Japanese route or translated article list; use the existing row layout if a separately authored Japanese hub is later added.

Icons and illustrations

None: this element uses no icon or illustration of its own.

Decisions and exceptions

Usage

1 uses across the built pages (measured by npm run site:system).

Tests

AspectValue
unittests/unit/site-system.test.ts: renders every do and don't example through the registry and checks the classes it owns
visualNot yet: there are no screenshot baselines; the Library page is checked for sideways scroll at 1440 px by tests/site/system.spec.ts
a11ytests/site/system.spec.ts: axe (0 serious or critical) on the element's Library page in light and dark
parityscripts/site/system/check.ts: Library examples are rendered by the same render function the site imports

Figma

not-yet: The Loom Site Figma library is the last stage of the plan; this element is not mapped yet.

Open in Storybook

Start with a conversation about your system.

We read your system, show you what we found, and agree with your team what to fix first.