Sanity Studio v3: Simplified yet Powerful Customization(sanity.io)

7 pointsby PaulWaldman4 ปีที่แล้ว2 comments

Sanity Studio v3: Simplified yet Powerful Customization

https://www.sanity.io/blog/sanity-studio-v3-simplified-yet-powerful-customization

2 comments

PaulWaldman4 ปีที่แล้ว

Hosting your own instance of Sanity Studio is new. https://www.sanity.io/docs/embedding-sanity-studio >Embedding Sanity Studio Sanity Studio is a React application distributed as a single dependency on npm. The application bundle is also ESM-compatible, meaning that it can be imported directly into browsers as a dependency on an URL. In principle, this means you can embed the Studio in any web application, as long as you can control the routing to redirect all Studio URLs to the page it‘s hosted.

But then, there is also this: https://www.sanity.io/docs/development >Sanity Studio always connects to a dataset in the hosted Content Lake, also when run locally. Your content is never stored locally. This means that you can have differences in the schema between a local and a hosted Studio. If the Studio finds content in a document that doesn't match its schema, it will display a warning.

What is the use case for hosting your own instance of Sanity Studio, while still having to rely on Sanity for hosting the content?

kmelve4 ปีที่แล้ว

Hi! Knut from Sanity.io here.

You could actually always host the Studio yourself, since it's an SPA. What's new is that we refactored it out of its custom webpack tooling and made it “just a React dependency” which allows you to embed it into other applications.

It's true that the Studio connects to the hosted data store (<pitch>but as many free projects as you want with pay-as-you-go for overages</pitch>), so the use case is the optionality to have your content workspace with your content models close to where you're consuming it. It also allows you to put the content workspace on a route so that content creators can go to a `/admin` or similar to edit content.