Aem pages are cached on dispatcher so getting the dynamic behaviour with each request of same page with different viewport won’t help you as page will be cached on the first request so it will render same content irrespective of media type on subsequent call. What issue has been raised by SEO team? ...

I do have lots of .mov file in aem dam and it’s remain in .mov format only. Do you have problem in aem damasset or assetshare commons?

currently, aem uses lazy loading for assets in assets ui. i am wondering if you are looking for any assets in aem dam then i believe without visualizing it you won't be able to find on which page you will find your assets. so for your use case lazy loading and pagination makes no difference for user...

i am wondering why you have this requirement  to pull user information on publisher? Are you doing any user authentication on your site for the user from your aem useradmin?

Above sling model class will only render json data when you call it as  com.test.web.core.models.SecondaryNavigationModel.model.json However you won't be able to parse it in json and i believe in your code you try to pass the json object on HTML DOM element to be used on frontend. If that's the case...

I know that metadata is read only on Brand Portal. I need the opinion from the community advisor if they have suctioned any thing similar in the past.   As in our use case Agency will be uploading the assets on BP and not in AEM so what are the ways we can get the metadata information from them back...

Hi, I do have a requirement where users in brand portal can upload the asset in brand portal contribution folder but i don't see the option to update the metadata field on brand Portal. in our requirement i don't want to give brand portal user access to AEM assets(licensing constraint) so what shoul...

if you are doing that way then you need to have a separate Configuration of Dispatcher farm for invalidating the content. see Configure Dispatcher to Handle Multiple Domains section on https://experienceleague.adobe.com/docs/experience-manager-dispatcher/using/configuring/dispatcher-domains.html?lan...

separate docroot is not required for dispatcher configuration for multiple site. you can work with same docroot folder for all sites configuration per environment

Tt seems the configs are right. the problem is you are creating 2 different farms prod and stage with similar configuration on vhost and is always going to last farm. Normally you shouldn't use separate farms for stage and prod and it should behaves same for all environment. Different farm is only r...