Migrate static template pages to editable template pages

[SathyaprakashAs]

Hi Team,

We are planning to migrate around 3K+ pages from static to editable pages. Can anyone provide insights regarding the modernizer tools?(i.e. prerequisite to use modernizer tool)

Please note that we have created an editable template and wanna migrate the pages now.

[ayushmishra07]

Hi @SathyaprakashAs , 

Please refer to the following link for getting complete details related to planning, configuration, and development of the Modernizer tool. : https://opensource.adobe.com/aem-modernize-tools/ 
For Installation and Implementation you can refer to the following git library : https://github.com/adobe/aem-modernize-tools 

Edit : Here's a link to the video demonstration of how to use the Modernizer tool for conversion - https://bluejeans.com/playback/s/sCLWuQu7elqbrYlJUI3UAMPrx2NaJeWesQvNtMj3HR8a4g4rnKw3hVi0lYd6zF6U 

Hope it helps !!
Thanks,
Ayush

[aanchal-sikka · Accepted solution]

Hello @SathyaprakashAs 

1. Existing Static Pages: Have a clear understanding of the static pages that need to be migrated. Identify the pages, their structure, and any associated assets or components.

2. Component Development: If required, develop the necessary components and templates that will be used in the editable pages. Example: iparsys might not provide you the expected results

3. Mapping and Analysis: Analyze the static pages to determine the mapping between the existing content and the new editable templates. This includes identifying which components, assets, and content need to be migrated to new structure.

5. Content Model: Define the content model for the editable templates. This includes determining the structure, fields, and components that will be used.

6. Moving the Site specific configs from Design mode to Context-aware configs

7. If Site-specific clientlibs are used, these would need to be configured on Site level in Content pages. Editable templates if shared across sites cannot be used for the same purpose.

8. Use responsive grids instead of parsys to get the benefits of Dynamic structure and responsiveness

9. Client-libs would need some adjustments, as page structure and thus HTML would change

[Sudheer_Sundalam]

@SathyaprakashAs 

Adding onto the points outlined by @aanchal-sikka 

10) Most static templates use iParsys for Header/Footer, Creating the header/footer as experience fragments and defining them as part of the editable template structure is the common practice in Editable Templates.

11) Reevaluate embedded components on the static templates.