Key takeaways
- Content fragments and experience fragments solve different reuse problems. A content fragment is structured content — organized as named fields based on a model (like "description," "itinerary," or "what to bring") — that can be delivered to any channel via GraphQL, including single-page apps, mobile apps, and IoT devices. An experience fragment is a fragment of a web page that includes components, layout, and styling; it can be reused across pages via a component, delivered externally as HTML or JSON, or used as an integration point with Adobe Target for personalization.
- A building block is a reusable set of components inside an experience fragment. Once created, a building block can be shared across multiple variations of the same experience fragment, or even across different experience fragments entirely. When the master building block is updated, every place it is used updates automatically — making it a powerful tool for managing shared content across a complex site.
- Experience fragment variations let you maintain different versions of the same content for different channels. A plain variation is an independent copy that stands on its own and is not affected by future changes to the master. A live copy variation maintains inheritance from the master, so common content stays in sync — but you can break inheritance on individual components to introduce local differences, preserving global consistency while still allowing channel-specific customization.
- A collection links assets to a content fragment without moving them. Rather than reorganizing your assets folder, a collection creates a static list of associated assets that becomes available in a dedicated asset picker when that content fragment is placed on a page. This makes it easy for authors to find and use the right images without having to search the full asset library.
- Displaying a "single text element" from a content fragment unlocks powerful reuse on a page. By selecting a specific named field to display — rather than the full fragment — the same content fragment can independently power multiple parts of a page (for example, populating each tab in a tabs component with a different field from the same fragment). This same structure is what makes the content available to external applications through GraphQL, so one piece of authored content can serve a web page, a mobile app, and other channels without duplication.