Sanity

Sanity serves as the central content repository for Total Ventures, allowing me to define content schemas in code and manage editorial assets with a level of precision and developer experience that traditional CMS platforms cannot match.

What it is

Sanity is a real-time, API-first headless content management system. This means content is stored as structured data and delivered via an API, decoupled from any specific presentation layer. Its core strength lies in its Content Lake, a global data store, and the Sanity Studio, a customizable content editing environment built with React. I define content types and fields using JavaScript or TypeScript schemas, which then generate the Studio interface. This code-first approach to content modeling is critical for maintaining consistency and enabling robust developer workflows. Content delivery is handled through a powerful query language called GROQ, which allows for precise data fetching and manipulation.

How I use it

Across Total Ventures, Sanity is the source of truth for all editorial and structured marketing content. For Pregnancy Power Hour, it powers the entire blog, storing articles, author profiles, and category metadata. On Total Formula 1, I use it for race recaps, driver biographies, and team news. The Studio itself is a custom build, tailored to the specific content models for each brand, allowing my AI agents to publish drafts and manage assets directly via the API. This agentic engineering approach means content generation and publishing can happen with minimal manual intervention. The frontend applications, deployed on Vercel, fetch content from Sanity's API at build time or on demand. While Firestore handles user-generated data and application state, Sanity specifically manages the curated, editorial content that drives engagement.

Why this over alternatives

Sanity earned its slot primarily due to its schema-in-code approach and the flexibility of its Studio. Defining content models in TypeScript means I can version control my schemas alongside my application code, ensuring consistency and enabling faster iterations. The real-time content preview functionality is invaluable; editors can see changes immediately, which accelerates the feedback loop significantly. GROQ is a powerful, intuitive query language that makes fetching exactly what I need, and nothing more, straightforward. Compared to alternatives, Sanity offers a superior developer experience for structured content, allowing me to build highly customized editorial interfaces without being constrained by a rigid platform. Its API-first nature also integrates seamlessly with my custom agent orchestration layer, making it an ideal backend for automated content workflows that might otherwise require complex integrations with Firebase Hosting + Cloud Functions for custom API routes.

Where it falls short

While robust, Sanity does have its limitations. The initial setup and schema definition can present a learning curve for those not comfortable with code-first content modeling. For a solo operator, this overhead is manageable and quickly pays off, but it's not a click-and-deploy solution like some simpler blog platforms. While its asset management is good, for highly advanced image optimization or complex media workflows, I often integrate external services. Also, Sanity primarily focuses on content delivery; managing complex user authentication or authorization for content access on the frontend typically requires building custom solutions on top of its API, rather than relying on built-in features.