@SDusane 1. An AEM website is a completely dependent entity (outcome) of the AEM ecosystem. To make it work it needs to be connected with the AEM setup (for authoring, content delivery etc). However, if you want to migrate the whole setup on Azure servers its surely doable2. Like other AEM features,...
Hello @Edardna,You can refer to this existing thread: https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/seo-friendly-page-name-validation/m-p/617051#M154777Thanks
Hello @SHIBANI06 If the url pattern is same then you can do something similar to this: - create a servlet that will take the current page path as param and generate other alternate regional paths - create a custom component that will only be visible on author in view as published (wcmmode=disabled...
Hello @Shreyas_tm , Thanks for the detail. I would suggest to create custom component, which will allow the author to put the thumbnail and the path of video file. The component needs to render the following markup: <video width="320" height="240" poster="/images/w3schools_green.jpg" controls>
<...
Hello @Shreyas_tm, I assume you have the video file that you want to show on the web page, in such case I think you can proceed with dynamic media player.https://experienceleague.adobe.com/docs/experience-manager-learn/assets/dynamic-media/video/dynamic-media-video-player-feature-video-use.html?lang...
Hello @eobaseki, Can you access the asset directly with url through browser? I hope you followed the steps for connecting RemoteDam: https://experienceleague.adobe.com/docs/experience-manager-cloud-service/content/assets/admin/use-assets-across-connected-assets-instances.html?lang=en#configure-a-con...
Hello @Aaron_Dempwolff, I think you placed the filters in the wrong place, it should be under build configuration in the pom.xml under your ui.apps.structure module as follow: <build>
<plugins>
<plugin>
<groupId>org.apache.jackrabbit</groupId>
<ar...
Hello @Aaron_Dempwolff, To add with @aanchal-sikka, make sure you have all your filter(s) inside a parent tag filters: <filters>
<filter><root>/apps/{project-name}</root></filter>
<filter><root>....</root></filter>
<filter><root>....</root></filter>
</filters> Thanks
Hello @TrifaCh, Though I am not sure about the business that you want to achieve, but its seems you want to maintain consistency of the configurable properties within the component dialog. If that is the case, I think you can achieve it with design dialog For your reference: https://experienceleague...