Technical articles | November 12, 2009

Roadmap after 2.0.0

Now that 2.0 has landed we would like to talk about the future.

5 minutes read

We already have a frontedit branch with the frontend editing functionality and some other new features. Also a new Dashboard for the standard django admin is in the works. These features will be in 2.1. If you have your own pony you would like to see it in 2.1:

  1. Create a ticket on [github](https://github.com/divio/django-cms/issues).
  2. Vote in the issue tracker at: https://github.com/divio/django-cms/issuesor fork and start coding :)

A target date for 2.1.0 will be end of year or January. In mid December we will have a feature freeze.

The road to 2.2

For 2.2 we will see a major refactoring coming along that already started in the newadmin branch with the help of [fivethreeo](https://github.com/divio/django-cms/).

  • The current monolithic admin classes will be split.
  • the plugins will be working in other apps
  • the tree will be working in other apps
  • the menu will get its own app.

A target date for this is not yet set but will probably be somewhen in summer 2010.

Mike Barrett

Article

The next chapter of django CMS starts with our members, past, present and future.

Mike Barrett, elected President of the django CMS Association for 2026 to 2028, thanks Mario Colombo and Joel Burch and sets out three priorities: a more valuable membership, an easier choice for agencies, and meeting in person at DjangoCon Europe.

Article

Hunting Down Quadratic Loops in django CMS

How PR #8913 removed quadratic work from django CMS menus, plugins, and page permissions: a permission-heavy menu on a 4,000-page site went from 11.7 seconds to 105 ms.

Article

One operation, three interfaces: a service architecture for django CMS

How shared content operations could support editors, REST integrations, and AI tools.