A 10px shape per status (circle, bullseye for live, triangle, cross, half ring, square).
A 10px shape per status (circle, bullseye for live, triangle, cross, half ring, square).
A 20-64px inline status glyph for agent work where the motion pattern itself is the signal: five states, five distinct cadences, no color and no swapped icon.
Illustrations for error pages: a wandering search icon for 404, a pulsing lock for 403 and a spinning ring for 500.
The small status glyph beside a task: a dashed ring for backlog, an open ring for todo, a ring filling like a pie while in progress and in review, a filled disc with a tick when done and a crossed disc when cancelled. Every state is built from the same four shapes, so a change animates from one to the next.
A status indicator component
Visual feedback for captions, fullscreen, picture-in-picture, and playback actions.
A small pill at the edge of the screen that reports background work. It reshapes as tasks come and go, opens into the full list, and leaves once everything is done.
Group membership drawn as an implicit surface: each item is a charge in an inverse-square field, and a marching-squares isoline at F = 1 is stroked as a bare outline, so items in the same group share one necked contour and an item that leaves visibly pinches off into its own closed loop.
A compact status history bar for showing service uptime across days or hours.
A 1em SVG status icon that morphs between idle, loading, success, and error, closing its spinning ring into a drawn check or cross with a portalled live region announcing each state
The mark of a message kind: success, error, warning, info.
Pill chip with a round icon well; status color only on the icon.
A dot and a few words: operational, degraded, closed.
A canvas-free AI thinking indicator: a rotating sphere of depth-cued SVG dots. Four states (thinking, searching, done, idle), distinct by motion, not color, legible from 24px inline to a 200px showpiece.
O texto que segura a pessoa durante uma espera longa, em quatro desenhos: linha com cronômetro, barra que varre, etapas e pulso.
Rising steam effect with wispy particle animation.
An inline sync-status glyph modelled on a float-and-thermostatic steam trap: condensate (pending events) fills a small chamber, a float trips a discharge valve at 88% height, the chamber blows down fast on an eased-out curve, and refill starts immediately, forever.
A live stem-and-leaf plot: every arriving value flies in from a staging slot and drops into its tens-stem row, existing leaves shoulder-nudging aside to insert it in sorted order, so the distribution is built entirely from the digits of the data and every leaf is still an individually focusable record.
Canvas headline spray-painted through a cut stencil plate: seeded S-curve sweeps deposit grainy paint inside the letter cutouts with faint overspray and a few drips, then the plate lifts away to reveal the word; drag to add coats.
A reusable pattern-masked input: the full template renders at rest as a muted stencil with literal separators already in place, each typed character inks its own cell, and a refused character prints faint, shakes, and falls away instead of vanishing silently.
Multi-step flow with a filling progress track, pulsing active step, sliding content that resizes smoothly and a completion state.
Horizontal stepper that shows where someone is in a fixed sequence — numbered circle markers joined by a connecting line, each drawn as complete (filled, with a check), current (ringed and highlighted) or upcoming (muted). Pass the steps and a current index and it derives every state; there is nothing to keep in sync by hand. Reach for it at the top of anything multi-step: a checkout or cart flow, a signup and onboarding wizard, account or workspace setup, a KYC or identity-verification flow, a document or tax filing, a multi-page form split across screens, an upload-then-review-then-publish pipeline, a survey or quiz, or an installer. Common asks it answers: "stepper component", "step indicator react", "multi-step form progress", "wizard steps ui", "checkout progress bar with steps", "onboarding progress indicator", "shadcn stepper", "progress steps 1 2 3", "form wizard header", "onboarding steps", "onboarding progress react", "signup flow progress", "step by step progress ui", "horizontal stepper react", "numbered steps component", "progress tracker steps", "step rail", "breadcrumb style steps", "step 2 of 5 indicator", "show which step the user is on", "wizard navigation header", "checkout steps cart shipping payment", "MUI Stepper equivalent shadcn", "antd Steps shadcn", "Mantine Stepper alternative", "Chakra Steps equivalent", "react-step-wizard alternative", "headless stepper react", "tailwind stepper", "accessible stepper aria-current step", "stepper screen reader completed current", "clickable stepper go back to a previous step", "prevent jumping ahead in a wizard", "ステッパー react", "ステップ インジケーター", "複数ステップ フォーム 進捗", "ウィザード 現在のステップ", "申し込みフロー 進捗表示", "オンボーディング 進捗", "ステップ 2/5 表示", "完了・現在・未完了 の表示", "aria-current=step ステッパー". shadcn/ui has no stepper: its progress component is a single bar with no notion of discrete stages, labels or a current position, and while its questionnaire is a multi-step flow, that component owns the questions and answers and reports its place as a plain "3 of 8" counter rather than a rail of numbered markers — so the header that shows where someone is in a sequence you already control still gets rebuilt by hand out of divs and borders. It is also not a timeline: this one counts position through a sequence that is known in advance and still to be finished, while timeline is the record of what already happened and has no current step. It is not a product tour either: a tour points at the interface and explains it, one popover at a time, while this says where somebody is in a sequence they are working through — reach for product-tour when the thing being explained is the screen, and for this one when the thing being tracked is their progress. Built as an ordered list, because the steps are an ordered list: the active one carries aria-current="step", every marker states its own status in screen-reader-only text (Completed / Current step / Not completed) rather than leaving the meaning to a colour and a tick, and the check icon is aria-hidden so it is not announced twice. Conveying stage by colour alone fails WCAG 1.4.1, which is why the status is always spelled out. Pass onStepClick and the steps already reached become real buttons with a focus-visible ring, while upcoming steps stay inert — a stepper that lets someone jump forward past validation is worse than one that is not clickable at all. Theme-aware through shadcn tokens with dark mode, and the only dependency is lucide-react for the check icon.
Showing 26,809–26,832 of 29,980
Showing 26,809–26,832 of 29,980