Again this is a fantastic article for the AEM community!!
I have ever heard about Core component and proxy technique and found that proxy component technique is very useful to deal with legacy components and component versioning. Instead of changing legacy component source code directly, we could clone it to a new version and make a proxy to new one.
I have applied this technique to my current project recently. The result proved that we could rollback to old version as quickly and easily as possible if any issue with new version happened. It actually makes deployment process less painful, more confident and reduce the cost of testing and development.
Thanks for your article
Great post and very informative.
As I have one question and please help me to understand the same –
Suppose based on the requirement if it is required to create a new component [similar to /apps/weretail/components/content/button (Link Button) and it doesn't have sling:resourceSuperType] and I want to incorporate ‘component policy’ feature with my new component , then what would be value of
sling:resourceSuperType property or I would say the what would be the approach.
Please correct me also.