[MGNLUI-6106] DOC: Guide to migrating apps to new UI framework (first draft) Created: 03/Aug/20  Updated: 29/Sep/20  Resolved: 29/Sep/20

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

Type: Task Priority: Neutral
Reporter: Ashraf Khamis Assignee: Ashraf Khamis
Resolution: Done Votes: 0
Labels: migration, new-UI-framework, new-content-app
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Relates
relates to MGNLUI-6250 DOC: Guide to migrating apps to new U... Closed
documentation
Template:
Acceptance criteria:
Empty
Task DoR:
Empty
Date of First Response:
Epic Link: Migrate apps to new UI framework
Sprint: UI FW 9, UI FW 10, UI FW 11
Story Points: 5

 Description   

A first draft by Sang can be found at https://wiki.magnolia-cms.com/pages/viewpage.action?spaceKey=~sang.ngo&title=Migrate+an+app+to+new+framework. Sang, Roman and Simon are collecting feedback from the Services and Support teams before the draft is finalized and handed over to DOCS.

For Sang's workshop on migrating apps, see the Zoom recording and presentation slides at https://drive.google.com/drive/folders/1GU_Kf5vWvrj2ZPeNEQUSBIoi7ghIJwz2.



 Comments   
Comment by Christopher Zimmermann [ 26/Aug/20 ]

It could be handy to split the guide into 2 parts.
1. A configuration part,  which would be understandable by any developer including frontend developer. And which would be enough for converting basic content apps, and the decoration part of content-type derived apps.

2. A code part which would be then be relevant only for Java developers.

Comment by Ashraf Khamis [ 29/Sep/20 ]

Created an unpublished first draft at https://documentation.magnolia-cms.com/display/DOCS62/Migrating+an+app+to+Magnolia+6+UI. Reviewed by Roman.

Filed a follow-up ticket (MGNLUI-6250) for next sprint to flesh out the draft with Sang's presentation and to consider restructuring and/or splitting the guide as suggested above.

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