Craft CMS for publishers: flexible content modelling at a licence fee

What is Craft CMS?

Craft CMS is a PHP content management system made by Pixel & Tonic, Inc. Its repository describes it as a CMS with a control panel, clean-slate content modelling, Twig-based templating, an auto-generated GraphQL API, ecommerce capabilities and a plugin ecosystem. It is built on the Yii 2 framework, which its repository lists among its topics.

Craft ships almost nothing prescriptive. You define sections, fields and layouts, and a developer builds the templates. For a publisher, that means the site can match how the newsroom thinks, but someone has to build it.

Who is Craft CMS best for?

Craft fits magazines, digital publications and media companies that have a developer or agency, want a tailored editorial interface and are happy to pay a modest licence fee instead of assembling plugins. Complex content, such as articles with multiple contributors, series, events and sponsored sections, is the sweet spot.

It is a poor fit for a volunteer-run site, a publisher with no developer, or someone who wants to install a theme and start writing. The licence cost is small against agency time, but it is a cost, and a team that wants everything free should look at the open-source profiles in the CMS directory.

Consider a regional magazine with print and digital editions, sponsored content and an events calendar. Craft lets a developer give each of those its own section and field set, so editors see a form that matches the job instead of a generic post editor. A single-author blog gets little from that flexibility and would pay for it in build time.

The practical test is whether anyone on the team can write Twig and PHP, or whether you will retain an agency. If the answer is neither, price that gap before the licence.

How does Craft CMS handle editorial workflow?

Everything in Craft is an element. The documentation lists Addresses, Assets, Categories, Entries, Global Sets, Tags and Users as the core element types, and says custom fields attach to elements through field layouts. Articles are entries inside sections you design.

Drafts let editors fork changes from the canonical version without publishing them. When a draft is applied, Craft copies the previous version into a revision, so earlier states can be audited and recovered.

User access depends on the edition. The documentation says Solo is limited to one admin user, Team allows up to five users and one user group, and Pro has no limit. Permissions cover things like control-panel access and editing within particular sections, and permissions granted by multiple groups add together. A newsroom with more than five staff needs Pro.

SEO, structured data and feeds

The Craft documentation pages we opened do not describe built-in meta fields, sitemaps or feeds, so we do not claim any. The plugin store lists an SEO plugin by Ether Creative (MIT licence, version 5.0.0, compatible with Craft 5) that provides an SEO field type with search preview, a sitemap manager and a 301 and 302 redirect manager.

Structured data, RSS and Google News requirements are normally handled in Twig templates, which gives control but means a developer writes them. Check the current docs for anything you rely on and follow Google’s own documentation on structured data.

Media, multilingual and performance

According to the documentation, one Craft installation can power any number of websites, with different domains and templates, and entries have propagation rules for sharing content between sites. That is the multi-language mechanism: each language or region is a site.

Static interface text goes through a translation system with a template filter and a PHP method. The pages we opened did not cover image transforms or caching, so we make no claims about them. See the feature checklist for what to ask.

Hosting and requirements

Craft 5 requires PHP 8.2 or later and Composer 2.0+. The database can be MySQL 8.0.17+, MariaDB 10.4.6+ or PostgreSQL 13+, with MySQL 8.0.36+ and PostgreSQL 16+ recommended. The documentation asks for at least 256 MB of memory for PHP and recommends 512 MB, and no longer recommends MariaDB for sites with many users or a large volume of content.

Craft Cloud is the vendor’s hosted option. The pricing page says Team and Pro licences are free on Craft Cloud; it does not list the hosting charge in the text we read, so check it separately. The self-hosted guide covers the work involved in running your own server.

Extending Craft CMS

Plugins are listed in the Craft plugin store, and the core repository describes a plugin ecosystem and extension framework. We have not verified the number of plugins, so we do not quote one.

For decoupled front ends, Craft provides a GraphQL API for separate applications such as single-page apps and static site generators. The project also advertises ecommerce capabilities, which matters if the publication sells subscriptions, events or merchandise, though we have not reviewed that product.

What does Craft CMS cost?

Per the pricing page on 2026-10-10: Solo is free, Team is $279 per project, Pro is $399 per project and Enterprise has custom pricing. Team and Pro include one year of updates and then cost $99 a year for updates. The page shows dollar amounts without naming the currency. Non-profits receive 15% off Team and Pro licences, excluding renewal fees.

The licence says a licensed copy may be actively installed in no more than one production environment at a time, so each production site needs its own licence. Add hosting and, above all, development: the licence is the smallest line in a Craft budget. Our cost guide sets this against other systems.

Worked through for a typical publication, the edition decision is driven by headcount before features. Solo is one admin account, Team stops at five users, and Pro removes the cap, so a newsroom of eight needs Pro on that basis alone. Renewals matter too: a publication that wants security and feature updates each year budgets the yearly update fee per project, and a publisher running several separate sites needs a licence for each production installation.

Where does Craft CMS fall short?

• Developer-dependent. The editorial interface is only as good as the build; there is no ready-made newsroom theme in the sources we read.
• Licence fees recur. Updates after the first year cost $99 a year, per project.
• User caps. Team allows five users and one user group, so a growing desk needs Pro.
• Features we could not verify. Built-in SEO fields, sitemaps, feeds and caching are not described in the pages we opened.
• Not open source. The licence permits one production installation per licence, which limits reuse.

The verdict for publishers

Craft is a good choice when a publication has unusual content, a developer on hand and a budget for a modest licence. Drafts, revisions, groups and a clean content model give editors a tidy workspace, and the GraphQL API leaves a headless route open.

It is the wrong choice if the aim is the cheapest possible site or the largest pool of ready-made plugins. This profile rests on vendor documentation, not on a test install; see how we test.