VELORYZ STUDIO / KNOWLEDGE

Site pages and navigation

Page tree, routes, navigation and page settings.

Site pages and navigation

VELORYZ Studio · Pages, sections and layout Audience: Project owners, designers and frontend implementers Guide type: Practical Studio operations guide

Purpose

Site pages and navigation 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. Page tree, routes, navigation and page settings.

This guide covers page tree, routes, navigation and page settings. 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 Studio's website and project delivery workflows support page planning and design; a customer-facing page-tree/flex/grid canvas is not verified. Treat detailed layout controls as implementation guidance, not as promised buttons in a public editor.

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 inventory of the desired routes, page purpose, navigation hierarchy and content
  • Examples of layout behavior for narrow and wide viewports
  • A reusable section and global-element plan
  • A short list of measurable success criteria specifically for site pages and navigation.
  • 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 Site pages and navigation: 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 Site pages and navigation and supplement the general workflow above. Apply only the controls and roles actually available to your account or deployment.

  • Create a page inventory containing purpose, audience, slug, owner, status and canonical route.
  • Group navigation into clear destinations and avoid multiple labels for the same action.
  • Connect public site pages to the sitemap and ensure links are not orphaned.
  • Check 404 handling, slash behavior and nested route refresh.

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

  • Map each intended page to a clear user need and stable path before visual implementation.
  • Define section hierarchy, containers and spacing using semantic HTML and modern responsive CSS.
  • Keep global header, footer, primary navigation and repeated call-to-action regions consistent.
  • Preview changes at common mobile, tablet and desktop widths and with long translated text.

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

  • Every public path has one meaningful page title and an accessible primary heading.
  • Navigation reaches all essential routes without forcing users through search.
  • Containers do not overflow at narrow widths and media preserves correct aspect ratios.
  • Reuse does not accidentally duplicate IDs, headings or interaction handlers.

Also confirm that the result addresses the original objective: Page tree, routes, navigation and page settings.. 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

  • For a broken route, verify slash conventions and routing before altering links.
  • For clipping, inspect min-width constraints, overflow and fixed-position UI.
  • For a global region regression, revert the shared component rather than patching each page independently.

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

  • [Create and configure a page](/docs/studio/pages/create-edit/)
  • [Sections and containers](/docs/studio/layout/sections-containers/)
  • [Layout systems: flex and grid](/docs/studio/layout/flex-grid/)
  • [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.

Let’s talk
Make your project