A client has an existing AEM site using components that proxy AEM WCM core components. The site uses simple page authoring without referenced content. declined wants to create a new experience on another marketing channel. The plan is to use as much of the existing page content as possible to avoid refactoring the current content and to maintain consistency across channels.
which AEM capability should an architect use to meet these requirements?
Which one would be the better option content fragment or experiment fragment to use?
Solved! Go to Solution.
Views
Replies
Total Likes
Hi @Ravindra_Sonawane ,
In the scenario you've described, where the client wants to reuse existing AEM content for a new marketing channel while maintaining consistency, leveraging AEM's capabilities like Content Fragments or Experience Fragments can be beneficial. However, the choice between Content Fragments and Experience Fragments depends on the specific use case and the nature of the content.
For Granular Content Reuse: If the requirement mainly involves reusing smaller, modular content elements (e.g., text snippets, images), Content Fragments might be more suitable. They allow for structured content modeling and offer flexibility in reusing specific elements across different channels.
For Larger Content Units: If the requirement involves reusing entire sections or layouts of the existing AEM pages, Experience Fragments could be a better fit. They encapsulate entire experiences or sections, allowing for consistent presentation across different marketing channels
Evaluate if the new marketing channel requires channel-specific adaptations or personalization. Experience Fragments might offer better previews and handling of entire sections for this purpose.
The decision between Content Fragments and Experience Fragments should align with the nature of the existing content, the level of granularity required for reuse, and the content's structure and layout needed for the new marketing channel. Often, a combination of both Content and Experience Fragments is used to efficiently manage content across different levels of granularity.
Hi @Ravindra_Sonawane ,
In the scenario you've described, where the client wants to reuse existing AEM content for a new marketing channel while maintaining consistency, leveraging AEM's capabilities like Content Fragments or Experience Fragments can be beneficial. However, the choice between Content Fragments and Experience Fragments depends on the specific use case and the nature of the content.
For Granular Content Reuse: If the requirement mainly involves reusing smaller, modular content elements (e.g., text snippets, images), Content Fragments might be more suitable. They allow for structured content modeling and offer flexibility in reusing specific elements across different channels.
For Larger Content Units: If the requirement involves reusing entire sections or layouts of the existing AEM pages, Experience Fragments could be a better fit. They encapsulate entire experiences or sections, allowing for consistent presentation across different marketing channels
Evaluate if the new marketing channel requires channel-specific adaptations or personalization. Experience Fragments might offer better previews and handling of entire sections for this purpose.
The decision between Content Fragments and Experience Fragments should align with the nature of the existing content, the level of granularity required for reuse, and the content's structure and layout needed for the new marketing channel. Often, a combination of both Content and Experience Fragments is used to efficiently manage content across different levels of granularity.
Criteria | Content Fragment | Experience Fragment |
---|---|---|
Nature | Standalone content with no layout information. | Combines content and layout for a cohesive design. |
Content Authoring | Content is authored independently. | Content and layout are authored separately. |
Reuse of Content | Highly reusable; content can various channels. | Reusable, but may carry layout information. |
Consistency Across Channels | Well-suited for consistent content presentation. The channel has absolute control on presentation | Effective for consistent content and layout design. |
Headless Implementation | Highly suited, as it separates content from layout. | Less suited, as it may carry unnecessary layout info. |
Granularity | Content-centric, suitable for modular content reuse. | Both content and layout, suitable for larger-content reuse. |
Integration with Core Components | AEM core components need to be extended to read info from Content Fragments. Unless you use the Content Fragment component itself | Can leverage existing AEM components, including Core Components. |
Addition to what @aanchal-sikka and @Madhur-Madan mentioned,
You can explore the Building Blocks with Experience Fragments if thats fit your requirements
Views
Likes
Replies