Weave Code
Cms Laravel Package
statamic/cms
Statamic is the flat-first, Laravel + Git powered CMS for building beautiful, easy to manage websites. This package is the core Composer library installed into an existing Laravel app, offering extensive documentation, community support, and official Pro support.
Statamic is a flat-first, Laravel + Git powered CMS for building beautiful, easy-to-manage websites. Instead of a database, content lives in flat files (Markdown and YAML), making it portable, human-readable, and version-controlled alongside your code.
Installed as the core Composer package into an existing Laravel app, Statamic pairs a polished control panel with a flexible templating layer and full extensibility.
- Flat-file content as Markdown/YAML, versioned in Git
- Laravel-native — extend with any Composer package
- Customizable control panel with rich fieldtypes
- Antlers and Blade templating for full front-end control
- Multi-site and localization support
Frequently asked questions about Cms
- What is statamic/cms and is it a standalone CMS?
- statamic/cms is the core Composer package for Statamic, a flat-first CMS powered by Laravel and Git. It is not a standalone CMS; it installs into an existing Laravel application. For greenfield projects, start from the official statamic/statamic application repository rather than assembling the integration manually.
- How do I install statamic/cms into an existing Laravel application?
- Install statamic/cms via Composer into an existing Laravel app, or start a new project from the official statamic/statamic application repository. Plan integration work such as content directory layout, Git workflow, asset storage and CDN, caching, search indexing, queue workers, scheduled tasks, control panel auth and SSO, roles and permissions, and deployment automation. Design content storage and publishing workflow early, because production write access to flat files and Git is the critical architectural decision.
- Which Laravel and PHP versions does statamic/cms support?
- The provided context does not list exact Laravel and PHP version constraints; check the package's composer.json and release documentation for the target version. Confirm supported Laravel/PHP versions before planning an upgrade. Statamic has frequent minor and patch releases, so version support and patch policy should be part of your upgrade plan.
- Is Statamic suitable for non-technical editors who need complex publishing workflows?
- Statamic's flat-first, Git-powered model is a strong fit for developer-controlled versioned content, releases, and GitOps-style deployment. It is a weaker fit if non-technical editors need high-concurrency, database-backed publishing with complex approval workflows unless those workflows are explicitly validated. Confirm the editorial workflow, permissions, and conflict-resolution model before committing.
- How does Git-based content work in Statamic and what are the operational risks?
- Statamic stores content in flat files that are versioned in Git, which supports versioned content and developer-controlled releases. The main operational risk is coupling editorial publishing to engineering deploy processes, along with Git repository growth, merge conflicts, editor concurrency, large asset libraries, search performance, and multi-environment content sync. Define who owns merges, releases, and conflict resolution, and benchmark these concerns against expected content volume.
- What are the licensing and cost considerations for statamic/cms?
- The package license is marked NOASSERTION, so legal review is mandatory before adoption. Statamic has a free core and paid Pro/support tiers, so confirm SaaS, agency/client, redistribution, upgrade, and addon licensing obligations. Evaluate required Pro features, support tier, and addons to determine total cost of ownership.
- How does statamic/cms handle security patching and maintenance?
- Statamic has a significant security-sensitive surface area, and changelog entries show repeated hardening around SVG sanitization, path traversal, endpoint authorization, password reset, CSP, revision routes, and 2FA. That is positive maintenance activity, but it also means delayed patching is a real risk. Define a security patch SLA and confirm your team can apply upstream releases quickly.
- Can I use statamic/cms as a headless CMS or with GraphQL/REST APIs?
- API and headless use is feasible with Statamic, but validate GraphQL and REST coverage, preview tokens, caching behavior, and multi-site/localization support against your omnichannel requirements. Confirm whether the features you need are native, Pro, or addon-dependent. This validation should happen before committing to the platform.
- What integration work is required for production with statamic/cms?
- Production integration includes content directory layout, Git workflow, asset storage and CDN, caching, search indexing, queue workers, scheduled tasks, control panel auth/SSO, roles and permissions, and deployment automation. Existing Laravel apps can integrate incrementally, but content storage and publishing workflow must be designed early. Production write access to flat files and Git is the critical architectural decision.
- What upgrade, maintenance, and exit risks should I consider with statamic/cms?
- Upgrade risk is moderate to high because of frequent minor and patch releases, frontend/Vue dependencies, npm supply-chain exposure, and potential addon or fieldtype incompatibilities. Test upgrades against your addons and fieldtypes, and confirm the patch policy before launch. Also define an exit strategy covering content portability, URL preservation, data export, and fallback if the package is abandoned or licensing changes.
Weaver
How can I help you explore Laravel packages today?