Note

This section describes how to activate a preview version of the CKEditor 5 in CoreMedia Studio. To learn about how to customize the current default editor (CKEditor 4), see Section 9.6.5, “Customizing RichText Property Fields” instead.

In one of the early AEP releases of CoreMedia Content Cloud v11 the default editor in CoreMedia Studio will change from CKEditor 4 to CKEditor 5. While you may stick with CKEditor 4 throughout the lifetime of CoreMedia Content Cloud v11, new features will only be implemented for the new richtext editor. As such, we discourage customizing the CKEditor 4 based rich text editor – and if required, ensure to keep a specification as it is likely, that you will have to rewrite the customizations for CKEditor 5. If you plan to start migrating or adding new plugins before the next release, you can already switch to a preview version of CKEditor 5 in CoreMedia Studio. This chapter describes how to activate the CKEditor 5 preview and guides you through the process of adding different builds with customizations in the Blueprint.

Warning

Do not use CKEditor 5 in production environment. Using CKEditor 5 in this early stage may or will modify your richtext data when loaded into CoreMedia Studio. This is because some valid CoreMedia Richtext 1.0 elements and attributes are not supported yet. When loaded from server, such yet unknown elements and attributes will be removed from XML.

Also, be aware that the CKEditor 5 preview still has a limited feature set and is e.g. missing the following features: