Contentful Space and Content Model Setup

A client arrives with a ready-made React application — content lives in JSON files. Each release involves copying data via Slack, edits get lost, microcontrollers go haywire. Switching to Contentful is a lifesaver, but a wrong content schema turns the CMS into a swamp. Mistakes in field types or missing validation kill scalability. We configure the Space so that developers and content managers don't curse everything in sight.

Over 5+ years of working with Contentful, we've accumulated hundreds of hours of optimization. For example, one client was losing up to 20% of content during manual migration — after setting up the Space with automatic validation, errors disappeared completely. The cost of such setup varies depending on model complexity and number of environments. Below are the key stages of professional setup.

How to Design a Content Model for Scale?

Content Model is the skeleton of the project. Improper normalization leads to N+1 queries and overcomplicated editor forms. We follow the rule: one content type — one entity (article, author, category). For a blog, 4–6 types are enough. Example structure:

Use field-level locale for SEO fields (title, description) — this provides flexibility without duplicating content. According to Contentful's official documentation, proper localization with field-level locale reduces duplicate fields by 40%. For projects with 5+ locales, we recommend not exceeding 10 Content Types — otherwise editor interface performance drops.

GUI, CLI, or Codegen?

CLI approach is 3 times faster than manual GUI creation and allows versioning the model in Git. Compare:

For production, we combine CLI + codegen: export model, edit JSON, import via CI. This saves 2 days on every model change and reduces content management costs by 30–50%. Contact us for a Space architecture consultation — we'll analyze your model in 30 minutes.

Environment Setup and API Tokens

Use separate environments for staging and production. Each environment has its own CDA, Preview, and CMA tokens. Never use a CMA token on the frontend — it's a security hole.

# Create staging environment and copy model from master
contentful space environment create --name staging \
  --environment-id staging --source master

In the frontend SDK, use the CDA token with the staging environment:

const client = createClient({
  space: SPACE_ID,
  accessToken: STAGING_CDA_TOKEN,
  environment: 'staging',
})

Automating Model Export to Git

Use Contentful CLI to export the model without content:

contentful space export --space-id xxx --skip-content --export-dir ./model

The file contentful-export-xxx.json is stored in the repository. When the model changes, import via CI into the appropriate environments. This eliminates human error and speeds up deployments. According to Contentful official documentation, this is a best practice for team collaboration.

Generating TypeScript Types from the Content Model

Codegen via cf-content-types-generator creates full interfaces:

npx cf-content-types-generator \
  --spaceId YOUR_SPACE_ID \
  --token YOUR_CMA_TOKEN \
  --out ./src/types/contentful.d.ts

After that, importing import { IBlogPost } from './types/contentful' gives autocomplete and error protection. Saves 1–2 hours of manual TypeScript type definitions per project.

Step-by-Step Space Setup Guide

1. Requirements analysis — define content types, fields, validations (1 hour).
2. Create Space and environments — master, staging, dev via CLI (15 minutes).
3. Design and import Content Model — create JSON schema, import via CLI (30 minutes).
4. Type generation and documentation — codegen TypeScript, write readme (1 hour).

Full setup takes 1–2 days and reduces operational costs by 20–30%. Typical setup cost depends on scope. Savings on manual content migration can reach significant amounts.

What's Included in Our Work?

• Requirements analysis and Content Model design
• Space and environment creation (production, staging, dev)
• API token setup (CDA, Preview, CMA)
• Model import/export via CLI, CI/CD integration
• TypeScript type generation and integration
• Documentation for content managers

We guarantee: no extra fields, full validation at the CMS level, architecture ready to scale. We've been working with Contentful for over 5 years — during that time we've completed more than 30 projects of varying complexity. A typical project (4–6 Content Types, 2 locales, 2 environments) is set up in 1–2 days. The cost is calculated individually — depends on model complexity and automation requirements. Just get in touch — we'll prepare the architecture and a precise plan.

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.