Authoring and publishing

This page complements /dashboard/web-apps-and-tours/landing-pages with product-facing wording support teams can reuse in tickets.

1. Provision the landing shell

Teams start from the organization’s landing pages list and create a new web app when permitted. Early decisions that matter:

Decision	Guidance
Default languages	Affects guest locale detection; unfinished translations can limit some modules. See /reference/languages-and-localization.
Visual identity	Check contrast and readability on real devices, including dark backgrounds if the brand uses them.
Domain / slug	Coordinate DNS and TLS with whoever runs infrastructure; a mismatch often shows as a blank page or certificate warning in the browser.

2. Compose tiles

In the landing detail workspace:

1. Add tile and pick a type from the catalog (basic, tour, engagement, etc.).
2. Reorder tiles so the first screen matches the story you want guests to see first—order is persisted when saved.
3. Preview in the dashboard to catch missing translations, broken links, or empty modules before sharing the public URL.

Duplication strategy

• Duplicate a whole landing for recurring events, then adjust only what changes.
• Copy individual complex tiles (for example chat or gallery) when reusing configuration; always re-check moderation copy and legal terms for contests or raffles.

3. Configure advanced availability

Many tiles support:

• Date windows when the tile should appear.
• Alignment with opening hours where relevant.
• Messaging for “closed” periods so guests know when content returns.

Keep physical signage and campaign dates aligned with these settings.

4. Nested navigation

Use nested landing page tiles for sub-sections. For busy events, avoid very deep navigation stacks on mobile—too many levels make the back path hard to follow.

5. Publishing checklist (support script)

• Each visible tile has a valid size for its type.
• External links use HTTPS and match your link-safety policy.
• Files meet your organization’s malware or document policy where applicable.
• Interactive tiles (chat, gallery, raffle) have an owner for moderation and incidents.
• Payment-related tiles were exercised in a staging or test context when real money is involved.

6. Post-publish monitoring

• Compare traffic or engagement before and after major QR or campaign changes.
• If marketing expects high click volume on a specific tile, confirm engagement looks plausible after go-live.

Related: Web app model, Layout sizing and visibility, Analytics and support.