Expand my Community achievements bar.

Dive into Adobe Summit 2024! Explore curated list of AEM sessions & labs, register, connect with experts, ask questions, engage, and share insights. Don't miss the excitement.
SOLVED

Delivering content in accordion format; what's better CONTENT FRAGMENT or EXPERIENCE FRAGMENT?

Avatar

Level 2

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.

 

  1. I've looked at CONTENT FRAGMENTS, however since they're just text based it seems that they don't quite fit the bill since I won't have the control over the layout as I did building the entire accordion on the page via the visualizer. Is there a full Rich Text editor available in CONTENT FRAGMENT where I can add HTML?  It may just be turned off for me, which I can request access from my dev team?
  2. Can EXPERIENCE FRAGMENTS be used to fill a accordion tab(s)? Do they allow the same level of design component control as I would on a regular page? Should all of the regular visuazling components be available in experience fragments also and they're just not turned on from a permission perspective for me?
  3. From a functional standpoint building it as a fragment will help in finding and editing individual accordion tabs instead of sifting through hundreds of components on the page.

 

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?

1 Accepted Solution

Avatar

Correct answer by
Level 8

@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. 

https://experienceleague.adobe.com/docs/experience-manager-core-components/using/wcm-components/acco...

 

View solution in original post

2 Replies

Avatar

Correct answer by
Level 8

@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. 

https://experienceleague.adobe.com/docs/experience-manager-core-components/using/wcm-components/acco...

 

Avatar

Level 2

As for the accordion component, I think you can configure what components that you want inside an accordion via the allowed components configuration. 

https://experienceleague.adobe.com/docs/experience-manager-core-components/using/wcm-components/acco...

 


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