tips when developing for AEMaaCS (sites) when you're coming from on-premise

@jayv25585659 

• Though you can do your local development as usual , there could be some features which will be available only on cloud. e.g WebP Optimization.
• Also , custom logs are not available on Cloud. 
• CRXDE access will be restricted on Cloud. Even if you can access , we should not make any changes directly . All the code changes should be pushed via CM pipeline. 
• Leverage the Enviornment Specific Configurations where ever possible https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/implementing/deploying/configuring-osgi#how-to-choose-the-appropriate-osgi-configuration-value-type
• Core Components are part of the Libs. No separate installation required
• While developing components for cloud , try to reuse the core components as much as possible or overlay them using the concepts of Sling Resource Merger.

One change is as below though it is not significant change 🙂

Aem 6.5 explicitly mention create component/ template however same can be achieved in two step create node and then select node type cq:Component and add all other related property after node is created and saved

AEM as a cloud (only have create Node option)