Create the Project: Where Authors Compose
A Studio project is the workspace authors open. Creating one links your Contentstack stack to Studio and provisions the content type that stores every composition record. Until it exists, there is nowhere for a Template or Section to live.
| Step | What it does |
|---|---|
| Create a Studio project | Links the stack, provisions the compositions content type |
| Environment, language & canvas URL | Tells the project which environment to preview from, which locale, and which route to load |
| Studio web app: browser-only steps | The handful of settings that exist only in the Studio UI |
Do It With a Skill
configure-studio sets environment, language and Canvas URL in one guided pass instead of clicking through the settings panels.
The Part That Trips People Up
The Canvas URL is a path, not a URL — /canvas, not http://localhost:5173/canvas. Studio joins it to the environment’s per-locale Base URL at render time:
Base URL (environment) Canvas URL (project) http://localhost:5173 + /canvas = http://localhost:5173/canvas
Put a full URL in that field and the project is pinned to one environment, so preview breaks everywhere else. Leave the environment’s Base URL empty and the canvas stays blank no matter what the route does.
Two Layers, Two Owners
Project settings live in the Studio web app; the route they point at lives in your code. Both have to agree. That split is why setup fails quietly — each half looks correct on its own.