Hospitality Content Studio · Documentation
How to Use This Demo
Driving Hospitality Content Studio in the host, the Cloud/OSS inspector, and the operator console — with honest labels.
← Hospitality Content Studio- 1
Signing in
The ecosystem is gated. Open the live demo and sign in as the universal owner (admin / admin@123) to generate, edit, and publish copy, or as the read-only viewer to browse drafts, versions, and published copy. The owner-only configuration (the brand guardrail list) is never sent to the browser for an unauthorized session.
- 2
Generating copy
Open app 06 from the launcher. In the operator console, pick a property, then choose a content-type (tagline / description / highlights / POI prose), a voice (warm / luxury / family / concise), and a language (English / हिन्दी). Press Generate: the one metered stage runs and a draft appears with its reading-ease score and any brand flags. Edit the draft inline — QC re-runs deterministically on every change — then Publish. Publish is blocked while a guardrail flag is present.
Open the dark "Behind the scenes" inspector to see the honesty layer: the Cloud/OSS mode toggle, the per-stage trace (context → brief → generate → QC + brand guardrails), and the cost meter. None of this instrumentation appears on the studio surface itself.
- 3
Versions + guardrails
Every publish appends a version with a note, so the history is always recoverable. The owner-only CONFIGURE section holds the brand guardrail list — the owner-added banned phrases that join the built-in banned claims. Viewers see drafts, versions, and published copy but not the configuration; the owner-only controls are absent from the DOM for a viewer session.