Advice on organizing folder structures and schemas in Sanity.io projects

Need some advice here. I have this folder structure of the studio where basically almost everything is inside the “documents” folder. I want to cleanup the folder and make it more readable and logical.
Any tips ? Where would you move the docs in which folder because it can be pretty tough somethimes
😄

Hey Nino. One approach you could take is to group your files by "concern". That is, to have multiple directories for each "concern" (e.g. "settings" or "articles") and to have

documents

and

objects

etc. directories inside each of those.
You could even use plugins to help do this grouping (
https://www.sanity.io/docs/plugins ), however it's not strictly necessary because you can load your schemas from any location.

Which plugin do I need don’t see it on this page. Love Sanity, only issue is something structure on how to make it readable and clean.

Is it the “sanity install third-party-reviews” plugin

Sorry, I didn't explain that very well. What I meant is that you can create a plugin for each of your "concerns" (different parts of your app) and keep them in the

plugins

directory only for you. Your plugins don't have to add anything to the Studio UI, you can simply use them as a clean way to organise your code 🙂.
This page might be helpful:
https://www.sanity.io/guides/creating-my-first-sanity-io-plugin .

Thank you. I see a lot of people having modules, objects and documents. From multiple demo starters from Sanity. maybe I should do the same. But keeping code organized is never easy.

My current play project is nowhere near as complex as yours, but one of the first things I do to stay “sane” is organize my schema files into a simple file system that makes sense to me for the project I am doing. In this case, a simple blog concept. The naming conventions for directories within

./schemas

don’t matter as much as the imports and datatypes. In my case, I wanted to set up two different portable text block content inputs, so I created two objects named

ptext

and

ptextLite

, and this works how I want.

Thanks for sharing! I will first follow the design and based on the elements build documents and modules.

I often browse public repos from the Sanity team and community submissions for inspiration. Sounds like you’re on a good path!

Yes, I’v setup some of the Sanity team and community demos to take inspiration from. Usually I see modules, documents, objects.

My current little blog workflow experiment that I’m using to test community questions as well is intended to be a platform for a handful of my own different sites. As I add different documents for different projects, I may switch my file layout to match the different sub projects. I don’t have a prescriptive suggestion for you, but part of the fun in all of this is coming up with my own methods!

My current little blog workflow experiment that I’m using to test community questions as well is intended to be a platform for a handful of my own different sites. As I add different documents for different projects, I may switch my file layout to match the different sub projects. I don’t have a prescriptive suggestion for you, but part of the fun in all of this is coming up with my own methods!

Agree here if you think about it, there is no good or bad as long as it makes sense on the long term if you have to update it. Naming is the most important page, category, tag, list etc etc.

There are some amazingly deep discussions about best methods and a lot of strong opinions in nearly every dev community. I think I try to organize in a way that seems easiest for someone else to read and easiest for my own workflow. I sometimes start with multiple components combined in a single file, just to break them out - and sometimes with a bunch of different small component documents only to merge them later.

good point, for instance image field/type not to copy paste the same code over and over again, but create one component named image.js and share it with other document files. That’s what you are talking about right?

good point, for instance image field/type not to copy paste the same code over and over again, but create one component named image.js and share it with other document files. That’s what you are talking about right?

May I ask which font are you using I really like it. Could you share the settings from vscode?

Cascadia code and one of the oceanic themes with italics. https://github.com/microsoft/cascadia-code

Thank you very much!