How CMS Data Relates to the Website
Audience: front-end end users
In one sentence
CMS data decides what the site can show, sell, and check out; website modules decide how pages look and how they are laid out. Both belong to the current project, but they have different entries and jobs.
Division of work
| Side | Typical capabilities | Manual chapter |
|---|---|---|
| CMS data | Content items, media, categories and tags, products and orders, shipping and tax, payment setup | This chapter (07) |
| Website building | Front-end template binding, components, pages, visual editor, global settings, navigation | [08-Corporate Website] |
Typical data flow
- Upload images in Media Management, then reference them in Content List / Products.
- Create dimensions in Category / Tag, then attach them when publishing content or products.
- Configure currency, shipping, tax, and payment methods so front-end checkout uses those rules.
- Order List / Payment Records store transaction results; funding details can also be checked in Enterprise Finance.
Do not mix up these entries
- Content List: CMS articles and similar content; the page title is often “Article Management”.
- Documentation List: see the Enterprise Documents chapter; the sidebar item is under Other (plan-controlled).
- Enterprise Docs: the right-side file library, not the CMS media library.
Multi-tenant
All CMS data is isolated by the current project (tenant). After you switch projects, you see a different set of content, products, and orders.