sfnext-page-designer
Build merchant-editable Page Designer content in a Storefront Next project: components decorated with @Component/@AttributeDefinition/@RegionDefinition, page routes decorated with @PageType, <Region> rendering, fetchPageWithComponentData, component loaders and fallbacks, the generated static registry, and the pnpm cartridge:generate / cartridge:validate / cartridge:deploy workflow. Use when adding or editing a Page Designer component, exposing a region on a route (home, PDP, PLP, search), fetching a page by pageId or aspectType, marking a Region critical, debugging a component that does not appear in the Business Manager palette or renders empty, or reviewing Page Designer code. Do not use for classic ISML/SFRA Page Designer (use b2c:b2c-page-designer), for turning a Figma frame into blocks (use figma-to-sfnext-pagedesigner:figma-to-sfnext-pagedesigner), or for plain React components that merchants never edit (use storefront-next:sfnext-components).
Pinned to revision fe78868e0e70, so it is the text this page describes rather than whatever the author pushed since.
Files
- skills/sfnext-page-designer/SKILL.md
- skills/sfnext-page-designer/evals/trigger-evals.json
- skills/sfnext-page-designer/references/BUSINESS-MANAGER.md
- skills/sfnext-page-designer/references/COMPONENT-REGISTRY.md
- skills/sfnext-page-designer/references/DECORATOR-PATTERNS.md
- skills/sfnext-page-designer/references/REVIEW-CHECKLIST.md
- skills/sfnext-page-designer/references/TROUBLESHOOTING.md
Every link opens the file at its source, pinned to the revision this page describes.