@raviranjan : please also check: - The reports tab, if it reports any errors with the references in the map - the output presets tab, whether all the expected output types are showing up?   Please also share the ditamap source - for us to assess what could be wrong.

@suresh_36 : which version of AEM Guides are you currently trying this with? Also, can you confirm if the link component is overlay'd or OOTB?

@ravir73578276 : This has to be custom built. OOTB there is currently no path to get SPA directly.

@MayurSatav : It depends on what elements/attributes of DITA topic do you plan to map to the tab component properties. Basically when you map a element to a AEM component, the DITA element should have enough sub-elements/attributes that are expected by the component code (sightly/jsp) or else you wi...

@sschnelbach @BRG_MA : do you already have a support ticket for this? (I assume both of you are from same team)Please send out a note to the Customer Success Manager on this - we would like to understand this further.

So is the above behavior reproducible on Chrome as well then?In the mean time - I tried the same on edge as well and I didn't face the slowness - however I did not work whole day on the editor.Also, with your last post - is it safe assumption that this behavior is not content specific?

@sschnelbach : which version of AEM Guides are you on?Is it happening for a specific type of content or does web-editor hang for every file you open in editor? Did you also try this on Chrome? Is it reproducible for same content on Chrome?  

@MayurSatav : possibly please share the DITA content package along with the template configuration you created.     

No, currently it is not an available out of the box integration Please raise this request with product management to discuss the use case - to see if there is a possibility of same on roadmap.

Acknowledged.  I have raised a change request and engineering will pick this up soon.