Studio Developer Manual / Version 2310
Table Of ContentsIf you followed the upgrade steps from CKEditor 4 to CKEditor 5 or if you compare the CKEditor integration in previous versions of CoreMedia Content Cloud with the current integration, there are some differences worth mentioning. At least some of them are directly visible to editors who are used to working with CoreMedia Rich Text 1.0 with CKEditor 4 in CoreMedia Studio.
Here is a short overview:
Style and Position of Teasers: For CKEditor 4 choosing a style and position was integrated into the toolbar of CKEditor 4. For CKEditor 5 they are now independent components. This reflects the content state much better, as their state never was related to the edited CoreMedia Rich Text 1.0.
No Fallback to Article Text for Teasers: For CKEditor 4 if you have neither selected a style nor modified the text, a fallback text to Article Text was displayed for Teaser Text. For consistency reasons, this feature has been removed as the actual behavior is triggered in delivery and the simulated state in CoreMedia Studio always only was a restricted preview of what is eventually rendered on the web page.
Default CKEditor for Teaser Text: For CKEditor 4 you had only a limited set of formatting options in its toolbar for Teaser Text. With CKEditor 5 the default editor also used for Article Text is used. This addresses a lot of issues, which existed for the CKEditor 4 solution not only regarding hardly predictable copy and paste behavior but also regarding valid CoreMedia Rich Text 1.0 set for Teaser Text triggered by the Unified API, for example.
Combined Content and External Links: In CKEditor 4 you were used to having two toolbar buttons: One for creating links to contents and another for creating external links. In CKEditor 5 both approaches were combined so that you can now transparently switch from content link to external link and vice versa and both provide the same options regarding the target behavior, for example.
Pure CKEditor 5: The editing area as well as the toolbar and dialogs are now provided by CKEditor 5. For CKEditor 4 toolbar and dialogs based on Ext JS which were rather some kind of remote control for CKEditor 4.
This provides subtle differences compared to other dialogs and toolbars within CoreMedia Studio. But it comes with the great benefit of less friction between both frameworks — not to mention the much easier way of integrating new plugins. You can take them directly from the rack, that is, you just take the CKEditor 5 plugins and apply them to your configuration without (much) additional effort.
For details have a look at Section 10.1.3, “CKEditor 5 Customization”.
Part of CoreMedia Blueprint: CKEditor 5 in contrast to CKEditor 4 is fully exposed in CoreMedia Blueprint. This provides much richer configuration options and easier adaptations to your needs.
Minor drawback though: CKEditor 5 is not yet supported for non-Blueprint-usage.
No “Open Images in Library”: The former CKEditor 4 toolbar button for opening the library filtering content items according to
ConfigureDefaultRichTextImageDocumentTypewas not re-introduced. This feature was rather limited compared to the various media you may embed. Instead, apply corresponding filters in the library directly.For details on embedded media configuration see Section 10.1.3.4, “Embedded Media in CKEditor 5”.
Along with that, some more subtle changes were applied by adapting some plugins provided for CKEditor 5:
Integrated split and merge cell for tables.
Support for table header cells.
Linked embedded images now have a badge, so that you can distinguish them from other images.
Not to mention the various enhancements to editing experience provided by the CKSource team, like, for example, in-place editing of links featuring the new concept of so-called contextual balloons.
