Hi,  A pure headless approach means that you have a source system(AEM) where data (content, in the case of AEM) is exposed to different "heads" or applications, generally React or Angular applications. By definition, the headless approach means you don't have the ability to provide any WYSIWYG edito...

Hi,  If you access the SPA URL directly through the dispatcher (the full path), is the application loading? If not, check which resources are being blocked by using the Network tab in the browser. Then, review the dispatcher logs to understand what type of redirect is occurring and address it. Once ...

I agree with @arunpatidar , but if this button could come from an RTE where the markup is dynamic, I think the best approach is simply to use vanilla Javascript. 

Hi,   I don't fully understand your use case, but if you need to update the button's OOTB markup, is there any reason why you would not extend and update the markup there? You could achieve this with Javascript easily, as well.      

Hi   This is an external bundle, so you need to wrap it into your bundle to deploy it along with your code. Please check this thread:  https://blogs.perficient.com/2018/10/09/resource-streams-in-apache-sling/    Hope this helps

Hi, Double check the changes are reflected in the "../enabled_vhosts/.vhost" file, and make sure you are not seeing cached content, try it on an incognito window. 

Thanks @user12648, I didn't understand the question.   @jezwn, if you are simply looking for a way to display a banner on a public AEM site, the easiest approach is to add a custom banner component (likely within an XF) that you can update easily once, and then have the component displayed on all th...

You could explore using I/O Events for that use case and get rid of the WF launchers and custom WF steps, even better, there is exactly that use case described on this page: https://experienceleague.adobe.com/en/docs/experience-manager-learn/cloud-service/aem-eventing/examples/assets-pim-integration...

I think it depends on what your custom process does, based on that, using the methods @Rohan_Garg and @arunpatidar should be the way to go. I could even explore if there is a chance to offload that processing from AEM.   Hope this helps

Hi,    Do you have an empty structure in your codebase under /apps/cq/gui/content as the filter configuration you have is set to allow deployment of whatever is in your codebase?