How to document a Sanity build for a non-technical team
Three readers, three short documents, and one test that tells you whether the handover worked.
How to set up Sanity so marketing teams publish without calling a developer. Content modeling, preview workflows, and the mistakes that make a CMS annoying for non-technical people.
Three readers, three short documents, and one test that tells you whether the handover worked.
Most preview setups go unused because they were built for the developer. Here is what one looks like when it's built for the editor and the reviewer.
The schema is only half of a content model. The other half is what the editor sees when they open the Studio on a Tuesday afternoon.
Sanity is flexible enough to build a CMS nobody on the marketing team can use. The five ways that happens, and what to do instead.
The persona idea applied to navigation and content structure: how to serve patients, referring providers, and partners from one site without building three.
The stack I build every healthcare site on, explained from the problems it solves: editorial independence, migration safety, compliance, and performance.