Content: Blog

The first alpha of django CMS 5.1 has officially landed — and it marks an exciting step forward for the project.

Whether you're building complex multi-site platforms or crafting refined editorial experiences, 5.1 brings meaningful improvements you can start testing today.

🌟 A Fresh New Look for django CMS

One of the most noticeable updates in 5.1 is a refreshed interface design.

The UI has been modernized with:

• Improved contrast and accessibility

• Updated iconography

• Clearer visual hierarchy and spacing

• A more cohesive editing experience across admin and frontend

The result is a cleaner, more focused environment that feels at home in modern Django projects while preserving the workflow users know and love.

Need time to adjust? The legacy theme can still be enabled using: data-cms-theme="4"

🏗️ More Flexible Multi-Site Configuration

django CMS 5.1 significantly improves how you manage multi-site setups.

You can now:

• Run multiple sites from a single Django settings file

• Control whether the admin application is available per site

• Maintain cleaner separation between editorial and public-facing environments

For organizations managing multiple brands or deployments from one codebase, this unlocks a much smoother workflow.

🔌 Model-Specific Plugin Restrictions

Developers now have finer control over where plugins can be used.

With new allowed_models and Model.allowed_plugins options, you can:

• Restrict specific plugins to certain models

• Prevent misuse in unintended contexts

• Design safer, more structured content systems

This is a big win for larger projects with custom page models and editorial governance needs.

⚡ Enhancements & Performance Improvements

Beyond the headline features, 5.1 includes numerous refinements:

• Async support in middleware and apphook registration

• Apphooks now have access to root placeholders by default

• UX polish in external placeholders, preview handling, and redirect indicators

• Performance optimizations across key components

• Compatibility updates preparing for Django 6

It’s a steady evolution — focused on reliability, developer ergonomics, and long-term maintainability.

🛠️ Deprecations: Preparing for django CMS 6.0

Every strong major release begins with careful groundwork.

The 5.1 alpha begins deprecating legacy APIs in areas such as:

• Portions of the Page model

• Placeholder utilities

• Permission APIs

• Toolbar helpers

Nothing disappears overnight — but if you're maintaining custom extensions or integrations, now is the perfect time to test and adapt ahead of 6.0.

🧩 Compatibility Matrix

django CMS 5.1 supports:

• Django 4.2, 5.2, 6.0

• Python 3.11–3.14

This ensures continued compatibility with modern Django environments while future-proofing the platform.

🧪 Why You Should Test the Alpha

Alpha releases are about collaboration.

By testing django CMS 5.1 early, you can:

• Validate your plugins and extensions

• Provide feedback on the new UI

• Help identify edge cases

• Shape the direction of the final release

Your input now directly improves the stability and quality of 5.1 stable.

🚀 Get Involved

django CMS continues to evolve thanks to its community. Whether you're reporting issues, submitting patches, improving documentation, or simply testing the alpha — you’re part of shaping the next chapter.

The path to django CMS 6.0 starts here.

Install the alpha, explore the changes, and let us know what you think.

pip install django-cms==5.1.0a1