@nkoppul1 What you mentioned is in fact the cost efficient approach. Only thing that will further influence the approach is whether you have a AMS, On prem or AEMaCS setup. AEMaCS has a traffic based contract pricing and it is different from an On-Prem pricing. For more details, you might want to ch...

@WalterHill_WV Yes, this is definitely possible. Also, you can even use both fully React and fully HTL based components on the same Template.

@SudarshanV1 No need to change the resourcetype TYPE to String[]. Just add this property in the node. propertyName - multiple PropertyType - Boolean PropertyValue - True.   This will allow the tags field to accept multiple tag values.

@carbfrze_crown You can create a event listener that listens to Activation actions on Preview agent. Inside this even listener , you can trigger an explicit content rollout using the RolloutManager API - https://developer.adobe.com/experience-manager/reference-materials/6-5/javadoc/com/day/cq/wcm/ms...

@rajat168 Can you add the user that you are using to log in to your local instance to the administrators group? The script is being executed by the logged in user here. If you are logging in with admin/admin , then just add the Administrator user to the administrators group. Due to some weird reason...

@rajat168 Script execution access is allowed only to specific user groups. Be default it is the administrators group. make sure the current logged in user is part of the administrators group and you should be able to execute the script. If you want to have some other user group that should be allowe...

@shikhasoni1 every time the user logs-in , you can add a custom property in the user's profile node. This property can store current login timestamp. Lets call it last-logon-date . Every time the user logs in, the following should happen and in that order (at the time of user login) :   read the exi...

@mancillaign Here you go - https://experienceleague.adobe.com/en/docs/experience-manager-65/content/sites/administering/integration/adobeanalytics  

@touseefk2181136  You need to add the below after setting the node properties.   replicator.replicate(session, ReplicationActionType.ACTIVATE, "/content/data/stores");   Ofcourse, make sure that you add the Replicator service in your service by using :  @Reference private Replicator replicator; ...

@Manasi29 Check the system console to see if there are bundles that are not active.