@ShaylaBl alttext, captions, description can be either managed in AEM sites component or managed at central place such as Asset metadata.   Few things to consider:  If managed at sites page components: Flexibility to manage along with page contentCan be different for different pages based on context...

@Aaron_Dempwolff why do you want to create pages for each product? Will it be possible to explore how OOTB CIF component architecture follows? Create single, generic page in AEM and use same page with a selector to identify productid, serve content based on your product information.   <domain>/us/en...

@SaumyaJa it depends on how are trying to use those react components, are you trying to build a SPA website? then mapping AEM components resourcetype to React SPA component. But its not mandatory, you can also just load those clientlibs on the page and hyderate React tags for each components on the ...

@punithshetty123 no

@Chaithra1998 you cab even remove read permission for that path to concerned user..    As informed by @arunpatidar @EstebanBustamante search results will be picked by respective content type index and apply acl on top of it.. so if the user doesn't have read access to those paths, they won't be disp...

@ChristianJu as AEM is built on top JCR repository, move operation is nothing but deleting a node from one folder and creating in new folder. So it needs delete permission to allow move operations to work..   One thing we can do is to write some custom JS on top of aem UI to hide delete button on pa...

@gallaghan6 when you say cloud vanilla instance? Is it a aem cloud online instance or local aem cloud sdk instance?

@EduardoBo3 have you tried using granite include? https://developer.adobe.com/experience-manager/reference-materials/6-5/granite-ui/api/jcr_root/libs/granite/ui/components/coral/foundation/include/index.html

@anupampat good question.. while i dont have any immediate solution for you.. but curious to know the responses from other community experts///