AEM adds new feature "content fragment model", which can have different content fragment data types. It is very useful feature.
However, after following this link (Adobe Experience Manager Help | Getting Started with AEM Content Services - Part 1 - AEM Content Ser...to define the FAQ, I am not able to create variations, the "Creation Variation" link is not there.
Is it possible to have own content fragment model and also include the variation for different channels?
Just wonder if adobe can provide some guideline or example for how to use content fragment model with different variation?
Thanks.
Solved! Go to Solution.
Views
Replies
Total Likes
Content Fragments created from Content Fragment Models should already be channel agnostic (they are "raw" data).
If you want only data points X and Y exposes on Channel A and some other data points Y and Z (of the same Content Fragment) exposes on Channel B; then you'd select them when you defined how that Content Fragment will be exposed for each respective channel. Content Fragments models naturally make this "easy" as their built out of discrete fields.
Content Fragments created from Content Fragment Templates (the longer-form editorial style) have variants (and elements) because they are effectively one big field.
So where as a CF from a Template may have a long "Web variation" and a more concise "Mobile variation", a Content Fragment from a Model might simple have 2 fields: Long Description and Short description.
HTH!
Here are the docs for this:
Page Authoring with Content Fragments
As you can see, you can add different components to fragments. You can build flexible fragments for your business requirements.
Views
Replies
Total Likes
Thank you for your response.
However, I ask for adding variation in content fragment model? The variation function exists in content fragment, but not content fragment model.
Can you please ask adobe internal developers to see if we are able to use variation for content fragment model?
Thanks.
Views
Replies
Total Likes
Checking that!
Views
Replies
Total Likes
Content Fragments created from Content Fragment Models should already be channel agnostic (they are "raw" data).
If you want only data points X and Y exposes on Channel A and some other data points Y and Z (of the same Content Fragment) exposes on Channel B; then you'd select them when you defined how that Content Fragment will be exposed for each respective channel. Content Fragments models naturally make this "easy" as their built out of discrete fields.
Content Fragments created from Content Fragment Templates (the longer-form editorial style) have variants (and elements) because they are effectively one big field.
So where as a CF from a Template may have a long "Web variation" and a more concise "Mobile variation", a Content Fragment from a Model might simple have 2 fields: Long Description and Short description.
HTH!
Excellent response David!
Views
Replies
Total Likes
Views
Likes
Replies
Views
Like
Replies
Views
Likes
Replies