01
Models
A content model is an operating model. Types, references, and constraints decide whether people can publish without waiting on a developer.
01/Content operations
Ryan Mills/Staff Content Operations Architect at Sanity
I work on content models, workflows, and governance for teams using Sanity. I’m a Staff Content Operations Architect at Sanity, and I write here about the practice of content operations.
02/How I think
01
A content model is an operating model. Types, references, and constraints decide whether people can publish without waiting on a developer.
02
Who can change what, and when it goes live, matters as much as the schema. Scale usually fails in the handoffs, not the diagram.
03
The useful system is the one a team can run on an ordinary Tuesday. I care about the path from brief to published.
04
Agents raise the stakes on people, process, and technology. Structured content is what makes that work reviewable.
03/Writing
No essays published yet. New writing will be listed here.
04/Earlier work
Selected names from earlier agency and consulting work, before Sanity.
“Working with Ryan was a game-changer for our business. His insight, creativity, and attention to detail were exactly what we needed, and we couldn’t be happier with the results.”
“Ryan made things simple, clear, and genuinely enjoyable. He brought structure without stress and insight without jargon.”