Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
BedrockMission!

Learn More

View all

Sign in to view all badges

Rendering of an Experience Fragment inside a Webpage?

Avatar

Avatar
Validate 1
Level 2
surenk
Level 2

Likes

9 likes

Total Posts

48 posts

Correct Reply

3 solutions
Top badges earned
Validate 1
Ignite 1
Give Back 5
Give Back 3
Give Back
View profile

Avatar
Validate 1
Level 2
surenk
Level 2

Likes

9 likes

Total Posts

48 posts

Correct Reply

3 solutions
Top badges earned
Validate 1
Ignite 1
Give Back 5
Give Back 3
Give Back
View profile
surenk
Level 2

26-08-2019

Fundamentally Experience Fragments are consumable content which can be used "as-is" and "makes senses on its own".

Also detailed here Adobe Experience Manager Help | Understanding Content Fragments and Experience Fragments in AEM 

                            

If an Experience Fragment lives within a site page, can it use it's own template/styles separate from what the main Page will be?

If an Experience Fragment need to have certain specific styles (like font size/color for title and text, image sizes on it) and if this Experience Fragment need to live on a page in AEM Sites, but if that Page is built using a different Template that as separate styles defined.. the Page/Template styles are over-writing the XF styles. We cannot see the specific styles applied to components in an XF but seeing that of the site.

The process we are doing that isn't working:

  1. Build an Editable Template (say Template-1) using styles (say Styles-A)
  2. Build a page (Page-1) using Template-1
  3. Build an Editable Template (Template-2) using styles (Styles-B)
    1. Add allowed Components. And also apply specific styles using the AEM OOTb Styles UI options.
  4. Build an Experience Fragment (XF-1) using Template (Template-2 - internally uses Styles-B)
    1. While authoring the content using the allowed components, the specific styes are not being applied.
  5. On Page-1, drag an "Experience Fragment Component" and use XF-1 as the source
    1. XF shows up with Styles of the main page Styles-A instead of Styles-B

We have issues at 4.1 and 5.1.  How do we solve this?

Accepted Solutions (0)

Answers (0)