Statamic

Content kept in a database sits outside version control. Statamic takes the other road, a flat-first content management system powered by Laravel and Git, where the content of a site has the same history, review and rollback story as its code.

This repository holds the core Statamic Composer package, meant to be installed into a Laravel application you already have. A separate application repository holds a Laravel app preconfigured with Statamic, and that is what the Statamic CLI tool starts from when you create a new project.

A few consequences follow from that arrangement.

• Laravel-native: the CMS is a dependency of your application, so routing, packages and deployment stay the way Laravel already does them.
• Git-powered content: content changes travel through the same branches and reviews as everything else in the repository.
• Two entry points: add Statamic to a running app through Composer, or scaffold a fresh project with the CLI.
• Migrator: a companion Statamic Migrator project is maintained alongside the core package.
• Documentation: an extensive docs site is maintained daily, and the team treats anything unclear or incomplete as an issue worth filing.

Support is split by audience. Official developer support comes with Statamic Pro projects, while community help runs through GitHub Discussions and a Discord server. Contributions are welcome once you have read the contribution guide, and the project asks everyone taking part to abide by its code of conduct.