Content: Roadmap

Official roadmap

django CMS is always looking for motivated people to contribute to its source code

Do you want to know where the future of django CMS is heading?

Check out our workgroups to see on what new features or improvements the open-source community is currently working on

Go to workgroups
This is our roadmap

...Help us shaping the django CMS roadmap - send us your suggestions!



django CMS 3.8 

Q2/Q3 2020

  • Adding support for Django 3.1
  • Dropping support for Python 2, supporting Python 3.5+
  • Dropping support for Django < 2.2, supporting Django 2.2, 3.0 and 3.1

django CMS 3.7 (LTS)


  • Our next Long Term Support release, replacing 3.4
  • Added support for Django 2.2 (LTS)
  • See full release notes

django CMS 3.6


  • Added support for Django 2.0 and 2.1
  • Removed support for Django versions older than 1.11
  • See full release notes

django CMS 3.5


  • Separated structure board from content
  • Pages can now be copied between sites
  • See full release notes

django CMS 3.4 (LTS)


  • Our first Long Term Support release
  • Added auto reload capabilities to plugins for faster rendering
  • See full release notes
How to contribute

Here’s what the contribution process looks like in brief

Step 1

Create an account on GitHub, checkout the project at and create your own personal fork. Browse through the open issues starting with the "easy pickings".

Step 2

Pick an issue and make your intentions clear in the comment section. Start creating a patch on your own fork, get help from the core developers, provide meaningful comments and information about your work.

Step 3

When you feel your code is good enough for inclusion, “send us a pull request” from your fork, by using the nice GitHub web interface. A core developer might provide feedback with eventual code changes.

For more information visit the full guide published in the django CMS Docs

Find us and talk with django CMS core developers at these events

Next events