Edit pages, navigation, themes, and reusable components

Know what the editor is changing #

The canvas is the page. Select an element to expose controls for its content, attributes, layout and style. When elements overlap or nest deeply, use the layer tree to select the exact node rather than repeatedly clicking the canvas.

• Canvas: direct editing and the closest representation of the page.
• Layers: the parent-child structure of sections, components and elements.
• Properties: controls that apply to the current selection.
• History: reversible editing steps. Test undo before making a broad change.
• Assistant: a plain-language edit request scoped to the page or selection.

Edit pages and navigation #

1. Open the page from the website dashboard and confirm its name and URL.
2. Select text, images, buttons or containers and change the smallest useful property. Save before navigating away.
3. Create, rename, reorder or remove pages from the page controls available to your role and plan.
4. Update navigation links after a page URL changes. Search the site for buttons or cards that still point at the previous address.
5. Preview the navigation with a mouse, keyboard and narrow viewport. A collapsed menu must open, keep focus visible, and reach every important destination.

Use themes and shared components deliberately #

Use theme controls for decisions that should apply across the site: brand color, typography, base sizing, content width, spacing, brightness and corner treatment. Use element controls for an intentional exception.

Save headers, footers, repeated calls to action and stable sections as reusable components. Editing a shared component changes every page that references it. Review the usage list before saving a broad change. Detach a page-specific copy when it should stop following the shared source.

Use AI edits with an escape route #

Select the narrowest scope that contains the intended change and describe the result, not implementation jargon. Review the page after each request. Use history or undo immediately if the result affects unrelated content.

AI editing does not remove your responsibility to check facts, URLs, responsive behavior, accessibility or database bindings. Save a known-good state before a large structural request.

Common editor problems #

The wrong element is selected

Choose it in Layers and confirm the selection outline before changing a property.

A change appears on several pages

You edited a reusable component or theme value. Undo, then detach the local copy or use a local property if the exception is intentional.

A control is missing

Confirm the selection type, role and plan. Some controls are hidden when the current user cannot perform the operation.

Publish starts before the last edit appears saved

Wait for the save state to finish. The editor asks the save manager to flush before publish, but a network failure still needs a retry.