django CMS for publishers: placeholders, plugins and versioning

What is django CMS?

django CMS is an open-source content management system built on the Django web framework. The GitHub repository describes it as an open-source enterprise CMS and lists internationalisation, multi-site support, front-end inline editing, a placeholder and plugin system, content versioning, a hierarchical page tree with SEO-friendly URLs, and apphooks for integrating other applications. The project website says the django CMS Association, a non-profit run by volunteers, is its guardian. The licence file shows copyright held by Batiste Bieler from 2008, Divio AG and contributors until 2020, and the Association since.

Like Wagtail, it is added to a Django project rather than installed as a finished site. The documentation says a new project can be started with the djangocms command.

Who is django CMS best for?

django CMS suits publishers and agencies with Django developers who want editors to change pages on the live front end. Its placeholder model, in which a page template defines areas that editors fill with plugins, gives marketing and editorial teams flexible layout control without developer help for each page. Multilingual sites are a stated strength.

It is less obviously a news CMS. Nothing in the pages we opened describes article-centric newsroom tooling, and the named users on the project website include National Geographic, L’Oreal, NASA, PBS and Parrot, which is a mixed list. If your site is mostly a stream of dated articles with tags and feeds, check carefully that the model fits. A team without Python developers should look elsewhere in the directory.

Editorial workflow

The documentation lists content versioning and editorial workflow support, with front-end editing and live preview on the project website. The website says versioning is full, with change history and rollback. The versioning feature is provided by djangocms-versioning, a package maintained in the django-cms GitHub organisation. It is described as general purpose for django CMS 4 and above, adds drafts, versions and publishing states, and is compatible with versions 4 and 5.

We did not open documentation on roles, permissions, scheduling or approval steps, so we make no claims on them. Before shortlisting it for a newsroom, check how permissions map to desks and sections, whether scheduled publication is supported in your version, and how the versioning package handles review.

SEO, structured data and feeds

The repository describes a hierarchical page tree with SEO-friendly URLs. That is all the pages we opened say on the subject, so we make no claim about sitemaps, redirects, structured data or feeds. Templates are written by your developers, so meta tags and JSON-LD are developer work. Django has its own sitemap and syndication frameworks, but we did not verify how django CMS integrates them. The guides cover what Google’s documentation expects.

Media, multilingual and performance

Internationalisation is one of the first features the repository lists, and the website describes granular multilingual content management. We did not open the documentation on how translations are stored or switched, so check it for your language count. Media handling, image tools and caching are not covered in the pages we opened, and we state nothing about them.

Hosting and requirements

The documentation says django CMS 5.0.x supports Django 5.2, a long-term support release supported through March 2028, and the site lists a 5.2.0 development version. We did not verify Python version ranges or the list of supported databases. Treat both as items to check on the installation page, because they change with each release.

The website describes a cloud-native architecture built for Docker and containerised environments. As with Wagtail, any host able to run a Django application will do; see the self-hosted guide.

Extending django CMS

The plugin system is central: editors place plugins into page placeholders, and developers write new plugins in Python. Apphooks attach other Django applications to the page tree, so a news archive or events app can live inside the CMS navigation. The project website calls django CMS 5 headless-ready, but we did not open its API documentation, so we cannot say how complete that is. See our headless guide.

Because django CMS is a Django application, the wider Django package ecosystem is available. We did not verify the number of django CMS add-ons and quote none.

What django CMS costs

There is no licence fee. The website says there are no licence fees or vendor lock-in concerns, and the licence is BSD 3-Clause; our licence guide explains what that allows. The cost is developer time, hosting and maintenance. We found no public price for any hosted django CMS service in the pages we opened. The cost guide lists the categories to plan for.

Where django CMS falls short

• It is developer-assembled. A publisher without Django skills cannot run it alone.
• Versioning is a separate package, so confirm its status and compatibility on the version you choose.
• The pages we opened give no detail on permissions, scheduling, feeds or media tools. Evaluate those before committing.
• The project is run by a volunteer association. That helps independence, but support is not a vendor SLA unless you contract an agency.
• This assessment rests on documentation alone. See how we test.

The verdict for publishers

django CMS is a reasonable choice for a Django-based publisher that values front-end editing, a plugin model for layout and multilingual content. The BSD licence and the volunteer-run Association keep it free of licence fees and vendor control.

For a pure newsroom, a CMS with article workflows and desk-level permissions out of the box is a safer default, and Wagtail is the closer Python alternative with documented moderation workflows. Prototype django CMS against your own editorial process before committing.