Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
Bedrock Mission!

Learn more

View all

Sign in to view all badges

SOLVED

Project Structure

Avatar

Level 2

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?

1 Accepted Solution

Avatar

Correct answer by
Level 4

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/

http://help-forums.adobe.com/content/adobeforums/en/experience-manager-forum/adobe-experience-manage...

Thanks,

Vamsi

View solution in original post

0 Replies

Avatar

Level 4

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

Avatar

Level 2

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. 

Avatar

Correct answer by
Level 4

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/

http://help-forums.adobe.com/content/adobeforums/en/experience-manager-forum/adobe-experience-manage...

Thanks,

Vamsi

Avatar

Level 2

Thanks Vamsi. You are probably right. I would want to avoid any pitfalls and will stick to adobe recommendations.