WovenUI started as an SCSS framework: readable utility classes, an apply() mixin that takes any value, and design tokens for light, dark and high-contrast themes. Core is the foundation layer. It styles plain buttons and form fields, and it stops there.
@wovenui/components is the layer on top: buttons, cards, forms, tables, modals, drawers, dropdowns, tabs, toasts and more, written as plain markup with wu- classes. It needs one companion package, @wovenui/core , which provides the tokens and themes the components read.
This post covers how the kit is built, and one lesson about dialogs that applies to any app, whatever UI kit it uses.
One class on native HTML
The kit leans on what the browser already does. Modals and drawers are <dialog> elements. Dropdowns and popovers use the popover attribute. Accordions are <details> elements, and accordions that share a name keep only one open.…