Understanding how adding new content types in development affects production dataset

2 replies
Last updated: Sep 4, 2020
So curious. There is a currently deployed studio that is live right now.I am adding new content types in development to production dataset.
If I publish something in development - will that error out in production?
Or does it not effect anything?
Sep 3, 2020, 8:05 PM
Nothing will show up in production until you deploy the newest schema changes, because the deployed studio isnt aware of those new content types yet 😊 If you make changes to document types that have already been deployed, then you’ll get warnings in your studio in those documents 👍
Sep 4, 2020, 8:36 AM
Thank you! I wanted to do a sanity check (haha) - thats what I thought what happened, but as I work more and more on existing sanity project (yay) I wanted to make sure I understood that correctly.
Sep 4, 2020, 3:18 PM

Sanity – Build the way you think, not the way your CMS thinks

Sanity is the developer-first content operating system that gives you complete control. Schema-as-code, GROQ queries, and real-time APIs mean no more workarounds or waiting for deployments. Free to start, scale as you grow.

Was this answer helpful?