Wagtail for publishers: a Django CMS built around editors

What is Wagtail?

Wagtail is an open-source content management system built on the Django web framework. Its repository describes it as “a Django content management system focused on flexibility and user experience” and lists the BSD-3-Clause licence. Wagtail’s About page says it was created by Torchbox, a web development company, and reports more than 1,000 contributors since 2014. It also says Google sponsored development of new content management features.

Wagtail is not a ready-made site. You add it to a Django project, define your page types in Python, and write the templates. What it provides is the editing interface and the content tooling around that code.

Who is Wagtail best for?

Wagtail suits a publisher or agency with Python developers that wants a custom content model and a clean editing experience. A magazine with distinct article types, such as features, galleries, long-form and live pages, can model each as a page type and let editors assemble pages with StreamField, the flexible content field the vendor highlights.

It is a weaker fit for a small team that wants to install a theme and start writing. Nothing here comes pre-built as a news site; you or an agency build it. Publishers whose developers know PHP or .NET would be starting a new stack. We found no official Wagtail page that names a news publisher as a user, so we do not claim one. The official pages name organisations such as Google, NASA and the NHS.

Editorial workflow

The features page lists customisable workflows that control who can moderate, review and publish, scheduled publishing with expiry dates, and revision comparison. In the permissions documentation, permissions attach to pages and cascade down the page tree. The permission types are add, edit, publish, bulk delete and lock/unlock. A group with edit rights on a section automatically gets them on the pages beneath it.

Users without publish rights can submit changes for moderation. The documentation also notes that editing a page implies the ability to delete it, because there is no separate delete permission, so give edit rights carefully.

Creators of pages become their owners, which supports drafting over several versions. For a newsroom this gives you desk-level permissions by section, a review step before publication and scheduled go-live. Multi-stage approval chains beyond the configurable workflows would need checking against your process.

SEO, structured data and feeds

Wagtail’s contrib sitemap module builds on Django’s sitemap framework. Once enabled in INSTALLED_APPS and urls.py, it adds all published pages to sitemap.xml, and a page type can customise its own entries. The redirects contrib app is optional. It creates permanent redirects automatically when pages are moved or slugs change, and an import_redirects command handles bulk imports, which helps with migrations.

We did not verify documentation for structured data, news sitemaps or RSS feeds, so we make no claim about them. As with any framework, the templates are yours: titles, meta descriptions, canonical tags and JSON-LD are things your developers build. The guides explain what Google’s documentation asks for.

Media, multilingual and performance

The features page lists image management with focal point and custom cropping tools, multiple upload and image deduplication. For languages, Wagtail’s i18n documentation says content is stored in a separate page tree for each locale, with a translation key linking translations. A basic Simple Translation module lets editors copy pages for translation. The separate wagtail-localize package, described in the documentation as third-party, adds PO files, machine translation and external services.

On caching and speed, the pages we opened give no figures and we state none. Wagtail runs as a Django application, so caching and CDN choices are the same as for any Django site and sit with your developers.

Hosting and requirements

The installation documentation says Wagtail is currently compatible with Django 5.2, 6.0 and 6.1, and that the Pillow imaging library is installed with the package and needs system libraries such as libjpeg and zlib. We did not confirm the supported Python versions or databases from the pages we opened, so check the current installation page. You run python manage.py migrate to create the tables.

Because Wagtail is a Python application, any host that can run Django will do. See our self-hosted guide for what running your own server involves.

Extending Wagtail

The v2 API is a stable, read-only interface built on Django REST Framework, intended for non-web clients or for using content in another site. Wagtail 8.0 adds a preview v3 REST API built on Django Ninja that the release notes say can create, edit, publish, unpublish, move, copy and revert content. A preview feature is a risk for production work, so confirm its status before depending on it.

The 8.0 notes also describe custom base page models, which apply only to new projects, and a permission policy registry. Because Wagtail sits inside Django, the Django package ecosystem is available too. We have not verified the size of the Wagtail-specific package ecosystem and give no count.

What Wagtail costs

The licence is free. The costs are developers, hosting and maintenance. Because you build the site, the first build is the bulk of the expense. Our cost guide lists the categories, and the licence guide explains what BSD-style terms allow.

We did not find a vendor-run hosted Wagtail service in the pages we opened and quote no hosted price.

Where Wagtail falls short

• It is a framework, not a finished site. Every Wagtail site needs Python development.
• Several useful features are optional contrib apps or third-party packages, including sitemaps, redirects and wagtail-localize. Each adds a dependency to maintain.
• Version 8.0 introduces a preview REST API. The stable read-only v2 API remains, but write access is still in preview.
• Upgrades follow Django’s, so you plan for Django version changes. The 7.4 series is marked LTS, which gives a slower path.
• This is a documentation-only assessment. See how we test.

The verdict for publishers

Wagtail is one of the strongest options when your developers write Python and you want editors to get a tailored, uncluttered admin. The permissions, workflows, scheduling and revision tools cover the daily needs of an editorial desk, and the BSD licence leaves you free to build commercially.

It is the wrong choice if you want a finished news theme out of the box or have no developer to rely on. Compare it with similar developer-led options on the CMS directory, including django CMS, and try a prototype before committing.