Content: Roadmap

Official roadmap

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

This is our roadmap

django CMS 3.4 (LTS) Released
This release is lead by  Divio

3.4 will be our first Long Term Support (LTS) release. Long-term support means that this version will continue to receive security and other critical updates for 24 months after its first release. Any updates it does receive will be backward-compatible and will not alter functional behaviour. This will enable users to deploy this version without needing to perform any updates (other than for security and other critical updates) until the next LTS release. This release will not incorporate major features but rather focus on:

  • Code cleanup (Permissions, Revision, Alias)
  • Improvements, particularly in speed, to the editing experience
  • Improvements to placeholder configuration
  • Real content preview in edit mode and the djangocms-text-ckeditor
  • Revision has been removed
  • Defining core and supported addons
  • LTS documentation and advertising
  • Add Django 1.10 support (waiting for django-treebeard)

django CMS 3.5
This release is lead by  Divio

This release will introduce new features and enhancements. The aim is to make it easier to edit, preview and access content on an overall scale. Several features beneath are being developed alongside 3.4 and might be merged to 3.4 (marked as checked).

  • Further accessibility improvements
  • Removal of revision in 3.4 requires a separate addon
  • RESTful API for headless use of the CMS as separate Addon.
    Commercially backed by Nephila and SteelKiwi.
  • Multiple menu support
  • Moderation enhancements

We are actively looking for help on the above mentioned topics

Get in touch with us

The roadmap is subject to change at any time.

How to contribute

Here’s what the contribution process looks like in brief

Step 1

Create an account on GitHub, checkout the project at https://github.com/divio/django-cms 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


Developers

Everything you need to know about django CMS

Documentation
Follow django CMS

Stay up to date about new product releases