Core pages first
Publish the main event guide while deeper pages continue through review.
Event Growth Studio
Preview the real microsite before anything goes live
Event microsite preview and publishing is the final go-live control inside Event Growth Studio, not the content intake or review process itself. It lets teams inspect the actual digital event guide before selected approved pages go live.
Structured for discovery. Assisted by AI. Approved by your team.
Conceptual workflow
Preview first; publish only approved pages.
Conceptual workflow
Conceptual workflow. Sanitised demo UI captures remain a follow-up once a demo session is available.
A real private preview, not a flat mock-up
Private preview lets reviewers experience the digital event guide as it will behave when published. They can inspect page structure, navigation, content completeness, source-informed copy and calls to action before a page becomes public.
- Review the actual page experience rather than a static document.
- Check links, page context and content readiness before release.
- Keep unfinished or unapproved pages out of the public site.
Example: phased publishing plan
Example only: page-level publishing can release ready information while incomplete areas stay private.
| Page or section | Preview check | Publishing decision |
|---|---|---|
| Main event page with approved summary and ticket link. | CTA points to official checkout and overview copy is approved. | Publish first as the public discovery entry point. |
| Programme page with two unconfirmed session times. | Source library shows stale schedule notes. | Keep private and return to review. |
| Venue access FAQ approved by operations. | Gate, travel and accessibility details match source notes. | Publish with the visitor information page. |
Page or section
Main event page with approved summary and ticket link.
Preview check
CTA points to official checkout and overview copy is approved.
Publishing decision
Publish first as the public discovery entry point.
Page or section
Programme page with two unconfirmed session times.
Preview check
Source library shows stale schedule notes.
Publishing decision
Keep private and return to review.
Page or section
Venue access FAQ approved by operations.
Preview check
Gate, travel and accessibility details match source notes.
Publishing decision
Publish with the visitor information page.
From preview to publication
Publishing follows approval; preview helps teams decide which selected pages are ready.
- 1
Open private preview
Review the page inside the real digital event guide environment before public release.
- 2
Check source and claims
Confirm AI-assisted copy against source material, ticket facts and owner notes.
- 3
Approve the page
Move the page to an approved state only after human review.
- 4
Publish independently
Publish the selected approved page without forcing every other guide page live.
- 5
Return updates to review
When facts change, bring affected pages back through review before republishing.
Page-level publishing controls
Digital event guides often need phased launches as programme, partner and visitor information becomes ready.
Partner pages later
Hold sponsor, exhibitor, optional public Media pages or restricted Press Room access until owners approve their content and audience.
Visitor pages when facts settle
Publish travel, venue and accessibility guidance when operational details are confirmed.
Updates after launch
Review changed content before republishing so stale details do not quietly drift public.
What publishing controls do and do not do
Publishing controls protect content readiness, but they do not turn the CMS into a commerce platform.
What they do
- Keep drafts private until approved.
- Let teams preview the real microsite before publishing.
- Publish pages independently as content becomes ready.
What they do not do
- They do not approve AI-generated copy automatically.
- They do not manage checkout, payments, orders, inventory or scanning.
- They do not guarantee rankings, AI citations, discoverability or sales.
What preview and publishing connects to next
Preview and publishing turns approved Event Growth Studio work into the public event destination without bypassing the rest of the workflow.
- Event Growth StudioStart from the parent system that organises structure, sources, review and launch control.
- Guided event microsite creationPlan the page families and source inputs the private guide is previewing.
- Event microsite platformUse the reviewed guide as a complementary microsite or the official event site.
- Event SEO platformStrengthen search foundations once approved pages and links are publicly available.
Related capabilities
Explore connected Event Growth Studio workflows without leaving the creation and CMS cluster.
- Event Growth StudioCreate, manage, publish and promote a complete digital event guide from trusted facts.
- Event content intakeConvert programmes, briefs, documents, biographies and media into structured guide content.
- Event source libraryKeep source ownership, provenance and freshness visible across the event guide and outputs.
- Event content review and approvalMove pages through draft, review, approval and publication with human sign-off.
- Event microsite platformDeploy the governed event guide beside an organisation website or as the official event site.
- Guided event microsite creationChoose page families, sources and review steps for a dedicated digital event guide or microsite.
- Event SEO platformBuild stronger search foundations with consistent event pages, metadata and structured data.
- EventSuite platformSee how Event Growth Studio sits alongside ticketing, operations and marketing modules.
Frequently asked questions
Is preview the same as a mock-up?+
No. The preview is intended to show the real private digital event guide experience before a page is published.
Can one page publish while another stays in review?+
Yes. Page-level publishing allows selected approved pages to go live independently.
Can AI publish a previewed page?+
No. Human approval is required before publication.
Does publishing replace ticket checkout?+
No. Published microsite pages can link to ticketing paths, but checkout, payments, orders, inventory and scanning remain elsewhere.
Can published pages be updated?+
Yes. Changed or stale content should return to review before republishing.
Preview the real guide before it becomes the public event destination
Use private preview and page-level publishing to launch Event Growth Studio content in stages instead of forcing the whole event live at once.
Check the actual microsite experience before approved pages become public.
Release ready pages while incomplete programme, partner or visitor sections stay in draft or review.
Keep the public event-site model, discoverability work and official ticketing journey connected to the same approved guide.
Preview before release.
Publish page by page.