Hi,
I was planning to use AEM 10 for bootstrapping my AEM project. However I would want to create multiple projects instead of one monlothic project. For example.
project-A-templates : This would have all the templates
project-A-components : This would have all the components.
project-A-designs : This would have all the designs.
project-A-content : This would have all the deployable content
project-A-services : This would have the services. All the different services would have their own project.
Need opinion on this approach please? Are there any problems doing this or Is it recommended to have everything under one project?
Solved! Go to Solution.
Views
Replies
Total Likes
Hi, Sanjeev
I didn't understand your thoughts behind deployments.
Actually, how you are you managing deployments. Are you engaged with Adobe Managed Services, or custom production deployments?
And, you can use package filters to package the things you want and deploy it into production. Also, if you want to deploy whole project you can version your package and bundles and deploy. It's maintainable and easy.
The way you are choosing to create a project structure is not a best practice and you may fall into pitfall while implementation. I would recommend to follow the structure recommended by adobe for respective AEM version.
http://www.aemcq5tutorials.com/tutorials/adobe-aem-and-cq5-best-practices/
Thanks,
Vamsi
Views
Replies
Total Likes
Hi, Sanjeev
Can we know little more info on requirement why you are planning this approach?
Do you have multiple projects to handle inside your organization?
Thanks,
Vamsi
Views
Replies
Total Likes
So when If components change, I will only deploy components. If templates change, I would want to only deploy templates etc.. I would not want to do regression on anything else. Also there is a low risk of anything else sneaking in.
Views
Replies
Total Likes
Hi, Sanjeev
I didn't understand your thoughts behind deployments.
Actually, how you are you managing deployments. Are you engaged with Adobe Managed Services, or custom production deployments?
And, you can use package filters to package the things you want and deploy it into production. Also, if you want to deploy whole project you can version your package and bundles and deploy. It's maintainable and easy.
The way you are choosing to create a project structure is not a best practice and you may fall into pitfall while implementation. I would recommend to follow the structure recommended by adobe for respective AEM version.
http://www.aemcq5tutorials.com/tutorials/adobe-aem-and-cq5-best-practices/
Thanks,
Vamsi
Views
Replies
Total Likes
Thanks Vamsi. You are probably right. I would want to avoid any pitfalls and will stick to adobe recommendations.
Views
Replies
Total Likes
Views
Likes
Replies
Views
Likes
Replies