Components

BeeUI’s public component reference is generated from the same Registry and @beemvp/beeui-ui export map that define the source/package surface. A stable public component cannot silently ship without a corresponding reference entry: the public-site quality gate joins Registry metadata, public exports, curated purpose/limitations and real Showcase usage before the docs build runs.

Browse

All components — the complete source-driven inventory, grouped for scanning.
Table — focused data-table guide.
Calendar & date/time — focused Calendar/DatePicker/DateTimePicker guide.
Showcase — the real interactive Component + Pattern runtime.

What every generated reference page includes

Each family documents its public import/export identity, Registry/source-ownership command, provider/dependency closure, platform/evidence boundary, accessibility and theming links, source-grounded executable fixtures, known limitations and direct source/Showcase links. Richer live preview + copy-code UX is layered on top of this same generated manifest rather than maintaining a second component inventory.

BeeUI remains unpublished until the existing owner release gate changes the canonical distribution state. Public reference pages therefore show the stable package boundary but never present public npm/CLI installation as already available.