1.4 KiB
WRNexus UI component inventory
This inventory maps the two approved v1.0 PDF checklists to implementation stages. The source documents are WRNexus Essential Component Inventory v1.0 and WRNexus Public SaaS Component System Checklist v1.0.
Release boundary
The current @wrnexus/ui release targets the documents' combined minimum
first-release component set and essential components to build first. These
are implemented as real components with theme tokens, responsive rules,
keyboard-native controls, visible focus, reduced-motion handling, and mobile
touch targets—not name-only aliases.
SEO and structured data are intentionally handled by WRNexus page/head APIs. Rendering them as body components would produce invalid or ineffective HTML.
Subsequent staged packages
The remaining expanded inventory is retained for staged implementation in the dependency order prescribed by the PDFs:
design-tokensandiconsui-forms,ui-calendar,ui-feedback,ui-overlaysui-navigation,ui-data,ui-charts,ui-editors,ui-mediaui-shell,ui-marketing,ui-commerce,ui-developersui-content,ui-legal,ui-status
Each stage must satisfy rendering, keyboard, focus, semantics, disabled/loading states, mobile layout from 320 px, light/dark themes, reduced motion, no horizontal overflow, documentation, and production-build tests before release.