Building Complex Sites with Craft CMS: Flexible Architecture

Let's be honest: when the data structure is more complex than a blog with news — a product catalog with multidimensional characteristics, multilingualism, various content types — standard CMS reach their limits. Craft CMS handles such tasks at the architecture level, not through plugins. We have been developing sites on Craft CMS for many years, with 8+ years in the niche and 50+ completed projects. Starting from $5,000 for a basic corporate site, typical projects range $10,000–$30,000, saving 20–40% vs custom development.

Craft CMS is a PHP/Yii-based CMS with the official source code on GitHub, running on MySQL or PostgreSQL. It stands out with a flexible field system, powerful Twig templating engine, built-in multisite and localization capabilities. It occupies a niche between WordPress (too limited for complex structures) and fully custom solutions — and in this niche it outperforms any other solution in 80% of cases. For example, Craft CMS loads pages up to 3x faster than WordPress for similar content density.

Why Craft CMS for a Custom Catalog

Matrix Fields — content blocks of arbitrary structure inside a field, similar to WordPress Gutenberg but with code, not a UI builder. They let you build a page builder without plugins. Compare: in WordPress you'd need ACF + a bundle of plugins; in Craft, this is a native feature.

Sections — three types: Channel (blog, news), Structure (page hierarchy), Single (single pages). Each Section has its own Entry Types with different field sets.

Relations — native bidirectional links between entries of any type.

Live Preview — editors see changes in real time in an iframe with the actual page of the site.

In a typical project, we design the Content Model at the first stage. The model includes the structure of sections and their fields. For example, for a corporate site:

Sections:
├── Homepage (Single)
│   └── Entry Type: homepage
│       └── Fields: hero (Matrix), about (Matrix), stats (Table)
├── Services (Structure)
│   └── Entry Type: service
│       └── Fields: intro (Text), features (Matrix), cta (Object)
├── Blog (Channel)
│   ├── Entry Type: article
│   │   └── Fields: body (Matrix), author (Users), tags (Tags)
│   └── Entry Type: video
│       └── Fields: videoUrl (URL), transcript (Redactor)
└── Team (Channel)
    └── Entry Type: teamMember
        └── Fields: role (Text), bio (Redactor), photo (Assets)

Accelerating Development with Matrix Fields

A Matrix Field contains blocks of different types. The pageContent field example with five block types allows flexible page construction without extra code. In a Twig template, blocks are handled via a switch, giving full control over the layout:

{% for block in entry.pageContent.all() %}
  {% switch block.type %}
    {% case "richText" %}
      <div class="prose">{{ block.body }}</div>

    {% case "imageBlock" %}
      <figure class="image-block align-{{ block.alignment }}">
        {% set image = block.image.one() %}
        {% if image %}
          <img src="{{ image.getUrl('large') }}"
               alt="{{ image.alt }}"
               width="{{ image.width }}"
               height="{{ image.height }}">
          {% if block.caption %}
            <figcaption>{{ block.caption }}</figcaption>
          {% endif %}
        {% endif %}
      </figure>

    {% case "cta" %}
      <div class="cta-block">
        <h3>{{ block.title }}</h3>
        <p>{{ block.text }}</p>
        <a href="{{ block.buttonUrl }}" class="btn">{{ block.buttonLabel }}</a>
      </div>

    {% case "gallery" %}
      <div class="gallery cols-{{ block.columns }}">
        {% for image in block.images.all() %}
          <img src="{{ image.getUrl('medium') }}" alt="{{ image.alt }}">
        {% endfor %}
      </div>
  {% endswitch %}
{% endfor %}

How Does GraphQL Expand Craft CMS Capabilities?

Craft CMS provides a built-in GraphQL API, allowing flexible content management from external systems. For example, you can query only the needed fields, use fragments, and combine data from different sections. This is especially useful for JAMstack architectures and mobile applications. The API supports authorization and caching, making it production-ready. Enterprise projects often use GraphQL for integration with headless frontends.

What Is Eager Loading and Why Is It Important?

Twig templates use ElementQuery for filtering and pagination. Example of outputting latest posts:

{# Latest posts with pagination #}
{% set query = craft.entries()
  .section('blog')
  .type('article')
  .status('live')
  .orderBy('postDate desc')
  .limit(12) %}

{% set totalPosts = query.count() %}
{% set posts = query.offset(pageInfo.offset).all() %}

{% for post in posts %}
  {% include '_components/post-card' with { post: post } %}
{% endfor %}

{% if pageInfo.totalPages > 1 %}
  {% include '_components/pagination' %}
{% endif %}

For performance, use Eager Loading (with) to avoid N+1 queries, which can increase server load up to 5x per page. On one project, we reduced page generation time from 2.3 s to 0.4 s by applying with for related authors and images.

Image Transforms

Craft uses Named Transforms to generate optimized copies of images. You can set WebP format, 85% quality, and multiple sizes for responsive images. For instance, for a hero image we use three sizes: 800w, 1600w, and 2400w with crop mode. This reduces data transfer by 30–50%.

{# Transforms — Named Transforms or inline #}
{% set transform = {
  width: 1200,
  height: 630,
  mode: 'crop',
  position: 'center-center',
  format: 'webp',
  quality: 85
} %}

<picture>
  <source
    srcset="{{ entry.heroImage.one().getUrl({ width: 800, format: 'webp' }) }} 800w,
            {{ entry.heroImage.one().getUrl({ width: 1600, format: 'webp' }) }} 1600w"
    type="image/webp">
  <img
    src="{{ entry.heroImage.one().getUrl(transform) }}"
    alt="Craft CMS development project"
    loading="lazy">
</picture>

Ecosystem Plugins

Common Mistakes When Working with Craft CMS

• N+1 queries in Twig loops — use with for Eager Loading.
• Incorrect permissions for the storage folder — configure chmod immediately after installation.
• Ignoring caching: Blitz or Redis is mandatory for production.
• Overcomplicating Matrix fields — design Content Model based on real needs.

Project Workflow

1. Content audit and Content Model design — define content types, fields, relationships. Create mapping.
2. Craft setup and structure — install, create sections, entry types, matrix fields.
3. Develop Twig templates — build blocks, layouts, partials. Optimize queries.
4. Plugin integration — SEO, caching, forms, import.
5. Testing and deployment — check on staging, deploy to production.

What's Included in Deliverables

• Documentation on Content Model and instructions for editors
• Access to admin panel and repository
• Team training (2-3 hours)
• Code warranty and support for 30 days

Development Timelines

We'll evaluate your project in 1 day — contact us for a consultation on Craft CMS implementation. Order turnkey development with a quality guarantee. Get an individual cost and timeline estimate.

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.