you do not need a mobile domain. For your domain, identify device type using user-agent and Pass Through URI with the correct selector RewriteCond %{HTTP_USER_AGENT} "!(android|blackberry|googlebot-mobile|iemobile|ipad|iphone|ipod|opera mobile|palmos|webos)" [NC]

You need to implement selector-based implementation, one selector for each device type. Desktop: /content/path/of/your/page.desktop.html Mobile: /content/path/of/your/page.mobile.html Now the components you want to have a different response for different devices, implement a selector file for them. ...

  <sly data-sly-use.industryModel="com.aem.sling.model.IndustryModel"> <h2>Haritha test :${industryModel.linkPath}</h2> <ul data-sly-list="${industryModel.childTitle}"> <li>${item}</li> </ul> </sly> Your syntax is worng, try above    

@anasustic Use ACS Commons Report Builder [1] capability, it provides Page Report, which allows you to select root page and template, and list down all pages created with the selected template used root path.   [1] https://adobe-consulting-services.github.io/acs-aem-commons/features/report-builder/...

If you are rendering components by code (in loop & data-sly-resource), you wont be able to allow editors to reorder them. I suggest you use the core component's [1] component selector capability in dialog [2], which will allow reordering items in the dialog itself.   [1] https://www.aemcomponents.de...

The script clientlibs are loaded by your code. So you should update your code to change the script rendering sequence.   Do you see any challenge in it?

SP are heavy bundles, and needs to perform many dependency resolutions, and update and restart many services. I do not recommend installing SPs via the package manager, rather put SP in the install folder of your repository and restart the AEM instance. See the below articles for details.   [1] http...

Technically it's possible by using different policies [1] for CTAs, one global policy for CTA, and another for CTA below Teaser.  In your policy, configure the styles you need.   [1] https://experienceleague.adobe.com/docs/experience-manager-64/forms/administrator-help/work-with-document-security/cr...

A combination of "Sling resource resolver config" and "mod_rewrite" always worked for me, be it single site hosting, or multiple sites hosted on the same AEM instance. I have also used Sling resource resolver to short DAM path, along with content paths.

Also, see this discussion [3]   [3] https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/foundation-component-vs-core-component-in-aem6-5/td-p/364019