Parsys vs project container in component | Community
Skip to main content
March 1, 2025
Solved

Parsys vs project container in component

  • March 1, 2025
  • 2 replies
  • 494 views
We are  working on developing a custom component in AEMaaCS—let say it is  a "Banner" component. This component needs a placeholder where authors can add other components dynamically. I’m trying to decide between using an iparsys or a custom Container component that we’ve already built for our project. What would be the best approach here?  What does adobe recommend.?Any suggestions .
 

 

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by Avinash_Gupta_

Hi @abhi9031 

 

Container component or the responsive grid provides more flexibility and provides more capabilities to authors to manage the layout of the template and using parsys you are restricting the styles in the custom code which is not in control of authors.

 

Hope this helps you.

 

Thanks,

Avinash

2 replies

Avinash_Gupta_
Community Advisor and Adobe Champion
Avinash_Gupta_Community Advisor and Adobe ChampionAccepted solution
Community Advisor and Adobe Champion
March 2, 2025

Hi @abhi9031 

 

Container component or the responsive grid provides more flexibility and provides more capabilities to authors to manage the layout of the template and using parsys you are restricting the styles in the custom code which is not in control of authors.

 

Hope this helps you.

 

Thanks,

Avinash

aanchal-sikka
Community Advisor
Community Advisor
March 3, 2025

@abhi9031 

 

To keep up with the consistent improvements, I would suggest using a component that extends from WCM Core Responsive Grid.

parsys is not recommended. 

iparsys should be used when you need to inherit components in a tree. It does not have all of the features that a Responsive Grid provides. 

Aanchal Sikka