Statamic
What is Statamic CMS?
Statamic is a content management system (CMS) built on Laravel, the PHP framework. It stores content in files instead of a database: every page, entry and setting is a Markdown or YAML file in the project.
Editors work in a control panel, as in any other CMS. Behind it, the content lives in the same repository as the code, so Git keeps track of every change.
We build websites on Statamic because it runs on Laravel, the same base as many of the web applications we build and maintain. That makes it straightforward to connect a site to the systems behind it, such as a portal or a back office.
How Statamic Works
Content in Files
Statamic reads the files, builds an index from them (the Stache) and caches the result, so pages do not depend on database queries. For very large sites, or content that changes all the time, Statamic can store content in a database instead.
Version Control
History: Git keeps a record of every change
Traceable: you can see who changed what, and when
Reversible: any change can be rolled back
Test to live: content moves along with the code
Complete copy: a copy of the repository includes all content
For Editors
Control panel: pages, entries and media in one place
Bard editor: text and reusable content blocks in one field
Live preview: see a page before it goes live
Multiple languages: each entry can have a translation per site
Forms: built-in forms, with submissions stored and sent by email
For Developers
Laravel underneath: custom features are written as regular Laravel code
Blueprints: the fields of each content type are defined in files
API access: content can also be read through an API, for a separate frontend
Git: content and code live in one repository
Addons
Advanced SEO by aerni is the addon we use for search engine optimization. It handles meta titles, descriptions, sitemaps and social sharing images, and this site runs on it too.
When a Flat-File CMS Fits
A flat-file CMS fits sites where a small team manages the content and editors rarely work on the same item at once. A CMS with a database fits better when visitors create content themselves, or when many editors change the same content at the same time. The main differences:
Topic | Flat-file CMS (Statamic) | Database CMS |
|---|---|---|
Storage | Text files in the project | Tables in a database |
Speed | Fast by default, through caching | Can be just as fast with caching |
Security | No content database to attack | Depends on updates and plugins |
Maintenance | Updated with Composer, along with the code | Core, theme and plugins often updated separately |
Large volumes | Works for most sites; database storage is optional | Built for large volumes from the start |
Extensions | Fewer addons; custom work in Laravel | Often a large plugin ecosystem |
Editors | Control panel with live preview | Control panel, often familiar to editors |
Editing at once | Best when editors rarely edit the same item at once | Handles many editors at once |
Version control | Content in Git by default | Content stays in the database |
Hosting | PHP hosting, no database needed for content | Always needs a database |
When Statamic Is a Good Fit
Statamic works well for:
Company websites with a clear structure and a small editorial team
Sites that share data with a web application, such as a portal or a back office
Multilingual sites, managed from one control panel
Blogs and knowledge bases with structured content
Look further if:
You need a wide range of ready-made plugins
Visitors create content themselves, as in a forum or a marketplace
Many editors work on the same content at the same time
Statamic keeps content and code in one place. That makes a site easier to maintain over the years.
FAQ
Need help with Statamic?
Our team has extensive experience working with Statamic. Let us help you build, integrate, or optimize your project.
Explore our services