Is There a CMS Built with shadcn/ui? Yes — UnfoldCMS

📝 Originally published on is a CMS built entirely on shadcn/ui (Laravel 12 + React 19 + Inertia 2 + Tailwind v4). The admin uses 51 real shadcn components — not a wrapped abstraction, not a vendor-skinned widget set. You can fork any component the same way you'd fork shadcn anywhere else. Below: why no one else shipped this first, what the admin looks like, and the honest tradeoffs.

Is There a CMS Built with shadcn/ui?

Yes. UnfoldCMS is the first production CMS where the entire admin is built on shadcn/ui. Not a template, not an admin starter — a full CMS with content modeling, an editor, a media library, a REST + GraphQL API, role-based access, and a marketing site, all sharing the same 51-component shadcn design system.

Most "shadcn CMS" results in Google are one of three things:

• A dashboard template (no content model, no API, no editor)


• A demo repo showing a few admin screens (no real product behind it)


• A tutorial on building one from scratch (you finish it and realize you've shipped half a CMS)

A real CMS needs all of: a content schema, a stable API, a media pipeline, a search index, scheduling, drafts, redirects, sitemaps, RBAC, and an editor that doesn't fight you. Wiring all of that to shadcn — and keeping it forkable — is the part nobody had finished.

What "shadcn-Native" Actually Means

When we say UnfoldCMS is built on shadcn/ui, we mean the literal shadcn philosophy: you own the component code. There's no @unfoldcms/ui package gating you behind a vendor abstraction. The admin's Button, DataTable, Sidebar, Dialog, Command, Toast — they all live in resources/js/components/ui/ as standard shadcn files. Fork one and rebuild your admin in an afternoon.

That sounds obvious until you compare it to what other CMS admins look like:

CMS	Admin built on	Customize the admin?
WordPress	jQuery + PHP templates	Override CSS, fight the rest
Strapi	React + custom design system	Plugin API only
Payload	React + custom design system	Override via component swap config
Directus	Vue + Vuetify	Theming hooks
Sanity	React + custom Studio	Studio Schema only
UnfoldCMS	shadcn/ui + Tailwind v4	Edit the .tsx file directly

Every admin in the table above ships with its own proprietary component vocabulary. UnfoldCMS ships with a vocabulary you already know if you've ever pasted from shadcn-ui.com.

What 51 Components Look Like in Production

We didn't import 51 shadcn components for a screenshot — we used them. Here's where they ended up:

• 
  DataTable + ColumnHeader + Pagination → the Posts, Media, Users, and Settings lists


• 
  Sidebar + NavigationMenu → the persistent left rail across 205 admin pages


• 
  Command + Popover → the global ⌘K search jumping across posts, pages, settings, plugins


• 
  Dialog + AlertDialog + Drawer → confirmation flows, media picker, slide-in editors


• 
  Form + Input + Textarea + Select + Combobox + Calendar + DatePicker → every CMS form you'd expect, plus the publish-date Tehran-time scheduler


• 
  Tabs + Accordion + Card → the post editor's SEO / Media / Schedule panels


• 
  Toast + Sonner → save confirmations, upload progress, error reporting


• 
  Avatar + Badge + Tooltip + ContextMenu + DropdownMenu + Sheet → every dense list item interaction you can think of

This is the part most "shadcn admin template" repos skip. Wiring all the components in one product, against real data, in 205 pages — that's where the gaps in the design system show up. Filling those gaps is the year-long engineering work that separates "we use shadcn" from "we shipped a CMS on shadcn".

How Do You Theme a shadcn CMS?

You theme it the way you theme anything in Tailwind v4: change the CSS variables. UnfoldCMS ships with three themes from one codebase — Default Blue (#2563EB), Purple, and Unfold soft-purple (#938DE5) — switched via a single data-theme attribute on the root.

CODE Kopieren

[data-theme="default"]   { --primary: oklch(0.546 0.245 262.881); }

[data-theme="purple"]    { --primary: oklch(0.488 0.243 264.376); }

[data-theme="soft"]      { --primary: oklch(0.611 0.137 297.4);   }

That's it. Every shadcn component reads --primary (and the rest of the token set), so adding a fourth theme is one CSS block. Customers who want their admin to match their brand don't have to fork the whole admin — they edit four CSS variables.

For the full token system + how Tailwind v4's new @theme directive ties it together, see .

The Honest Tradeoffs

UnfoldCMS being shadcn-native is the headline. Here are the parts we wouldn't put on the homepage:

• 
  The component count keeps growing. shadcn adds ~1 new component per month. Keeping the CMS aligned with upstream is work — we track it in a public roadmap.


• 
  You need to know React. WordPress lets a non-developer fix a typo by clicking Edit. UnfoldCMS does too — but extending the admin means editing .tsx files. If your team is PHP-only, that's friction.


• 
  Mature plugin ecosystems still beat us on breadth. WordPress has 60,000 plugins. We have a few dozen first-party integrations and a clean extension API. Most teams don't need 60,000 plugins — but if you do, we're not the right fit yet.


• 
  shadcn is opinionated. If you wanted Material Design or Ant Design, the admin is going to feel sparse. That's the shadcn aesthetic. We think it's the right call, but it's a call.

For the longer comparison of shadcn vs other admin libraries, see .

Who Is a shadcn-Native CMS For?

A few audiences. If you fit any of these, UnfoldCMS is the answer to the title question:

1. 
   You already use shadcn/ui in your app and want a CMS whose admin matches your frontend's visual language without a Frankenstein iframe embed.


2. 
   You're a developer-first agency that hands a CMS to clients but also needs to extend it for every new project. A shadcn admin is one stack you already know.


3. 
   You want admin source code that doesn't lock you in. If our company disappears tomorrow, you still have a working React + Laravel app you can run, fork, and extend.


4. 
   You're tired of fighting WordPress block editor / Gutenberg. shadcn's editor isn't trying to be a page builder — it's trying to be a fast content editor.

For agencies specifically, the handover story is the killer feature — see for the licensing details.

Try It

If you're searching for a shadcn-native CMS, the easiest next step is the or ·

💬 First published on my own site: https://unfoldcms.com/blog/is-there-a-cms-built-with-shadcn/

UnfoldCMS is a self-hosted, developer-first CMS. If any of this was useful — or you disagree — I'm in the comments.

Vollständiger Original-Bericht

Ausführliche Details, Code-Beispiele & Hersteller-Stellungnahme auf dev.to.

↗ Original-Artikel auf dev.to lesen