Sling Resource merger in aem is one of the most commonly and frequently used feature of sling after aem 6.0. Due to limited functionality of touch ui components, we often are required to overlay/ override a component from /libs to /apps. Earlier (before aem 6.0) in case of overlay we need to copy paste entire component structure with node type and properties and then we make our changes which indirectly increases the overhead on /apps folder.
But as adobe is promoting to use its new touch optimized ui for granite components , it have changed the definition of overlay for Touch ui (Granite) components where you need to create only similar skeleton structure (where nodes can be of type nt:unstructured) and you can add, remove or modify existing node.
Click here to learn more about www.aemcq5tutorials.com/tutorials/sling-resource-merger-in-aem/
