How Site Building and CMS Data Split
Audience: front-end end users
In one sentence
The website module decides page structure and presentation; CMS data decides what content and products the pages show. Both belong to the current project and sit in the same sidebar group, but they have different jobs.
Comparison
| Enterprise Website (this chapter) | Enterprise CMS data (chapter 07) | |
|---|---|---|
| Typical menus | Front-end template, components, single pages, visual editor, global parameters, navigation | Content list, media, products, orders, shipping and payment, and more |
| Focus | Template binding, page layout, preview, and AI restyle | Content items, assets, commerce and settlement configuration |
| Result | An accessible site frame and pages | Business data that pages can reference |
Suggested collaboration order
- In Frontend Template Management, bind or initialize a template and get the temporary URL.
- Use Components / Single pages / Website visual editor to adjust structure and copy layout.
- Configure front-end entries in Navigation Menu.
- Maintain articles, media, products, and similar items on the CMS side for pages and components to reference.
- When you need a custom domain, combine Enterprise Domain with Bind custom domain on the template page.
Multi-tenant
After you switch projects, template binding, page components, and CMS data all switch to that project’s own set. They are not mixed.