-
Type:
Epic
-
Status: In Analysis
-
Priority:
Minor
-
Resolution: Unresolved
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: CKEditor
-
Epic/Theme:
-
Main Core Job:Orchestrate - Centralize Content
-
Epic Status:To Do
Currently, CKeditor toolbars can be defined programmatically via EditorConfigContributors. Additionally, there is the concept of toolbar set which allows to define several toolbars as part of the editor configuration, then specify which one to use. All these mechanisms require programming and deploying code in the server.
However, we lack the ability to let users personalize these toolbars for different CKEditors in a way that avoids code to be deployed, and to remember their preferences.
In this epic we define a configuration-based mechanism to specify CKEditor toolbars, .
Acceptance criteria:
- A system/instance setting allows to add new toolbars. Each toolbar is defined as a JSON object which will be input as a string
- CKEditor provides a button to select the toolbar so that users can make their choice
- User choice is remembered for each separate editor
- Default toolbars are available (i.e. the ones we have)
- Is blocked by
-
LPS-130101 Allow users to customize and manage views in Frontend Data Set
-
- Ready for Development
-
- is duplicated by
-
COMMERCE-4164 Design improvements to the dataset display
-
- Closed
-
- is related to
-
LPS-84073 POC for an Editor Configuration Portlet
-
- Closed
-