A small Sanity setup for non-technical clients.

How I structure a Sanity studio so the friend who runs a café can update their menu without calling me first.

The setup is deliberately minimal: one document type per content area, field names that read as plain English, no schemas the client will never touch. The studio's sidebar shows exactly the sections they need and nothing else.

The single most useful thing I do: write the field descriptions as if I'm leaving a note for someone who will never call me to ask a question. Usually, they don't.

If you're building a Sanity studio for a client, the most important thing to get right is the editing experience, not the schema flexibility. Start with what they'll actually publish, not with what the data model might eventually need.