Category
12 posts
UnfoldCMS and Payload share an audience and almost nothing else. UnfoldCMS is a Laravel monolith with admin built on shadcn/ui. Payload is headless Node.js. Side-by-side on architecture, stack, hosting, pricing — and where each one wins.
Honest ranking of 7 CMS options for shadcn/ui projects. Only one is built fully on shadcn — the rest are headless with bring-your-own-shadcn front-ends, or admin templates without CMS guts.
The direct answer to 'is there a CMS built with shadcn/ui' — a production CMS using 51 real shadcn components across 205 admin pages, with three themes from one codebase.
A first-person build-in-public diary of the shadcn/ui admin rebuild — including the four-month timeline, time-to-ship metrics, and the three things I'd do differently next time.
Three tutorials for adding, customizing, and composing shadcn/ui components in the UnfoldCMS admin — no plugin API, just edit the file.
You built the shadcn dashboard. Now you need a blog, SEO meta, media uploads, and RBAC. Here is what you will build by hand - and why UnfoldCMS already ships it all.
We tested shadcn/ui, Ant Design, and Material UI on real CMS projects. Here is the honest 2026 breakdown — bundle size, customization, accessibility, and when each one actually wins.
A complete guide to using Tailwind v4 design tokens and shadcn/ui v2 to build a CMS admin that supports unlimited themes with no rebuild.
Every shadcn/ui component used in Unfold CMS, where it lives, and what we learned building 223 admin pages on top of the full shadcn surface area.
Laravel 12, React 19, Inertia 2, shadcn/ui, and Tailwind v4 — the modern Laravel CMS stack explained, layer by layer.
Most shadcn admin templates leave 80% of the CMS work to you — auth, permissions, media, publishing, SEO. Here's when a shadcn-native CMS makes more sense than a template plus weeks of glue code.
The first production CMS built entirely on shadcn/ui — 50 components, 183 admin pages, Tailwind v4, and three switchable themes. Here's why the shadcn philosophy maps perfectly onto what developers want from a CMS.