The following tips have been collected through customer feedback, and are helpful to know when building B2C Commerce Page Designer pages using the Visual Editor.
- Maximum number of components that can be included in a Page Designer component
Pages and components contribute to the content quota that also applies for content assets. There’s a maximum nesting depth of 5 levels in pages. Aside from the maximum nesting depth, there are no other limitations. For maintainability, don’t let pages grow too large.
- Drag and drop components
Some regions and layouts only accept specific components, so if a component doesn’t move it’s most likely that the target region doesn’t support this type of component. Your developer can provide more details.
- Publish the same page on multiple sites at once
When you create a page it’s automatically shared with all sites in an unpublished mode, via the Shared Library. The Published or Unpublished Status is separate for each site and requires manual adjustment.
- Using Variation Products in the Product Tiles
A Variation Product can be displayed in a Product Tile. The fundamentals for Main, Variant, and Product Groups in Site Genesis and Salesforce Reference Architecture (SFRA), are the same within Page Designer.
- Hide a component for a specific locale
Customer Groups allow you to promote components to specific users. To determine what Customer Groups are able to see the component, use Targeting on a page or component. Build Customer Groups to include or exclude specific regions. And use the same customer groups rulings across other features, such as promotions that support customer group bindings.
- Page Designer and Einstein Product Recommendations
SFRA contains Page Designer components that offer Einstein recommendations, including a picker for the desired recommender.
Note Be sure to assign the correct Business Manager cartridge in the Business Manager Cartridge List for this specific functionality. - Using content assets in components
Components support content asset binding. Instead of entering content directly, bind component attributes to content asset attributes. Use this approach to reuse content across multiple pages and update it from a single location. For more information, see Content Asset Data Binding in Page Designer.