Product overview
What Studio is, how projects move from draft to live.
Product overview
VELORYZ Studio · Product overview and onboarding Audience: New customers, Studio collaborators and product evaluators Guide type: Practical Studio operations guide
Purpose
Product overview 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. What Studio is, how projects move from draft to live.
This guide covers what Studio is, how projects move from draft to live. 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
VELORYZ Studio is a creative and technology team with a public project creator, consultation flow, design references, protected administrative CMS and a private client portal. The blueprint also describes possible visual-editor capabilities; these are not documented as available customer-facing controls until implemented and tested.
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
- The desired site or digital product, target audience, business goals and decision-maker
- Examples of preferred visual direction and the content available for the project
- Budget assumptions, launch constraints, integrations and required approvals
- A short list of measurable success criteria specifically for product overview.
- 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 Product overview: 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
The following steps are specific to Product overview and supplement the general workflow above. Apply only the controls and roles actually available to your account or deployment.
- Define Studio as the team, website, protected CMS, project creator and client collaboration experience.
- Document the journey from brief to discussion, proposal, build, review, release and support.
- Distinguish deployed site features from future-product ideas and conceptual Studio editor controls.
- Use the actual Create, Book, Pricing, Design and Client Portal routes as examples.
Evidence to retain
- A short before/after record of the actual user-visible change or reviewed deliverable.
- The exact site URL, owner or reviewer, and the approval or release reference.
- Any unresolved limitation, assigned follow-up, and a safe mitigation.
Configuration and decision points
- Begin with /create/ and outline the intended project before choosing a visual direction.
- Review /services/, /work/ and /design/ for the Studio's actual delivery offerings and references.
- Use /pricing/ to understand indicative estimates; confirm deliverables and payment stages in writing.
- Request a discovery call through /book/ and use the project reference for follow-up.
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
- The brief describes a measurable goal, intended pages, real content owner and review roles.
- Preview, approval and publication are distinct stages and have named owners.
- Reference material is marked as inspiration rather than pre-approved original work.
- No unverified self-service editor or automatic publishing capability is implied.
Also confirm that the result addresses the original objective: What Studio is, how projects move from draft to live.. 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 the public creator does not retain an answer, retry the step and preserve a local copy of the brief.
- If a quoted figure is unclear, request a written scope rather than assuming it includes every integration.
- If a feature is absent, record it as a requirement for the Studio team.
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
- [Documentation home](/docs/studio/)
- [Product concepts and terminology](/docs/studio/concepts/)
- [First project walkthrough](/docs/studio/start/first-project/)
- [All VELORYZ documentation](/docs/)
- [Studio documentation](/docs/studio/)
- [Help Centre](/help/studio/)
- [/create/](/create/)
- [/docs/overview/](/docs/overview/)
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.
