Understanding object types and schemas in Sanity.io

25 repliesLast updated: Feb 18, 2021

If I go with an object, I will have to lift it up, meaning I have to define it as a type, but this would then automatically show up as an option to define for editors?

Hi User. The object shouldn’t add to your hierarchy.

Hm. Creating the object would generally mean to:1. add it as a type
2. add it to the schema file

Correct?

And as I understand, this would add them to the general studio type sidebar.

Let me double check.

Sorry, I misunderstood you at first. Yes, that’s correct about the steps required. It’s generally a good thing as it allows for re-use.
An object won’t appear in the left-most sidebar in Sanity. Only documents.

There is some error in my conception of the whole process. Is there any good video that follows somebody through the creation of some complex schemas besides the simple introductionary ones?

Thank you for the help and the patience, User. Much appreciated.

Let me test a little first and then get back to you, if I still struggle with it.

Please let me find one for you. In the meantime, https://www.sanity.io/docs/object-type and https://www.sanity.io/docs/document-type offer some distinctions between the types. This distinction on the object page might help:

By default, object types can not be represented as standalone documents in the data store. If you want to define an object type that you’d like to be represented as a document with an id, revision and created and updated timestamps, you should define it using the
document
type instead. Apart from these additional fields, there’s no semantic difference between a document and an object.

I really like this guide: https://www.sanity.io/guides/implementing-a-content-model-in-sanity-io

Also, I’d invite you to check out fieldsets to see if they accomplish what you’re after.

And make sure to check out Knut’s video series on customizing schemas: https://www.youtube.com/watch?v=GbQ4dbQqduk

Sorry, last thing! 😆
I have found it valuable to set up some of Sanity’s starters and inspect their schemas. It definitely gives some insight into what’s possible and how things work.

I went through Knuts video series already and a lot of the docs. I will go through the things you have linked now and also inspect some of the starter schemas.

Thanks a lot for the valuable input, User!

Any time, User! 🙂 🙌

user A Dead links found 🙂 (the last two)

Is there a github repo for the docs so that I can help correct the docs, if I stumble over anything?

user L Those were just there to make sure you read them. 😆
Kidding. I’ll report those to the Sanity team. Thanks so much!

https://www.sanity.io/docs/donts-and-dos
https://www.sanity.io/docs/naming-things
Here are the correct links in the meantime.

Thanks for reporting those, User. User has already fixed them! 🚤

You are welcome User! Thank you for being that responsive in terms of help! :)

Hey user A!
In case anybody else is asking:
This series from User is genius when it comes to explaining the whole process of schema creation and organization. All the way from mapping out the schema in Figma, to explaining the documents, objects, plugs folder pattern used in the kitchen sink starter.

Invidious Link:

https://invidious.tube/playlist?list=PL46OzlGGU84RZw0R73RhMeqBZWlgBMHsg Youtube Link:

https://www.youtube.com/playlist?list=PL46OzlGGU84RZw0R73RhMeqBZWlgBMHsg

The exact video and time stamp mentioning the opinionated approach, documents, objects, plugs:
https://youtu.be/-B_Fxd6TMwA?t=112

Was this answer helpful?

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?

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

Related contributions