Problem

https://ckeditor.com/blog/ckeditor-4-end-of-life/

Expected results

Customers can safely use a supported rich text editor.

Actual results

CKEditor 4 reaches its End of Life (EOL) in June 2023. From then onwards, it’ll no longer be updated, have security patches and bug fixes, or new features.

Workaround

https://ckeditor.com/blog/ckeditor-4-end-of-life/#2-extended-support-model

Possible solutions

• Purchase the Extended Support Model (link in the Workaround section)
• Implement (all these will most likely introduce major incompatibilities and need major effort)

• • CKEditor5
    • licensing issue https://jira.magnolia-cms.com/browse/MGNLUI-6885?focusedId=353435&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-353435
    • no Vaadin8 integration addon 
  • Vaadin's OOTB richtextarea
    • https://vaadin.com/docs/v8/framework/components/components-richtextarea
    • limited functionality, might be enough for the SaaS offering
  • others like
    • TinyMCE Vaadin Integration,
      • https://repo.maven.apache.org/maven2/org/webjars/bower/tinymce/
      • https://github.com/tinymce/tinymce/security/advisories/GHSA-gg8r-xjwq-4w92
    • Froala Vaadin Integration 
      • https://github.com/froala/wysiwyg-editor

Result of the spike:

• Pros/Cons for the options listed above
• Simple PoC to integrate these (let's not spent time to integrate all the current CK4 integration features!)
• there is already a sample impl
  • https://design.sre.magnolia-cloud.com/.magnolia/admincentral#app:richTextEditors:detail;/:add
  • https://git.magnolia-cms.com/projects/INTERNAL/repos/design-webapp/commits