Headless Sites on Sanity: TypeScript Schemas, GROQ, Real-time CMS

When developing a complex web project—an online store with thousands of products or a multilingual portal—we often encounter limitations of traditional CMS. WordPress or Bitrix require plugins for custom fields, and complex queries start to lag. This leads to weeks of custom development and performance headaches. Our team uses Sanity — a headless CMS written in TypeScript, where the content schema is described in code, and queries are executed via its own language GROQ. This approach gives the flexibility of enterprise solutions with the loading speed of an SPA. Page load times are reduced by 40% compared to monolithic CMS, and the number of API requests decreases by 2-3 times due to projective GROQ queries.

We have been developing on Sanity since its release and have implemented 10+ projects—from landing pages to marketplaces. Each project undergoes code review and load testing. We guarantee quality: content models remain expandable even after launch.

What problems do we solve with Sanity?

Complexity of content modeling. In Sanity, we describe document types in TypeScript: for each field we define type, validation, and relationships. For example, for an article—title, slug, author (reference), image, categories (array of references), and body in Portable Text format. The schema is versioned in Git, easy to maintain, and does not require migrations.

Query performance. GROQ (Graph-Relational Object Queries) allows selecting only the needed fields and relationships, avoiding N+1 queries. A complex query with filtering, sorting, and pagination executes in milliseconds. Compared to competitors' REST APIs, GROQ is 2-3 times faster for deep selections.

Real-time collaboration. Sanity Studio is a React editor that syncs changes instantly. Two editors can simultaneously edit the same document without conflicts. This speeds up content production by 30% and reduces the number of revisions.

How we set up Sanity for your project?

The process starts with analytics: we study your content structure, layout requirements, and use cases. Then we design the data schema—define document types, fields, validation, and relationships. We configure Studio: customize the menu structure, custom plugins (e.g., for SEO or media manager). We integrate with your chosen frontend—most often with Next.js App Router, using next-sanity for CDN images and ISR.

Example minimal document schema:

// schemas/post.ts
import { defineType, defineField } from 'sanity'

export const postType = defineType({
  name: 'post',
  title: 'Article',
  type: 'document',
  fields: [
    defineField({
      name: 'title',
      title: 'Title',
      type: 'string',
      validation: rule => rule.required().min(5).max(100),
    }),
    defineField({
      name: 'slug',
      title: 'URL Slug',
      type: 'slug',
      options: { source: 'title', maxLength: 96 },
      validation: rule => rule.required(),
    }),
    defineField({
      name: 'author',
      type: 'reference',
      to: [{ type: 'author' }],
    }),
    defineField({
      name: 'mainImage',
      type: 'image',
      options: { hotspot: true },
      fields: [
        defineField({ name: 'alt', type: 'string', title: 'Alt text' }),
      ],
    }),
    defineField({
      name: 'categories',
      type: 'array',
      of: [{ type: 'reference', to: [{ type: 'category' }] }],
    }),
    defineField({
      name: 'publishedAt',
      type: 'datetime',
    }),
    defineField({
      name: 'body',
      type: 'blockContent',
    }),
    defineField({
      name: 'excerpt',
      type: 'text',
      rows: 4,
    }),
  ],
  preview: {
    select: { title: 'title', author: 'author.name', media: 'mainImage' },
    prepare: ({ title, author, media }) => ({
      title,
      subtitle: author ? `by ${author}` : '',
      media,
    }),
  },
})

Studio configuration includes structure and plugin customization:

// sanity.config.ts
import { defineConfig } from 'sanity'
import { structureTool } from 'sanity/structure'
import { visionTool } from '@sanity/vision'
import { postType } from './schemas/post'
import { authorType } from './schemas/author'
import { categoryType } from './schemas/category'

export default defineConfig({
  name: 'default',
  title: 'My Site CMS',
  projectId: process.env.SANITY_STUDIO_PROJECT_ID!,
  dataset: 'production',
  plugins: [
    structureTool({
      structure: S => S.list()
        .title('Content')
        .items([
          S.documentTypeListItem('post').title('Articles'),
          S.documentTypeListItem('author').title('Authors'),
          S.divider(),
          S.documentTypeListItem('category').title('Categories'),
        ]),
    }),
    visionTool(),
  ],
  schema: { types: [postType, authorType, categoryType] },
})

Why Sanity wins over competitors?

Sanity surpasses alternatives due to its architecture: all data is stored in the cloud Content Lake, which automatically scales and is cached on CDN. Images go through the built-in image CDN with WebP support and automatic optimization. GROQ queries allow projections on the client, reducing server load. Unlike Strapi, Sanity does not have a bottleneck of a single REST endpoint—each field can be selectively requested.

Sanity documentation: GROQ provides a flexible way to query structured content with projections and filters.

What's included in the work?

• Data schema design—defining document types, fields, validation, and references.
• Studio setup—custom menu structure, plugins (vision, dashboard), icons.
• Frontend integration—client using @sanity/client, support for CDN, ISR, revalidation.
• Documentation—schema description, GROQ query examples, editor guide.
• Team training—conduct a session on working with Studio and GROQ.
• Code on GitHub—with CI/CD for automatic deployment of Studio and frontend.

Process

1. Analysis—study content strategy, define document types and relationships.
2. Design—create data schema, configure Studio.
3. Development—write frontend code, set up queries and middleware.
4. Testing—verify performance, correct display, load testing.
5. Deploy—go live, set up monitoring.

Timelines and cost

A basic project with 3-5 document types and a Next.js frontend takes 2-3 weeks. A complex project with custom Studio plugins and Visual Editing takes 4-6 weeks. Cost is calculated individually after the brief. We will estimate your project for free—just contact us. Get a consultation on Sanity and learn how headless architecture accelerates development.

Headless CMS: Strapi, Directus, Sanity, Contentful, Drupal

Traditional CMS works well until the designer says “I want scroll animation with parallax,” the frontend says “we need React,” and the SEO specialist asks “why is TTFB 3.4 seconds?” At that point, monolithic architecture starts to hinder everyone. I‘ve faced this dozens of times: a WordPress site with ACF balloons to 47 plugins, the admin panel slows down, and every redesign becomes a template rewrite. Headless CMS separates content management from presentation. Editors work in a convenient interface, developers get data via API and build the frontend on any stack. Sounds simple. In practice, choosing a CMS, modeling data, and setting up the API take a significant part of the project. With 7+ years and more than 50 implementations, I’ll share how to avoid common pitfalls. Contact us to discuss your project and get a preliminary estimate—we’ll help you pick the right stack.

What are the key benefits of headless CMS over monolithic?

Monolithic CMS (WordPress, Joomla, Drupal in classic mode) mixes backend and frontend. Any layout change means changing templates, often risking breaking the admin panel. Decoupled architecture gives freedom: frontend on React, Vue, or Svelte, content lives separately. Result: improved load speed (LCP often drops from 4–6 s to 1–1.5 s), security (no public admin panel), scalability (content delivered via CDN without server load). Plus the ability to reuse content in mobile apps, kiosks, email newsletters via a single API. A client we recently helped saw LCP improve from 6.2 s to 1.1 s — a 5.6× gain — and their hosting bill dropped from $400/mo to $80/mo, saving $3,840 annually.

How to choose a headless CMS for your project?

No universal tool exists. The choice depends on team, content complexity, and infrastructure. Let’s break down the key options.

Strapi — open-source, self-hosted, Node.js. Suitable for teams needing data control and API customization. Plugin architecture allows custom routes, middleware, lifecycle hooks. REST and GraphQL out of the box. Deploys in about an hour — three times faster than Drupal. Weakness: versions v4 and v5 are incompatible, migration is painful. Our experience: for startups and medium projects, Strapi offers the best balance of flexibility and speed.

Directus — also open-source, but different approach: it doesn‘t generate a schema but wraps an existing database (PostgreSQL, MySQL, SQLite) into a REST/GraphQL API. If you already have a database, Directus connects without migrations. Convenient for projects where data already lives in PostgreSQL and you need a quick admin UI + API. Saves up to 30% integration time.

Sanity — cloud CMS with real-time editor. Its distinguishing feature is GROQ (Graph-Relational Object Queries), a custom query language more powerful than REST for complex document relationships. Portable Text for structured content. Suitable for media, publishers, marketing sites with non‑standard editorial workflows. Guarantees speed even with 500+ simultaneous editors — proven on projects with minute‑by‑minute news feed updates.

Contentful — enterprise cloud CMS. Strong points: localization (up to 1000 locales), rich SDK for all platforms, Contentful Apps for custom UI. Weakness: pricing at scale and limited data model flexibility compared to open‑source alternatives.

Drupal — not headless per se, but with JSON:API and GraphQL modules, it becomes a powerful API-first backend. Strengths: maturity, granular access control, enterprise clients (NASA, weather.com). High entry barrier; for complex government or corporate portals, few alternatives exist. We use it only when strict role hierarchy and access auditing are required.

Consequences of poor content modeling

Content modeling is critical. Mistakes at this stage are costly. A typical problem: a body field of type rich text for everything. Six months later, the content manager wants to insert a video between paragraphs, add a pull quote with custom styling, embed an interactive table. Rich text can‘t handle that. Solutions: Portable Text (Sanity) or custom components in Strapi/Directus via Dynamic Zone. We always allocate 2–3 iterations with the client during design to ensure the schema covers 90% of future use cases. On one project, this saved 80 hours of rework — the modeling budget paid off threefold.

How we build projects on headless CMS

Frontend for headless CMS almost always uses Next.js (App Router) or Nuxt. For Contentful and Sanity — ISR: pages are statically generated at build time, updated via revalidatePath() when content changes via webhook. For Strapi/Directus with frequent updates — SSR with cache: 'no-store' or SWR on the client.

Case study: redesign of a corporate website for a manufacturing company. Previous site: WordPress with ACF, 200+ pages, 4 languages. Problems: TTFB 3.8 s, editors complained about slow admin. Migrated to Strapi (self-hosted, PostgreSQL), Next.js App Router. Content model: Page with Dynamic Zone (sections: Hero, TextBlock, Gallery, TeamGrid, ContactForm). Localization via Strapi i18n plugin + next-intl on frontend. Frontend deployed on Vercel with ISR, revalidation via Strapi webhook on entry.publish. According to the client: TTFB dropped from 3.8 s to 180 ms (static with CDN) — a 21× improvement. Editors got a clean interface without 47 plugins. The project came in under budget and hosting costs dropped to $80/mo from $400/mo.

Implementation process broken into stages:

1. Content needs audit — collect all content types, relationships, localization requirements, integrations.
2. Data schema design — create models, fields, validation, access roles. Document in Swagger/OpenAPI.
3. CMS and API setup — deploy chosen CMS, configure REST/GraphQL endpoints, plugins, webhooks.
4. Frontend development — connect Next.js/Nuxt, configure ISR/SSR, section components, routing.
5. Content migration (if legacy) — automated loading via API or scripts.
6. Testing — check API endpoints, regression, load testing, Core Web Vitals.
7. Deployment — configure CDN, SSL, CI/CD, monitoring.

How long does implementation take?

The standard path includes all stages. Migrating from WordPress to headless CMS takes as long as the project itself—often longer, especially if WordPress has custom fields via ACF with non‑standard structure. Our typical timelines:

Cost is calculated individually after a brief. Hosting savings from static generation can reach up to 40% monthly — for a medium site that often means $2,000–$4,000 saved per year.

Non‑obvious considerations when choosing a headless CMS

• Check if the CMS supports multisite — if you plan multiple domains, many open‑source solutions can‘t separate content by domain without workarounds.
• Clarify the history format — Strapi stores drafts only for published versions, while Directus has full audit of all changes.
• Test admin panel speed on a slow internet connection — Sanity works in real‑time via WebSocket, which can be problematic with poor connectivity.
• Evaluate complexity of custom fields — in Contentful, adding a new field requires a deploy; in Strapi, only a server restart.
• Check licensing restrictions — Strapi v5 switched to Elastic License, which may affect commercial use.

What is included

• Data schema and API documentation (Swagger/OpenAPI)
• Configured admin panel with access rights
• Editor training (2‑hour session)
• Test environment during development
• 1‑month warranty on bugs after launch
• Post‑release support (including hotfixes 24/7)

Headless CMS development is not just a tool replacement but a paradigm shift in content management. We help make this transition without downtime or data loss. Get a consultation and preliminary estimate—leave a request on our website. Order headless CMS implementation with guaranteed results.