Cert++
Close

Page Designer component design and rendering performance recommendations

Key Takeaway

Page caching drives Page Designer performance. The page uses the shortest cache setting, so move content that must not follow the page's cache setting, such as current inventory, into a remote include with its own cache setting.

Page Designer lets developers build reusable page types and component types. Merchants assemble them into storefront pages in the Business Manager visual editor. Good component design keeps each component self-contained and its meta definition stable, so merchants can reuse it safely. Good rendering performance comes mostly from correct page caching, small pages and cheap per-request logic.

Plan and design components

Before you develop page types and component types, work with the merchant and the ecommerce director on the pages, components, layouts and assets they need. Planning first matters because merchants then reuse those types to build many pages without coming back to you.

Make each component self-contained, so any region can handle it as an independent unit. Give each component its own default styling.

A component sometimes needs different styling inside a specific region, such as a product tile inside a carousel. In that case, adjust it with custom render settings using dw.experience.RegionRenderSettings and dw.experience.ComponentRenderSettings.

For optimal performance, keep the nesting within components to 5 or under.

For dynamic pages, name components for the page they are meant for, such as Product Detail Grid. The name matters because a component with attributes that the page's aspect type doesn't specify won't render correctly. Prepopulating regions with default_component_constructors also guides merchants toward the right components.

B2C Commerce Developer Study Guide

Checklist progress

0/237Learned

Prepare for the Exam

Play Today's Certle

Study Community

Ask questions and get the latest info from other B2C Commerce Developer studiers.