Cert++
Close

Cartridge setup for Page Designer page and component types

Key Takeaway

Every Page Designer page type and component type is a JSON meta definition file plus a script file with the same name, in the same folder under experience/pages or experience/components. Custom attribute editors also need a script file, even an empty one.

Page Designer lets merchants build storefront pages in a visual editor in Business Manager. They build those pages from page types and component types that developers create and package in custom cartridges. Each type needs a JSON meta definition file and a script file in fixed folders. The folder path and file name of each type also set its ID. A separate cartridge can add localized names and thumbnails for the visual editor.

How Page Designer splits the work

Page Designer splits the work between developers and merchants. Developers build reusable page types and component types. Merchants drag those types onto a canvas in the Page Designer visual editor in Business Manager to design, schedule, and publish pages.

Each page or component a merchant creates is an instance of a type. So merchants can build many pages without asking the developer for changes.

Developers package their types in custom cartridges. A typical implementation uploads two custom cartridges to a site. One cartridge holds the page types and component types. The other cartridge holds supporting UI artifacts, which are localization resource bundles and thumbnail images for the visual editor.

SFRA includes Page Designer page types and component types built for SFRA, such as headers, carousels, and product tiles. Developers can customize these types or use them as code examples for their own types.

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.