Most UI libraries stop at primitives. You still wire up auth pages, dashboard layouts, settings flows, CRM views — all from scratch, every time.
Mdigitalcn gives you the full stack of UI. Components compose into widgets. Widgets compose into pages. Pages snap into layouts. Templates give you a running app in one command.
Everything is accessed through one entry point: the CLI.
npm install -g @mdigitalcn/cli# Scaffold a new project
mdigitalcn init
# Start from a full starter template
mdigitalcn init --name my-app --template vite/dashboard
# Add anything from the registry into an existing project
mdigitalcn add button login-form dashboard-page sidebar-layout authThe CLI scaffolds projects, pulls from the registry, and wires up configs. You do not install packages manually — mdigitalcn add handles everything.
cli ── scaffold + registry gateway
|
templates 10 project starters (Vite · Next.js)
pages 34 full pages (dashboard, auth, ecommerce, kanban)
layouts 17 layout shells (sidebar, topnav, docs, wizard)
modules cross-cutting logic (auth provider, guard, session)
widgets 47 composite widgets (auth, charts, CRM, HRM, stats)
uikit 80+ base components (buttons, tables, modals, forms)
utils FP utilities and React hooks
| Repository | What | |
|---|---|---|
cli |
Rust CLI — scaffold projects, add from any registry |  |
uikit |
80+ base components — buttons, tables, modals, pickers, forms, trees |  |
widgets |
47 composite widgets — auth, charts, CRM, HRM, ERP, marketing, stats | |
pages |
34 full pages — dashboards, settings, auth, ecommerce, messaging, kanban | |
layouts |
17 layout shells — sidebar, topnav, docs, wizard, auth, landing | |
modules |
Cross-cutting — auth provider, auth guard, session monitor | |
utils |
FP utilities and React hooks — array, string, validation, promises |  |
templates |
10 project starters — Vite and Next.js (SaaS, dashboard, blog, docs, commerce) |