[MGNLUI-8653] DOC: Restructure and extend the rich text field documentation Created: 12/Jan/24  Updated: 23/Jan/24  Resolved: 23/Jan/24

Status: Closed
Project: Magnolia UI
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Neutral
Reporter: Adrian Brooks Assignee: Adrian Brooks
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Work Started:

 Description   

CKEditor 4 is Magnolia’s rich text editor in 6.2. Before CKEditor 5 is introduced in 6.3, we need to rework the CKE4/rich text field docu.

For someone working in services addressing customer issues, the current structure is a bit confusing and missing important information.

  • Further resources at the end of the light rich text editor: bring in some common examples and link also to these resources in the rich text editor docu
  • Address in particular:
    • How to edit the tools bars, for example, magnolia plugin
    • Adding a checkbox or a newly created field to a plugin (enhancing it)
  • CSS styling - Drop-downs added to CKEditor to style text
    • Clarify with a dev check: two drop-downs next to each other and would like them to be conditional - is it possible?
    • CKEDITOR Styles Drop-down: Introducing your own styling CKEDITOR.stylesSet.add(“Block styles”, […
    • CKEDITOR config options …. “Not really enough what’s in the documentation” (better organise our content so that developers can quickly link to the right CKEDITOR docu sections)

Generated at Mon Feb 12 09:57:08 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.