Editable Templates in AEM
With AEM 6.0 onwards, after presentation of Touch UI for Granite related overlay we are utilizing Sling Resource Merger:- Presently on the off chance that we need to overlay a segment or use sling asset merger for a segment then we need not required to duplicate glue whole part structure with hub properties from libs to applications. We just need to reproduce the skeleton structure. To rearrange the diversion of the structure all delegate hubs can be of type nt:unstructured (they don't need to mirror the first hub type; for instance, in/libs). Note:- Sling Resource Merger and its related techniques must be utilized with granite(touch ui) parts. The benefits of utilizing the Sling Resource Merger in AEM is to: guarantee that customization changes are not made in/libs. diminish the structure that is duplicated from/libs. Abrogate a part in AEM:- Abrogating a part is essentially expanding or acquiring the segment utilizing sling:resourceSuperType property. You can abrogate a part from/libs by making a custom segment under applications physically and including every essential hub and setting estimation of sling:superResourceType property to that segment will acquire all the element from/libs/segment, even after overhaul regardless you acquire the highlights of picture segment. Here we can utilize the sling:superResourceType for any part that you need to acquire usefulness (model from projectA segment to ProjectB and so on., not just confined to libs). When to utilize overlay/sling asset merger and when to utilize supersede absolutely relies on your prerequisite.
0 Comments
Leave a Reply. |