Hello Adobe friends,
I am working on a new project of mine. I am contemplating creating an organization's core components based on WCM Core Components and adding an organization branding and style system. Now several questions in mind I'd like to raise:
Solved! Go to Solution.
Views
Replies
Total Likes
You have to refer it in maven dependency for deploying and use resourceSuperType to extend your core components.
Hi @sephytodd , the best practice is to keep your organization core components library under apps/org-core which you can add it as a maven dependency in your applications.
But then again, is referencing from maven dependency a best practice, or should we extend the org-core components to another AEM project as a supertype/resourcetype?
resourceSuperType should be used. The intention behind this is whenever there is an update to the core components from Adobe, all your proxy components will be updated to the latest standards.
You have to refer it in maven dependency for deploying and use resourceSuperType to extend your core components.
Hi @sephytodd
The folder structure is always a good practice to follow and there ain't any mandatory folder structure to follow.
The best way to follow would be using the archetype-generated folder structure. As you were asking about the location of the core components, that's where we can organize our component folders. I am currently following this structure for one of the projects, where we hold multiple sub-projects under a parent. See if this aligns to your liking.
apps/ my-project/ - clientlibs/
(all client libraries) - components/ sub-project content structure custom - config - i18 - templates - install
Under content, I have all my core components(proxy) + common components that could be used in all sub-projects.
I hope this helps.
Thank you,
Sravan
Views
Likes
Replies
Views
Likes
Replies