Hi! I'm a front end content manager trying to determine the best way to build an accordion. I have one already built using page layout/visualizer components. I would like to fill individual accordion tabs with reusable content on different pages in a future state. In my current accordion construction the content in each tab is more than just text and is a combination of images, video, and in some cases nested accordions, and is generally more complex than just text.
Am I approaching this the right way?
While I work closely enough with my development team to request additional access or permission levels, custom component development isn't in the cards right now. Thoughts? Suggestions?
Solved! Go to Solution.
Views
Replies
Total Likes
@culver-king Based on what you mentioned, Experience Fragments (XFs) should be the way to go as you are looking for not just plain text but styles as well.
A very good comparison of Content Fragments(CFs) and Experience Fragments (XFs) is available here - https://experienceleague.adobe.com/docs/experience-manager-learn/sites/content-fragments/understand-...
As for the accordion component, I think you can configure what components that you want inside an accordion via the allowed components configuration.
Views
Replies
Total Likes
@culver-king Based on what you mentioned, Experience Fragments (XFs) should be the way to go as you are looking for not just plain text but styles as well.
A very good comparison of Content Fragments(CFs) and Experience Fragments (XFs) is available here - https://experienceleague.adobe.com/docs/experience-manager-learn/sites/content-fragments/understand-...
As for the accordion component, I think you can configure what components that you want inside an accordion via the allowed components configuration.
Views
Replies
Total Likes
As for the accordion component, I think you can configure what components that you want inside an accordion via the allowed components configuration.
This is why I was confused when I tried to create an experience fragment, not all components were available to me. I'll work with my dev team to have them allow components in experience fragments. My guess is that it is a user-level permission and not site-wide, right? I'm going to submit a ticket now with my dev team. Thank you @Harwinder-singh
Views
Replies
Total Likes
Views
Likes
Replies