Blog
Explore our latest articles, tutorials, and insights.
A year of building UnfoldCMS on shadcn/ui — 51 components, 210 admin pages, real customers. The architecture lessons that survived production: composition over configuration, owning the code, forms as primitives, tables as data.
A shadcn dashboard template ships the visible part of a CMS in 10 minutes. The next 35-50 days are spent building everything you don't see — auth, roles, media, scheduler, SEO. Honest scope, shortest pragmatic path, when to bail on the DIY route.
Step-by-step tutorial: spin up a working blog CMS with Next.js front-end and shadcn/ui admin in 30 minutes. No Docker, no cloud account, just PHP + Node + MySQL. Real admin (51 shadcn components, 205 pages), real public API.
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.
How to handle Jalali (Solar Hijri) and Hijri (Islamic) calendars in a Laravel app using MultiCarbon — an open-source package that extends Carbon directly, so every Carbon method keeps working.
I spent two months trying to build a CMS on top of FilamentPHP. Here's what I learned about the difference between admin-panel frameworks and CMSes.
The new /api/v1/* namespace ships in Core. Public reads, authenticated user endpoints, admin CRUD, outgoing signed webhooks. Built for Next.js, Astro, SvelteKit, and mobile apps.
A working backup playbook for self-hosted CMS operators — DB dumps, media sync, encrypted offsite copies, retention tiers, and the restore drill that turns wishes into actual backups.
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.
Honest tradeoffs on JAMstack + headless CMS. Five scenarios where the combo pays off, four where you should stay on markdown, and the middle ground most sites should pick.