Skip to content

No.124 · Cards

Folio Card

An article card as thick as the article: page edges stack out from its corner, one sheet per 300 words, and a ribbon marks your place if you've started reading.

The prompt

Copy this text

Automatic copying is unavailable. Copy the selected text using your device’s copy command.

Written for the variant you picked above: Paper

Build an article card (a single link) whose depth shows the article's length. The card is a sheet of paper — mono kicker in the accent, serif title, short dek, author and date, and a mono line '11 min · 2,600 words'. Behind it, the pages: one box-shadow per sheet (words ÷ 300, between 2 and 30), each offset diagonally by i × a 'fan' amount and alternating between two paper tones so every edge reads as a line, plus one soft shadow under the whole stack. The card reserves margin for its own thickness so a grid of cards stays aligned. The fan amount is a registered @property number (1.25px per sheet at rest), so hovering or focusing the card animates it to 2.1 and the pages fan out smoothly (520ms expo-out) while the sheet lifts 2px toward the corner. If the reader has started the article (progress 0–1), a swallowtail ribbon hangs out from between the pages at that depth and the meta line adds '6 min left' in the accent; the ribbon swings a few degrees on hover. A note, a guide and an essay side by side should look different before you read a word. Selected variant — Paper (paper): Palette for this theme (Paper): --fc-accent #a8432f; --fc-focus #2f5fd0; --fc-ink #1d1b17; --fc-muted #706a60; --fc-page-a #f2eee4; --fc-page-b #d9d3c6; --fc-ribbon-c #a8432f; --fc-shadow rgb(40 32 20 / 0.28); --fc-sheet #fffdf8. Treat these as the root colour tokens, one value per role, and name them to suit your code. Select it with the theme option set to "paper". Keep every dimension, spacing value, state and motion from the brief unchanged, and keep text at 4.5:1 contrast or better on these surfaces. This selection takes precedence over references to other themes or options in the general brief. Implement this selected appearance; do not add a variant picker or alternative appearances unless requested. Implementation requirements: Use React and TypeScript. Keep the component self-contained, with uniquely scoped CSS and no animation libraries. Include required imports, styles and font setup in the result. Interaction: Hover or focus to fan the pages. The whole card is one link. Motion: Fan and lift 520ms expo-out via a registered custom property; the ribbon swings 6° on hover. Accessibility: One link with the title, meta and reading time as its text; the page edges and ribbon are decoration. Focus fans the pages like hover and shows a ring. Reduced motion keeps the pages still. Responsive behavior: Fluid width; the right and bottom margin equal the stack's depth so cards align in any grid. Preserve keyboard access, visible focus and reduced-motion behavior. Keep fictional demo data and simulated service calls in a separate usage example; expose callbacks for real actions and recover from rejected requests. Keep usage-example links inside the demo: use local buttons or prevent navigation. Demonstration links must not navigate to Vitrine routes or open other pages; preserve real URL support in the reusable component itself. Verify the result at narrow and wide viewport sizes, with keyboard input and reduced motion enabled.

Notes

Interaction
Hover or focus to fan the pages. The whole card is one link.
Motion
Fan and lift 520ms expo-out via a registered custom property; the ribbon swings 6° on hover.
Accessibility
One link with the title, meta and reading time as its text; the page edges and ribbon are decoration. Focus fans the pages like hover and shows a ring. Reduced motion keeps the pages still.
Responsive
Fluid width; the right and bottom margin equal the stack's depth so cards align in any grid.