Why Laravel deserved a first-class CMS

Laravel has 250,000+ active installs a month on Packagist. It has the best-in-class framework ergonomics in PHP. It has Filament, Livewire, Inertia, Breeze, Jetstream, and a dozen other first-party-feeling packages. What it did not have, until now, was a content management system that treated the writer as a first-class user.

The options were all compromises. Bend WordPress into a headless API and write a Laravel frontend that fetches posts over REST. Use Statamic, which is excellent but opinionated about its own stack. Install one of the half-built abandoned CMS packages on Packagist and spend more time patching it than writing content. Or rebuild the wheel inside your own app, which most teams did, reinventing the same six resources badly every time.

LaravelDesign takes that last option and turns it into a package. The six resources every CMS needs — posts, pages, categories, tags, menus, media — shipped as Filament 3 resources with auto-discovery. A visual page builder for the pages that need it. A classic editor for the ones that don't. A storage-disk-agnostic media library. Frontend Blade components you drop in. Auto-registered routes. That's it.

The discipline here is in what it refuses to include. No SaaS tier. No plugin directory. No dictated theme. No auth layer beyond what Filament already gives you. The upsells — AI content assistant, premium themes, advanced blocks — ship as separate packages you opt into. The core stays small.

Laravel deserved a CMS built by someone who knows Laravel. This is it.