The interface layer for the products we build.
mwui is an installable, shadcn-compatible registry of components, blocks, and hooks. Not a dependency you wait on. Source code the CLI drops into your project, for your team to own from the first commit.
A component library is a maintenance decision.
Most teams do not abandon a design system because the components were wrong. They abandon it because changing one meant filing a request and waiting. mwui removes that step by handing over the code.
Open code, not a black box
Every item lands in your repository as readable source. Change it, extend it, or delete the parts you never needed.
The CLI your team already runs
A standard shadcn registry. One command per item, resolved dependencies included, no bespoke tooling to learn.
Accessibility handled first
Components build on Base UI primitives, so focus order, keyboard behaviour, and ARIA are settled before styling starts.
Themed with tokens
OKLCH variables define light and dark side by side. Rebranding is a change to the token layer, never a sweep through components.
Documented where it is used
Each item ships a live preview, its source, and its installation steps on this site, generated from the registry itself.
Legible to coding agents
Markdown mirrors of every page, plus llms.txt and llms-full.txt, so the assistant in your editor reads the same docs you do.
What is in the registry today.
Primitives to start from, blocks to assemble a screen quickly, and the utilities that carry state between them.
Components
14Installable UI primitives and components.
Blocks
2Composed templates and larger UI sections.
Utilities
15Hooks, libraries, pages, files, themes, fonts, bases, styles, and other items.
Built inside client work, published for everyone.
Mediaweb designs and delivers enterprise digital experiences. mwui is the part of that practice we keep in the open: the components, blocks, and hooks that survived real projects.