Affects Version/s: None
Fix Version/s: None
As a Digital Experience Platform, Liferay DXP contains many content-centric applications and many instances where creating, editing and previewing content is a key part of a specific workflow.
To maximize extensibility, Liferay DXP offers the following editor OOTB:
For many apps, which WYSIWYG editor is used is configured via Configuration Settings or portal.properties.
At the time of writing, OOTB, both CKEditor and AlloyEditor are used in a variety of places. These defaults were decided without a proper User-Centric mindset.
To analyze our current usage of editors and simplify it to provide a better and more cohesive writing experience in DXP
- The module frontend-editor-ckeditor-web offers React components that safely wrap CKEditor for usage in the product
- Simple Inline Inputs (title, subtitle...) don't require a complex wysiwyg editor to be instantiated
- Unnecessary instances of AlloyEditor are replaced by standalone CKEditor
- Necessary usages of AlloyEditor are identified and UX requirements collected so we can Create a CKEditor-based Balloon Editor