Cloud 5 - Fragments

Transcript

Content fragments and experience fragments may seem similar on the surface, but each play very different roles in the AEM content management system. At their core, content fragments are designed to handle information and be able to structure that information using a data model. Experience fragments define the presentation, which creates an experience using any available AEM component. In this episode, Darren is going to play the role of an experience fragment, and I will be a content fragment. We’re going to have a little fun banter so that you can understand the differences between the two. As an experience fragment, I can fully lay out content and act like a mini web page. Look at this. I don’t think a content fragment could even look this good. Look at this. You know what, Darren? That does look pretty good, but that’s not what I’m all about. I’m all about structuring data by building an effective information architecture. I structure the data and I define a data model. Information architects love me. Take a look at this really cool model editor, which helps me define an effective data schema. Pretty neat. That’s pretty cool, but you’re not that cool. I can actually use content fragments inside of experience fragments. I can have both your data side and the presentation side. You know what? That’s true, but I’m data-centric. I’m not presentation-centric like you, experience fragment. I’ll allow you to use all of my data in your little experience fragments, but you know what? You still have to control the look and the feel of my data. The more I think about it, that’s not even a job I want. Before you get too cocky, don’t forget that it’s not just you. Any channel can control my look and feel. It doesn’t have to be an experience fragment. It could be an iOS app. It could be an Android app. It could be the entire internet of things. Anyone can control the look and feel of me for any purpose. Experience fragments are just superficial. They just deal with the look and the feel while I deal with the really important things like data. Oh yes, but how sweet my look and feel is with the beautiful responsive layout and feel. Things you can only dream of, my friend. Only dream of? You know, how are your AI capabilities? Can you do intelligent text summarization of multi-line elements like I can? Hm, I didn’t think so. I can do translation and localization. I mean, can you do that stuff? Sure, I can do translation and localization as well. And you know what? None of that stupid markup gets in the way. It’s just pure data. Do you allow authors to do annotations like me? I mean, it really helps build the team collaboration. Yes it does. And as a matter of fact, I do. My multi-line text component fully supports annotation and collaboration among team members. Well, how’s your personalization skills? I mean, I could export HTML to Adobe Target for personalized offers. I can even export it as JSON to Adobe Target for even more flexibility. You know what? I can use any third-party solution via AEM content services, which allows me to export JSON. I can even export via the AEM Assets API, which again provides even more flexibility with any third-party solution. You know, I guess you can be useful in defining the look and the feel and also creating personalized solutions using Adobe Target, but data is my focus. As this conversation shows, both content fragments and experience fragments have useful places in any content management system. Content fragments allow for data flexibility, while experience fragments allow you to build beautifully authored presentations. I can still do that though.