No.293 · Navigation
Thread Stepper
A step indicator drawn as a thread through beads: finishing a step pulls the thread taut to the next, and the current bead pulses.
The prompt
The design brief behind this component — reuse it to regenerate, remix, or explain it.
Design a horizontal stepper as a thread passing through beads. Steps sit in equal columns; a dotted rail runs from the centre of the first bead to the centre of the last. On top of it a 2px frost-to-lilac thread with a soft glow is revealed by a clip-path whose right inset is driven by a CSS variable for progress (current step ÷ last step), transitioning over 700ms with a symmetric ease — so advancing a step pulls the thread taut to the next bead. Each bead is a 38px circle button. Todo: hairline border, muted mono number. Current: frost border, cream number, and a slow pulse ring (box-shadow 0 → 10px fade, 2.4s). Done: filled frost with a check that draws itself (stroke-dashoffset) after the thread arrives (500ms delay). Fill/border changes are delayed 200ms so the thread reaches the bead first. Titles and optional hints sit below each bead (hints hide on narrow screens). Completed and current beads are clickable to go back; future ones are disabled. Use an <ol> with aria-current="step" and descriptive aria-labels including state. 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: Advance via your own controls (or click a completed bead to go back); the thread eases to the new position. Motion: Thread 700ms symmetric ease; bead fill 400ms after 200ms; check draw 380ms after 500ms; pulse 2.4s loop. Accessibility: Ordered list with aria-current=step on the current bead; each bead's label includes its number, title and state; future steps are disabled. Reduced motion removes delays and the pulse. Responsive behavior: Equal columns; hints hide below 30rem. 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
- Advance via your own controls (or click a completed bead to go back); the thread eases to the new position.
- Motion
- Thread 700ms symmetric ease; bead fill 400ms after 200ms; check draw 380ms after 500ms; pulse 2.4s loop.
- Accessibility
- Ordered list with aria-current=step on the current bead; each bead's label includes its number, title and state; future steps are disabled. Reduced motion removes delays and the pulse.
- Responsive
- Equal columns; hints hide below 30rem.