Prerequisites: What Studio Expects to Already Exist
Studio installs into a working Contentstack setup. It does not create that setup for you, and it fails in confusing ways when a piece is missing — usually much later, when a canvas loads blank rather than when the thing is actually absent.
Two checks, in this order.
| Step | What it answers |
|---|---|
| Check Studio access | Is Studio switched on for your organization at all? A ten-second look at the app switcher. |
| Before you start | Do you have the stack, environment, locale and tokens the install will ask for? |
Do It With a Skill
analyze-project-fit reads your project and reports what is present and what is missing, before anything is installed.
Why the Order Matters
Access first, because everything below it is wasted effort if Studio isn’t enabled. The failure has no error message: you install three SDKs, wire a route, open Studio, and the canvas never appears. Checking the app switcher takes seconds and rules that out.
Then the stack. The install asks for four values — API key, delivery token, preview token, environment — and expects them to exist already. Studio assumes they’re in place and won’t provision them.
What This is Not
This group is about the Contentstack side. Nothing here touches your app. Code changes start at Install the SDKs.
Next
Install the Delivery SDK