Editor overview
Editor architecture and panel responsibilities.
Editor overview
VELORYZ Studio · Editor foundation Audience: Designers, editors and stakeholders reviewing page changes Guide type: Design specification and team-managed workflow
Purpose
Editor 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. Editor architecture and panel responsibilities.
This guide covers editor architecture and panel responsibilities. Use it as an actionable design specification and team-managed workflow: verify the current UI and any provider configuration before relying on a control in production.
Availability and responsibility
The current public site does not expose a verified self-service canvas editor with drag-and-drop, layers, inspector or keyboard shortcuts. This section documents safe editing and review requirements for team-delivered websites; implement and verify any visual-editor UI separately before issuing click-by-click self-service instructions.
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
- A page URL, viewport width and annotated screenshot of the element to change
- The requested copy, images, links and interaction outcomes
- Acceptance criteria for desktop, mobile and accessibility
- A short list of measurable success criteria specifically for editor 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 Editor 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 Editor overview and supplement the general workflow above. Apply only the controls and roles actually available to your account or deployment.
- Explain how a professional visual editor would distinguish canvas, layers, properties and preview from the current public project creator.
- For current customer changes, identify the exact page, element, content and acceptance criteria in a written change request.
- Use owner CMS controls only for the fields actually exposed; avoid editing source files through untrusted embeds.
- Validate all user-visible changes in preview before publication.
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
- State which page and section requires a change and identify the selected element in a screenshot.
- Specify the exact replacement content, responsive expectations and what should remain unchanged.
- Review the proposed output in a preview or staging environment before publishing.
- Record the approved result, revision, and any new dependencies or media rights.
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
- Text remains legible, controls have accessible names and interactive elements are keyboard operable.
- Desktop, tablet and mobile layouts avoid overflow and reflow problems.
- Editing a component does not silently modify unrelated global sections.
- Changes can be traced to an approved revision or delivery note.
Also confirm that the result addresses the original objective: Editor architecture and panel responsibilities.. 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 selection or drag-and-drop controls are not present, do not search for nonexistent UI; submit the edit through project communication.
- If content overlaps or disappears at a viewport, report the URL and viewport dimensions.
- If an approved version breaks, ask the Studio to restore the last accepted release.
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
- [Canvas and viewport controls](/docs/studio/editor/canvas/)
- [Selection and direct editing](/docs/studio/editor/selection/)
- [Drag-and-drop editing](/docs/studio/editor/drag-drop/)
- [All VELORYZ documentation](/docs/)
- [Studio documentation](/docs/studio/)
- [Help Centre](/help/studio/)
- [/design/](/design/)
- [/motion/](/motion/)
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.
