Page Designer page types, components and aspects

What the exam expects

• Create a page type or component type as a meta definition JSON file plus a same-named script with a render function, in the right experience folder and with valid names.
• Choose attribute types for a marketer's editing need, and predict how required and default_value behave.
• Render pages with PageMgr.renderPage and regions with PageMgr.renderRegion, and print region markup without HTML-encoding it.
• Build dynamic pages with aspect types, dynamic_lookup and getPageByCategory/getPageByProduct, and prepopulate regions with default_component_constructors.
• Apply the rules for custom attribute editors, incompatible meta definition changes, page caching and the 3 MB page limit.

Key terms: page type (a page template whose meta definition describes regions); component type (a reusable building block whose meta definition describes merchant-configurable attributes and optional regions); meta definition file (the JSON file that defines a type); region (an area that holds components); aspect type (a meta definition that makes a page dynamic, with attributes passed at render time and an optional category or product binding).

Key facts

Check yourself