Content: Blog

django CMS core

At the core of django CMS, much of the work centered on stability and correctness in real-world setups. Multi-site support was strengthened, plugin handling became safer, and several tricky edge cases around apphooks and placeholders were resolved. Alongside this, improvements to the CI and testing setup ensure that the project is better aligned with modern Django versions and better prepared for long-term maintenance. These changes may not always be visible at first glance, but they make a significant difference for larger and more complex installations.

djangocms-frontend

On the frontend side, the focus was on making things more robust and predictable for both developers and editors. Rendering behavior was hardened, safer defaults were introduced to avoid unnecessary failures, and documentation for component authors was improved. Together, these refinements make it easier to build custom components while reducing friction during day-to-day development.

djangocms-rest

Headless support reached an important milestone during this cycle. With recent improvements to djangocms-rest, the REST API is now production-grade, offering clearer schemas, more predictable behavior, and better documentation. This positions django CMS as a strong option not only for traditional websites, but also for modern, API-driven architectures where content needs to be delivered across multiple channels.

Many other improvements

Media handling and content applications also benefited from focused attention. django-filer saw improvements through refactored JavaScript dependencies, resulting in a more stable media browsing experience and fewer UX regressions. At the same time, djangocms-stories received a series of bug fixes that improved admin workflows, increased test coverage, and reduced the number of unexpected behaviors editors might encounter.

🌐 New website

In parallel to the core and ecosystem work, significant progress continued on django-cms.org. Carl, Max, and Sal have been driving the new website forward with a modern frontend architecture, improved navigation and layout, and an expanding set of reusable content plugins. The site is steadily becoming a living showcase of what django CMS can do today — both technically and creatively.

🙌 Community

This period also brought new voices into the project. First-time contributors made meaningful improvements right out of the gate: clearer documentation for frontend components, more graceful handling of optional dependencies, and subtle but important fixes in core editing workflows. These contributions highlight how even small, well-scoped changes can have a real impact — and how essential new contributors are to the health of the project.

• creimers improved the template components tutorial in djangocms-frontend, making field attributes clearer for developers.
• kunaly111 <meta charset="UTF-8">strengthened djangocms-frontend by ensuring it fails gracefully when django-filer isn’t installed.
• 줄리엣 <meta charset="UTF-8">fixed an edge case in django CMS core where page_title could be empty in frontend edit mode for apphooks.

🔎 What's coming up?

Looking ahead, the conversation is already turning toward what comes next. Two initiatives are currently shaping the future direction of django CMS. One explores the potential role of AI and LLM-assisted workflows, such as editorial assistance, SEO suggestions, or safe “copilot”-style features within the CMS. The other proposes a framework to make it easier to integrate custom Django models as first-class CMS content, reducing boilerplate and supporting richer domain-driven applications.

✨ django CMS 5.1 (alpha)

As we prepare for the django CMS 5.1 alpha release, community involvement is more important than ever. Testing early releases, sharing real-world use cases, and participating in discussions all help ensure that 5.1 is not only feature-complete, but genuinely useful in practice.