b2c-page-designer

To define page types and component types for Page Designer, create JSON files like homepage.json in cartridge/experience/pages and banner.json in cartridge/experience/components, then configure regions and attributes to meet the schema requirements for storefront content.

A region definition in Page Designer structures storefront pages by assembling component types into editable areas. You need region configurations when building homepages, product detail pages, or marketing pages to ensure a consistent editorial workflow for merchants.

To create reusable Page Designer components, define a Component Type JSON file in cartridge/experience/components with attribute groupings for modular content. This allows merchants to visually author and reuse content elements across different storefront pages.

Yes, you can use Page Designer to build a storefront homepage by defining a Page Type with multiple regions, then assembling marketing component types into those regions to create a visually authored, consistent experience across your B2C Commerce site.

Yes, the Page Designer schema requires meta definitions for every page and component type. These definitions include region configurations and attribute groupings that satisfy the structural requirements for the experience editor to render content correctly.

The best way to preview Page Designer pages is to define your page and component JSON files in the experience directories, then run your local B2C Commerce development environment to launch the experience editor and visually inspect the storefront content.