Statamic CMS: Flat-First CMS for Laravel

Understanding Statamic's Core

Statamic CMS is a Composer package that adds flat-first, Git-powered content management to an existing Laravel application. This repository, statamic/cms, is specifically the core package meant to be installed into a Laravel app you already have — a separate application repository, statamic/statamic, ships a Laravel project pre-configured with Statamic, used together with the Statamic CLI tool when starting a brand-new project instead.

Key Capabilities of Statamic

• ✓Flat-first content storage: content lives in files tracked by Git rather than requiring a live database connection for every read, per the README's description of Statamic as 'flat-first, Laravel + Git powered.'
• ✓Ships as a Composer package (statamic/cms) that installs into an existing Laravel application, rather than a standalone app you deploy on its own.
• ✓A separate application repository, statamic/statamic, provides a Laravel project pre-wired with Statamic, used when scaffolding a new project through the Statamic CLI tool.
• ✓GitHub tags this repo with headless, GraphQL, api-rest, and jamstack topics, alongside ssg and vuejs — pointing at a CMS built to serve content beyond server-rendered PHP templates alone.
• ✓Official developer support is available for Statamic Pro projects, per the README, with community support running through GitHub Discussions and a Discord server for everyone else.
• ✓Extensive documentation lives at statamic.dev, and the README says the team spends time daily improving it and welcomes issues on anything unclear or incomplete.

Installing the Statamic Core Package

The README doesn't list an explicit composer require command or version requirements in the facts available here — it confirms this package is meant to be installed into an existing Laravel application, but exact install steps aren't spelled out beyond that. If you're starting a brand-new project instead of adding Statamic to one you already have, the README points to a separate application repository, statamic/statamic, preconfigured with Statamic and used together with the Statamic CLI tool. Full documentation lives at statamic.dev, which the README calls the place to go if any step is unclear.

Developing with Statamic

Day-to-day usage isn't walked through in the facts available here beyond the high-level architecture: content sits in flat files under Git version control inside your Laravel app, rather than living only in database rows. The repo's topics list graphql and api-rest, suggesting content can be pulled out through an API layer as well as rendered in templates, and vuejs is tagged too, hinting at a JavaScript-driven front end being a supported pattern. Specifics of routing, templating, or the control panel workflow aren't documented in what's provided here — the README defers to statamic.dev for the full picture.

Statamic Alternatives

Statamic CMS FAQs

The problem it solves

Adding real content management to a Laravel app usually means wiring in a database-driven CMS package with its own admin tables and migrations, or building an ad-hoc admin panel from scratch. Statamic's README frames its own answer as flat-first: content stored in Git-tracked files that live alongside your Laravel codebase, so content changes travel through the same version-control history as your code instead of sitting only in database rows.

Best use cases

• •Adding a CMS to an existing Laravel application without introducing a second framework, since Statamic installs as a Composer package into the app you already have.
• •Starting a brand-new Statamic-powered site using the separate statamic/statamic application repository together with the Statamic CLI tool, instead of wiring the package in by hand.
• •Wanting content history in Git alongside code history, since Statamic's flat-first storage is built around files rather than only database rows.
• •Serving content to a decoupled or JAMstack front end, given the repo's graphql, api-rest, ssg, and jamstack topic tags.
• •Teams that expect to need official developer support, by budgeting for a Statamic Pro plan rather than relying solely on community help.

Who should try it — and who should skip

Try Statamic CMS if you're already building on Laravel and want content stored in Git-tracked flat files instead of exclusively in a database, especially if you're comfortable installing a Composer package into an app you control end to end. Skip it if you're not working in Laravel/PHP, need a CMS that runs standalone without a host application, or need guaranteed developer support without budgeting for a Statamic Pro plan.

Related repositories