EDGE delivery with AEM sites options for onboarding

[edge3436]

Hi EDS experts,

We have been exploring different ways an AEM clients who want to stay with AEM sites can onboard onto EDS.
Our understanding is there are three main paths

1) Converter approach
This would involve
a) writing a converter to convert non-semantic HTML to semantic HTML
b) rewriting the front end code to comply with blocks way of development

2) Instrumentation approach
This would involve
a) writing a converter to convert non-semantic HTML to semantic HTML
b) rewriting the front end code to comply with blocks way of development
c) instrumenting the pages in AEM to be compatible with universal editor

3) Writing from scratch
This would involve
1) Using aem-sites-with-edge-delivery-services-template create pages
2) create equivalent blocks for components compatible with UE using models
3) rewriting the front end code to comply with blocks way of development

Is this understanding correct?

Especially around approach 2 step a, is converter required in this approach.
Our understanding is unless we are creating everything from scratch the proper EDS way converter is required to convert non semantic HTML to semantic HTML.

Kindly let us know your thoughts.

[Shashi_Mulugu · Accepted solution]

@edge3436 only #1 and #3 valid.  #2 is option to support universal editor feature when you need wysiwyg feature and with multiple content source options..

[Shashi_Mulugu]

@edge3436 Did you find the suggestions from users helpful? Please let us know if more information is required. Otherwise, please mark the answer as correct for posterity. If you have found out solution yourself, please share it with the community.