You are here:
Content Asset Data Binding in Page Designer Overview
Content asset data binding allows Page Designer components to dynamically pull content from content assets instead of using static, manually entered values. This topic applies to B2C Commerce.
How Data Binding Works
When you bind a component attribute to a content asset attribute, the component displays the content asset's data at runtime. Instead of entering text or HTML directly into a component, you select a content asset and specify which attribute to use (such as body, title, or a custom attribute).
For example, create a "Free Shipping" banner as a content asset, then bind that content asset to banner components on your home page, product pages, and checkout page. When you update the content asset, the change appears everywhere you use the content asset.
Benefits of Data Binding
- Content reusability: The same content asset can be used in multiple components and pages without duplicating content.
- Centralized updates: When you update a content asset, the changes automatically appear on every page that uses it.
- Reduced maintenance: You don't manually update the same content in multiple places.
- Separation of content and presentation: Content authors can manage content in content assets while merchandisers focus on page layout and design.
Binding to a Component
Content assets can be bound to any component you select from the Components menu. After you select a content asset, bind its attributes (such as body) to the component's attributes.
Which Content Asset Attributes Can You Bind?
Only attributes in the Content section of the content asset are available for binding. Bind a content asset attribute to a component attribute if:
- Both attributes have a compatible type. Text-based component attributes (such as rich text, text, and string) can bind to text-based content asset attributes (such as html, text, and string).
- The content asset attribute contains content. Empty attributes can't be bound.
To add custom bindable attributes, go to , create an attribute definition, and add it to the Content attribute grouping.
Other Considerations
- You can bind a content asset even if it's offline, but Page Designer displays a warning that the content won't appear in the storefront unless the content asset is online.
- Visibility rules (scheduling and customer groups) apply to the component, not the content asset. To control when content appears, configure visibility on the component.
- Content asset localization is managed separately from page localization. To provide localized content, create locale-specific versions of your content assets. The component itself also has to be localized.
