fragment-usage
When to use
- Reusable content — any content that appears on multiple pages (legal disclaimers, product specs, team bios).
- Structured data — content fragments with defined models (articles, products, events).
- Content variations — show different versions of the same content using fragment variations.
- Headless integration — bridge between headless content fragments and page-based rendering.
Key decisions
- Fragment path: Reference the content fragment by its DAM path. Fragment must exist before referencing.
- Variation: Use master for default. Create named variations for different contexts (mobile, regional, seasonal).
- Field selection: Show all fields for complete rendering, or select specific fields for targeted display.
- Display mode: fragment-display-default for full rendering, fragment-display-card for compact, fragment-display-inline for inline content.
fragment-options
All authoring options
Reference
fragmentPath: DAM path to content fragment (aem-content)
fragmentVariation: variation to display (master, mobile, web, etc.)
Display
classes_fragmentDisplay: fragment-display-default | fragment-display-card | fragment-display-inline
classes_fragmentFields: multiselect of fields to show
Appearance
classes_fragmentStyle: fragment-style-default | fragment-style-bordered | fragment-style-minimal
Analytics
trackInview: boolean
trackInview_meta: text