Is there any reference on how to create experience fragment template that supports remote SPA. Any pointers would be helpful.

Hi, we want to implement header and footer for AEM Headless with remote SPA(Next Js). Will that be possible by using experience fragments? Will I get SPA editor for editing the experience fragments components? Please suggest some pointers? Thanks in Advance.

Hi @Peter_Puzanovs , The above solution is not working because the request is going to /cf and not /cf# and # is part of page and is executed at client-side. If I replace /cf with /editor.html then the request is redirected from localhost:4502/cf#/content/we-retail/en.html to localhost:4502/editor.h...

hi @Peter_Puzanovs , We already did [1]. Now we are looking for sling:redirect solution. I tried to implement in my local but not working. Below is the screenshot  

Hi All,   Recently we migrated from ClassicUI to TouchUI and we dont want our authors to edit the content in ClassicUI. So either we need to redirect them to TouchUI editor.html or block/restrict access to cf#. We are doing this because we did not delete the classic dialogs. We kept them and may be ...

Hi @B_Sravan , We cant use the @Default(values="defaultValue") in our sling model because if we dont enter any value while authoring in dialog the default value will be picked from sling model and will be rendered in page. But ideally if we dont enter anything in dialog it should not be rendered on ...

Hi All,Facing an issue for defaultvalue in textfield inside multfield for touch dialog. While authoring, I have removed the default value from dialog and saved it. In content the value is not present which is correct. Again when I reopen the dialog the defaultvalue in dialog is coming .Ideally it sh...

Hi @srinivas_chann1 , We are also facing similar issue. Do you have any solution.Thanks

Hi @deana66659071 ,Can you please elaborate on how you did this solution. If possible can you please provide source code if there is no issue. Thanks,Manikanta

Hi All,We are planning to migrate our AEM Project from Classic UI dialogs to touch UI dialogs. Our classic UI dialog contains multifield of custom xtypes saving data in the form of string array of Json Objects. As the touch UI dialog is based on coral UI 3, we are planning to migrate the content fro...