No.279 · Feedback· New
Errata 404
A correction sheet for a missing page: an interrupted column, editorial annotation, and a neatly numbered route back.
The prompt
The design brief behind this component — reuse it to regenerate, remix, or explain it.
Build a 404 like an editorial correction sheet on warm paper (#f1eadb) with brown ink. A mono ruled masthead identifies THE CORRECTION SHEET and No. 404. Beneath it, a narrow margin holds ERRATA, a small annotation and a bent arrow; the main column carries a large Instrument Serif headline. Supporting copy shares a row with an interrupted text column represented by fine rules and a TEXT OMITTED annotation. A numbered index of ordinary recovery anchors follows; hovering or focusing a link draws an underline from the left over 250ms. End with a quiet ruled colophon. This is a missing-page composition, not a document browser. Keep all text semantic, omit decorative marks from accessibility, and never require motion to navigate. On a phone move the margin note inline, remove the decorative empty column and keep the source reading order. Reduced motion makes link feedback instant. 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: In Vitrine and the usage example, activating a recovery link is simulated locally and never changes page. In a consumer application, caller-supplied anchors remain usable. Numbered recovery anchors underline on hover or keyboard focus. Motion: 250ms underline scale; reduced motion removes the transition. Accessibility: Semantic headings and native links/buttons, visible focus, decorative geometry hidden from assistive technology. Independent instances; honour reduced motion. Responsive behavior: Fluid layout and wrapping text at 320px through desktop. Page compositions stack intentionally on narrow screens; recovery links remain visible. Touch: Normal taps activate all actions. Pointer-only decoration is optional and fixed on touch. 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
- In Vitrine and the usage example, activating a recovery link is simulated locally and never changes page. In a consumer application, caller-supplied anchors remain usable. Numbered recovery anchors underline on hover or keyboard focus.
- Motion
- 250ms underline scale; reduced motion removes the transition.
- Accessibility
- Semantic headings and native links/buttons, visible focus, decorative geometry hidden from assistive technology. Independent instances; honour reduced motion.
- Responsive
- Fluid layout and wrapping text at 320px through desktop. Page compositions stack intentionally on narrow screens; recovery links remain visible.
- On touch
- Normal taps activate all actions. Pointer-only decoration is optional and fixed on touch.