Content editing with agents
Combine visual content editing and agent-assisted development in the storefront project.
The Site Editor combines visual content forms with Studio's work tools. Your team can configure content directly or ask an agent to help develop components, adjust content, and investigate a storefront problem.
Choose the right session
Use a content-editing session with Fast Preview when the change fits the site's existing components and schemas. For a new component, a runtime fix, or another code change, use a coding session with a development environment.
The current Site Editor exposes Preview, Content, and Code in the same project context. Available capabilities depend on the project and session. Fast Preview can support content work without provisioning a full coding sandbox.
Review the outcome
An agent's change uses the repository workflow. Preview the affected pages and inspect the changed content or code. Publishing follows the project's policy: some changes can publish directly; others need a request for review and repository approval.
A direct publish goes through the underlying GitHub publish sequence. Separate human approval depends on project policy and repository requirements.
Product boundaries
This guide belongs to Storefront because it explains operating a site. Studio's generic documentation explains how to build MCP Apps, connect context, organize tasks, and execute work in sandboxes.
Connecting an existing site to Studio is independent of upgrading its framework. See Legacy migration before combining the two changes.
Implementation reference: Studio Site Editor. Reviewed 2026-10-05.