Skip to content

No.276 · Feedback· New

Missing Glyph 404

A typographic dead end: an empty aperture between two giant fours, interrupted by a registration line, with clear links back to familiar places.

The prompt

Copy this text

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

The design brief behind this component — reuse it to regenerate, remix, or explain it.

Build a typography-led missing-page composition on pale mineral paper (#e9e7df), with deep green ink. A small mono header reads LOST & FOUND and ERROR — 404. Across the centre, two huge flat Geist fours bracket an empty oval aperture with a second inset outline and tiny ABSENT annotation. One hairline registration rule crosses the whole numeral. A green radial highlight inside the fours follows a fine mouse pointer, returning to the middle on leave. Below, arrange a small status, a medium-weight heading and muted description beside a ruled recovery-link index; the primary home link comes first. Use ordinary anchors and configurable content, not router imports. Keep the numeral decorative, the heading semantic and the recovery navigation labelled. On a phone, scale the numeral without clipping and stack copy above links. Touch and reduced motion keep the highlight fixed. Do not add depth, a game, or animated letters. 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. Follow a fine pointer with the numeral highlight; use normal recovery links. Motion: Pointer sets a CSS gradient position without a frame loop. Reduced motion holds it centrally. 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. Follow a fine pointer with the numeral highlight; use normal recovery links.
Motion
Pointer sets a CSS gradient position without a frame loop. Reduced motion holds it centrally.
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.

Featured

310 components