Content systems
people (+ AI agents) can
actually operate.
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.
How I work
Content Models
Types, references & constraints.
Start with structure
A content model is an operating model. Types, references, and constraints decide whether people can publish without waiting on a developer.
Governance
People, process, technology.
Make the handoffs work
Who can change what, and when it goes live, matters as much as the schema. Scale usually fails in the handoffs, not the diagram.
Workflows
A path people can follow.
From brief to published
The useful system is the one a team can run on an ordinary Tuesday. I care about the path from brief to published.
Working with AI
A brief, an agent, a human check.
Keep the work reviewable
Agents raise the stakes on people, process, and technology. Structured content is what makes that work reviewable.
About me
I’m Ryan Mills, a Staff Content Operations Architect at Sanity. I work with teams on content models, workflows, and governance—the things that help people get from brief to published.
Before Sanity, I worked in agency and consulting roles. I care about useful structure: clear handoffs, reviewable work, and systems a team can run on an ordinary Tuesday.
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.
I’ve worked at
I’ve worked with
