How Templates, Components, Pages, and Navigation Relate

Audience: front-end end users

Object relationships

Front-end template (site skin / capability pack)
    │
    ├── Website global parameters (site-level configuration)
    ├── Navigation menu (front-end entry structure)
    │
    └── Single page ──references──► Component
            │
            └── Preview / edit / AI adjust in the visual editor

Object	Description
Front-end template	The site template bound to the tenant; decides base capabilities and the default page set
Global parameters	Site configuration shared across pages (metadata and similar)
Component	Reusable blocks (such as cart, checkout, content blocks)
Single page	A named page (such as home, pricing) that can attach components
Navigation menu	Front-end menu tree pointing to pages or external links
Visual editor	Change pages/components in a preview context, including AI assistance

Common paths

Change the whole site look / capabilities: Frontend Template Management → switch or initialize a template.
Change one page: Single Page Management → open the page; or switch the page in the visual editor and edit.
Change a reusable block: Component Management → edit component metadata.
Change top / side navigation: Navigation Menu Management.

Use the fields and buttons on each page. If no template is bound, some site-building features may be unavailable or ask you to initialize first.