[MGNLUI-8592] [DOC] Create migration process for the users with possible script blueprints Created: 13/Dec/23  Updated: 01/Feb/24  Resolved: 01/Feb/24

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

Type: Task Priority: Neutral
Reporter: Dominik Maslanka Assignee: Adrian Brooks
Resolution: Done Votes: 0
Labels: dx-core-6.3
Σ Remaining Estimate: Not Specified Remaining Estimate: Not Specified
Σ Time Spent: Not Specified Time Spent: Not Specified
Σ Original Estimate: Not Specified Original Estimate: Not Specified

Attachments: PNG File screenshot-1.png    
Issue Links:
Relates
relates to MGNLUI-8587 [DOC] Create simple process for the i... In Progress
Sub-Tasks:
Key
Summary
Type
Status
Assignee
MGNLUI-8593 Implementation Sub-task To Do  
MGNLUI-8594 Review Sub-task To Do  
MGNLUI-8595 Pre-Integration QA Sub-task To Do  
MGNLUI-8596 QA Sub-task To Do  
Template:
Acceptance criteria:
Empty
Task DoR:
Empty
Date of First Response:
Epic Link: CKEditor 5
Team: Nucleus
Work Started:

 Description   

User Story: As developer I want to migrate the rich text data as seamlessly as possible so that when I will upgrade from CKE4 to 5 I will consider is as a nice experience without any fear of loosing data.

 

As described in attached docu CKE5 is different tool than CKE4 - which means configuration differs. We need to investiage if configuration and content migration is possible so that customer have seamless upgrade.

 

 

More info here: https://ckeditor.com/docs/ckeditor5/latest/updating/ckeditor4/migration-from-ckeditor-4.html

 


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