Working on Django 3.1 support
Django 3.1 has been released and we're working towards support in our next release: django CMS 3.8.0.
Now that Django 3.1 is available, various packages are in the process of upgrading their code-base to support the latest release. Aligned with our roadmap, so are we!
We have started the process of upgrading django CMS, its dependencies and the core addons to support Django 3.1. We expect a release of django CMS 3.8.0 in August or September, depending on how fast external dependencies are updated.
django CMS 3.8.0 will drop support for Python versions below 3.5 (including Python 2.x) as well as Django versions below 2.2. django CMS 3.8.0 will officially support Python 3.5+ and Django 2.2, 3.0 and 3.1. This will also apply to all django CMS maintained dependencies (e.g. django-sekizai, django-classy-tags) and core addons (e.g. django-filer, djangocms-text-ckeditor).
We strongly recommend upgrading from Python 2.x to at least 3.5 as well as from Django 1.11 to at least 2.2. If this is not possible for you, now would be a good time to pin requirements in existing projects to the versions you are using now. Otherwise, new releases of dependencies are very likely to break your project.
Once django CMS 3.8.0 has been released, support for 3.6.x will be dropped. We strongly recommend upgrading to django CMS 3.7.x (LTS) as soon as possible if you are still using 3.6.x.
Please note that django CMS 3.4.x (LTS) and django CMS 3.5.x are no longer supported and will not receive any further security updates.
Angelo Dini
Release
django CMS 5.1 is here: easier setup, flexible deployments, and a fresh editing experience
This release reduces friction across the whole project lifecycle: creating a new project, adding django CMS to an existing Django application, configuring larger deployments, controlling which plugins editors can use, and working with the CMS every day.
Release
django CMS 5.0.9 released: security, accessibility, and stability improvements
This release addresses three medium-severity security vulnerabilities and includes improvements to accessibility, Django compatibility, permissions, Content Security Policy support, and general editor stability.
Case Studies
How we built our professional services digital platform using django CMS
Compound Partners is a UK digital consultancy specialising in audience-centric user experience and content architecture for professional services firms. Fifteen years ago, a developer's recommendation pointed us at django CMS. Today, our entire business is built on it.