Measured entry

kibo-dialog-stack

navbarminimal-flatmotion on file

A client-side React primitive for wizard-like cards that visually stack as users move forward and back. It ships as shadcn registry source rather than a package, uses Radix Portal and controllable-state utilities, and expects Tailwind classes plus a local cn helper and theme tokens.

Specimen
Motion capture of the mounted demo, recorded by the harness. No audio track.
Harness screenshot of kibo-dialog-stack at 375 pixels wide
Harness screenshot at 375 pixels wide. No horizontal overflow recorded.
Harness screenshot of kibo-dialog-stack at 768 pixels wide
Harness screenshot at 768 pixels wide. No horizontal overflow recorded.
Harness screenshot of kibo-dialog-stack at 1440 pixels wide
Harness screenshot at 1440 pixels wide. No horizontal overflow recorded.

Measured

Every value below was written by the harness on the run that produced the frames above. None of it is derived from the prose.

Harness measurements recorded for kibo-dialog-stack
BuildOK
MountOK
Console errors0
Uncaught page errors0
Horizontal overflowclean at 375, 768, 1440
Axe critical0
Axe serious0
Axe moderate0
Axe minor0
Gzip marginal33.4 KB (98.9 KB build, 65.5 KB baseline)
Bare modeOK
Provider requiredNO
Demo usedwritten from the component source API

Verdict

A solid visual shell for short wizard flows, with clean composition and a verified standalone mount. Treat it as a stack animation and navigation primitive, not a complete accessible dialog system, and add the missing interaction semantics for modal use.

Use it if

  • You need a compact multi-step form or setup flow presented as stacked cards.
  • You want controlled or uncontrolled open state and composable headers, content, footers, and navigation buttons.
  • Your React app already uses Tailwind conventions and can own the copied source.

Skip it if

  • You need full dialog behavior such as focus trapping, Escape-key dismissal, and explicit dialog semantics out of the box.
  • You need routing, validation, persistence, or branching between steps built into the component.
  • You do not want to maintain copied registry code or reproduce shadcn-style theme utilities.

Install

Installation record for kibo-dialog-stack
Declared dependencies@radix-ui/react-use-controllable-state, radix-ui, clsx, tailwind-merge
Missing on installnone
Bare installbuilds and mounts without the shadcn-style helpers
Providerno provider required in the harness

In a non-shadcn project, add React, Tailwind styling and theme variables, a cn class-merging helper backed by clsx and tailwind-merge, plus Radix Portal and controllable-state dependencies. Preserve the client-component boundary and ensure the registry import alias resolves.

Source and credit

This page is a review, not a copy. The component source lives with its author and this site does not republish it. Read the license before you use anything.

License
MIT
Record published
2026-08-17

Alternatives

Other published entries for the navbar pattern, ordered by what they measured: mounts first, then clean axe scans, then bare-mode passes, then the smaller bundle.