Manage website content
Publish static pages and blog posts while keeping public forms and marketing context clean.
Use this guide when your team manages website content inside the workspace and wants public pages to support acquisition instead of living outside it.
Domain behavior
Public websites are tenant-aware:
- the platform root host shows the generic platform website for anonymous visitors
- tenant hosts like
tenant.platform.reuzio.comresolve to that workspace's public website - the tenant root path
/resolves to the configured homepage slug from Website Settings - direct content routes like
/page/aboutstill work as usual for published CMS pages
If a tenant domain is unknown or not active, the public website fails closed instead of falling back to another workspace.
Flow
Best practice
Static pages
Use CMS pages when you need evergreen site content with an optional public form and optional featured-offer merchandising. Keep the slug stable before publishing.
Blog posts
Use blog posts when the content is editorial and does not need the same conversion structure as a landing page.
Forms on CMS pages
If a static page includes a public form, treat it like a lighter marketing surface:
- confirm field mappings
- test submission
- verify the CRM handoff
Commerce sections on CMS pages
Use the Commerce sections JSON field on page create or edit when you want a CMS page to merchandise featured courses or events. The current section type is featured-offers, which can render:
- mixed featured offers
- course-only selections
- event-only selections
This keeps content, demand generation, and revenue entry points in the same public page.