Solved
Delivering content in accordion format; what's better CONTENT FRAGMENT or EXPERIENCE FRAGMENT?
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.
- 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?
- 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?
- 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?