VELORYZ STUDIO / KNOWLEDGE

Environments and release workflow

Draft/preview/live separation when supported.

Environments and release workflow

VELORYZ Studio · Preview, publishing, hosting and domains Audience: Release managers, site owners and client approvers Guide type: Practical Studio operations guide

Purpose

Environments and release workflow should be treated as an end-to-end responsibility, not an isolated button. Start by defining what will change, who can approve it and how success will be checked. Draft/preview/live separation when supported.

This guide covers draft/preview/live separation when supported. Use it as an actionable practical studio operations guide: verify the current UI and any provider configuration before relying on a control in production.

Availability and responsibility

The source includes CMS draft, preview, publish, history and restore operations. Actual hosting, DNS and SSL changes require appropriate infrastructure access; the public project creator does not self-publish an entire site.

Before committing time or budget, confirm who operates this workflow: the visitor, the client portal user, a Studio owner, or the delivery team. A feature described in design documentation is not automatically a public account entitlement.

Before you begin

  • An approved project scope, release checklist and tested production domain
  • Owner sign-off for content, responsive behavior, SEO and legal pages
  • Rollback path, backup and access to deployment diagnostics
  • A short list of measurable success criteria specifically for environments and release workflow.
  • A recovery plan if the proposed change creates a regression.

Recommended procedure

  • Locate the relevant area or public route. For new projects, establish the brief at /create/; for owner-only content changes, use authenticated Studio Control at /admin. Do not assume a missing feature exists.
  • Define the specific work item for Environments and release workflow: capture the initial state, user intent, relevant data, permissions, expected output and what must not change.
  • Follow the design and operating decisions listed below. Work in a draft, staging or reviewed project handoff where available; avoid editing live customer data experimentally.
  • Review the effect with real content and realistic viewport sizes. Record any exception and obtain the appropriate approval before a public change.
  • After the change, verify the public outcome rather than relying on a success message alone; preserve a reference to the reviewed version.

Topic-specific operating procedure

These steps apply to Environments and release workflow. The implementation must be verified against the current Studio permissions, deployed provider connections and approved project scope.

  • Define local, preview and production environment responsibilities, including environment variables and backend bindings.
  • Run source checks and migrations in the correct environment before release.
  • Record commit SHA, CMS publication revision and deployment status separately.
  • Do not expose test endpoints, dev-only credentials or provider secrets in production.

Evidence to retain

  • The original input or situation, and a clear before/after comparison.
  • The reviewed version, responsible owner and acceptance record.
  • Any limitation, follow-up decision, or safely reversible workaround.

Configuration and decision points

  • Stage content changes in the protected CMS draft or the project's code review environment.
  • Inspect preview separately from published pages; test forms, navigation and interactive components.
  • Publish only an approved version, preserving commit or CMS publication references.
  • Verify the real public domain, TLS certificate, redirects and indexing status after release.

When more than one implementation is possible, prefer the simplest approach that remains accessible, maintainable and compatible with the current source. Note any cost, licensing, privacy, ownership and performance implications before approval.

Verification checklist

  • Production URLs are correct, secure and return expected HTTP status codes.
  • Sitemap, robots directives, canonicals and social previews match the target domain.
  • No preview credentials, test secrets or draft-only content reach production.
  • Rollback instructions and an accountable release owner are available.

Also confirm that the result addresses the original objective: Draft/preview/live separation when supported.. Review the customer-visible language, error states, navigation paths and the relevant device widths. A green build or a successful save does not by itself establish a correct production outcome.

Troubleshooting and recovery

  • If deployment fails, inspect actual build and hosting logs before making another change.
  • If a domain is not ready, check DNS propagation and certificate status without claiming instant activation.
  • If a release breaks, restore the last stable version and document the incident.

When asking for assistance, include the exact public URL or project reference, a concise reproduction path, the expected behaviour, actual behaviour, relevant timestamps and a redacted screenshot if useful. Never include passwords, access tokens or private customer records.

Related reading

  • [Preview modes and test links](/docs/studio/publish/preview/)
  • [Pre-publish checklist](/docs/studio/publish/checklist/)
  • [Publish and republish](/docs/studio/publish/publish/)
  • [All VELORYZ documentation](/docs/)
  • [Studio documentation](/docs/studio/)
  • [Help Centre](/help/studio/)
  • [/docs/architecture/](/docs/architecture/)
  • [/docs/quality/](/docs/quality/)

Operational note

This article describes the Studio workflow and its acceptance criteria. Where a self-service control is not available, the action is coordinated with the Studio team rather than silently represented as automated.

Let’s talk
Make your project