if you have fix set of user group for known set of properties then you can try it via using node level ACL's permission and implementing like jcr:modifyProperties or similar. check here  https://experienceleague.adobe.com/docs/experience-manager-65/administering/security/user-group-ac-admin.html?lan...

The references should auto update with language copy if you have enabled the sub-pages while language copy and enabling with translation project (may test with default translation config)

try checking https://github.com/shinesolutions/aem-healthcheck/blob/master/bundle/src/main/java/com/shinesolutions/healthcheck/hc/impl/ReplicationQueueHealthCheck.java as the replication queue object received from agentmanager if that helps.

hello,if you refer https://kbwebconsult.com/authentication-handler-in-aem-custom-approach/ and look at method obtainUserId(token) which returns the userid can be used as to cross verify if the token still valid and verify against userid.

you can put comma separated path (make sure, its absolute path) there as it process as string array.

Hello,   AEM servers doesn't allow to disable OPTIONS method call by default and i think there is already reply to access to custom way.   Curious to understand the reason behind making such request?? because you already have dispatcher to secure the traffic. also refer https://stackoverflow.com/que...

Hello,   How did you identify that its because of number of child pages?? the log you shared has only info no error, probably try to grab the error/warning coming during the process in error.log and share.   another work around to clear the doubt is to create a new live copy page hierarchy with less...

your recommendation derive from your filtering criteria, so read through https://experienceleague.adobe.com/docs/target/using/recommendations/introduction-to-recommendations.html?lang=en for better understanding.

refer - https://experienceleague.adobe.com/docs/experience-manager-desktop-app/using/troubleshoot.html?lang=en to troubleshoot.

Hello,   If you created separate projects in different GIT the deployment will override the previous one. to overcome this better create both projects as sub module suggested by others and make it under by creating a parent project.    like project C has sub modules like A & B. hope this works.