Content: Blog

With the latest release of djangocms-text-ckeditor5, CKEditor 5 now achieves full feature parity within the djangocms-text ecosystem. The final missing capability—support for text-enabled CMS plugins—has officially landed.

At the same time, the broader architecture has evolved: Tiptap remains the default editor, while CKEditor 5 is positioned as a fully supported alternative for teams that prefer its ecosystem and editing model.

A New Editing Architecture

The introduction of djangocms-text brought a fundamental shift:

• Editors are now swappable
• Content handling is more structured and flexible
• The system is designed for long-term extensibility

Within this architecture:

• Tiptap provides a modern, default built on ProseMirror focusing on text structure
• CKEditor 5 integrates as an optional, feature-rich HTML-oriented editor alternative

This dual approach gives teams freedom of choice without fragmenting the ecosystem.

The Missing Piece: Now Delivered

Until recently, CKEditor 5 integration had one major limitation: ❌ No support for text-enabled CMS plugins

This meant that while basic editing worked in environments where text-enabled CMS plugins are not used, more advanced Django CMS workflows — especially those embedding plugins inside text — were not fully supported.

✅ With the latest release of djangocms-text-ckeditor5, that gap is closed. CKEditor 5 now fully supports CMS plugins:

• Embedding text-enabled CMS plugins directly within content
• Inline editing of plugin-rendered elements by double clicking
• Adding text-enabled plugins from a dropdown or the editor toolbar itself

In practical terms, CKEditor 5 can now do everything teams previously relied on in CKEditor 4—without compromise.

Where This Leaves Us

With full support for text-enabled CMS plugins, CKEditor 5 is now a complete, production-ready editor within djangocms-text.

At the same time, Tiptap as the default reflects the shift toward more structured content—without taking away choice.