Storefront and Studio
Understand the relationship between the storefront offering and the extensible Studio platform.
Storefront groups the tools for building and operating websites and apps: the Blocks framework, Site Editor, commerce integrations, analytics, and observability. Its documentation follows concrete work on that digital experience.
Studio is the extensible platform those tools use. It supplies shared capabilities for connecting context, organizing tasks, running work in sandboxes, and extending interfaces through MCP Apps. Studio can support applications beyond storefronts.
Start with your task
If you want to compose a page, configure a product component, preview a campaign, or publish content, start with the Site Editor.
If you want to implement the components and functions that power that site, choose your Blocks framework version. The new next framework contract is a preview; existing Fresh and TanStack documentation remains versioned.
If you want to build a new Studio application or connect another system to its work loop, use the Studio developer guides.
Document the capability where people use it
The Site Editor's user guides stay in Storefront even though the editor runs inside Studio. The generic interface-extension API belongs to Studio. This gives each product one clear entry point while allowing guides to link to their shared platform dependencies.
Product-specific availability depends on the installed integrations and deployment. An extensible platform does not automatically provision every storefront service.
Implementation reference: Studio Site Editor. Reviewed 2026-10-05.