Component Layout with Matrix Fields in Craft CMS: Configuration Guide

Developers often encounter pitfalls with Matrix Field in Craft CMS: either N+1 queries kill the server, or editors ask for 'one more block type'. In one project, a client's 'About' page had 25 blocks, each with an image. Page load took 8 seconds due to 25 separate media queries. After properly configuring eager loading, the time dropped to 1.2 seconds — a 6.7x improvement. With over 50 Craft projects, we've refined an approach where Matrix neither slows down nor frustrates the team.

How to Design Blocks to Avoid Redesigns

In a typical corporate site, the pageBody field contains 6–10 block types. Each block is a micro-structure: text, image, link, quote, code, stats. It's critical to plan the set of fields — adding a field later is harder than removing one. The optimal landing page structure:

pageBody (Matrix)
├── hero
│   ├── heading, subheading, backgroundImage, ctaButton
├── richTextContent
│   └── content (Redactor)
├── imageWithCaption
│   ├── image, caption, alignment
├── twoColumns
│   ├── leftContent, rightContent (Redactor)
├── testimonial
│   ├── quote, author, role, avatar
├── stats
│   └── items (Table field)
├── ctaBanner
│   ├── heading, text, buttonLabel, buttonUrl
└── codeSnippet
    ├── language, code

Use Table fields for lists (stats, pricing) — they are faster than nested Matrix and easier to cache.

Twig Rendering: switch vs include vs component

Most projects use {% switch %} inside a loop — reliable and readable. But with 10+ blocks, the template becomes bulky. An alternative is to extract each block into a separate include. This simplifies maintenance but is marginally slower due to multiple include calls. The optimal approach renders blocks via a component approach with fragment caching.

In our experience, pages with 15+ blocks gain 40–50 ms by including cache tags.

Why N+1 Destroys Performance and How to Avoid It

Without eager loading, each block with an Assets field generates a separate query. For example, an image block searches for the image, a testimonial block for the avatar. If the page has 10 blocks, you get 10 DB queries plus the block list query. The solution is a single with() call: {% set blocks = entry.pageBody.with(['image', 'avatar', 'backgroundImage']).all() %}.

For blocks containing nested Matrix (e.g., tabs with inner content), use .with()['subMatrixField.childField'] — Craft supports deep eager loading. Full details in the official Craft CMS documentation.

What to Do If Matrix Slows the Control Panel

A Matrix with 50+ blocks in CP is a common nightmare. The reason: each block renders its fields. The solution is to fragment the matrix into multiple fields: separate Matrix for 'header', 'body', and 'footer'. Alternatively, use Neo Field by McDowell — an analog supporting nesting, though at $99 cost.

Tool Selection: When to Use Matrix, Neo, Table

Matrix is best for 80% of projects. Neo is worth it only for more than two levels of nesting. Table and SuperTable are for tabular data.

Block Caching Strategies for Matrix

Matrix blocks break page caching without a strategy. The solution is to cache each block separately with tags. In Twig:

{% cache globally using key 'block-' ~ block.id tags 'matrixBlock:' ~ block.id %}
  {% include 'matrix/_' ~ block.type.handle %}
{% endcache %}

When a block is modified, Craft invalidates only its cache. For static blocks (richText), cache for a day; for media, for an hour.

pageBody (Matrix):
- hero (heading, subheading, backgroundImage, ctaButton)
- richTextContent (content Redactor)
- imageWithCaption (image, caption, alignment)
- twoColumns (leftContent, rightContent Redactor)
- testimonial (quote, author, role, avatar)
- stats (items Table field)
- ctaBanner (heading, text, buttonLabel, buttonUrl)
- codeSnippet (language, code)

What You Get from Proper Matrix Configuration

After completion, you receive:

• A configured Matrix Field with 5–8 block types.
• Twig templates supporting responsive layouts (mobile version determined via craft.app.request.isMobile if needed).
• Eager loading configured for all relational fields (Assets, Categories, Entries).
• Documentation on adding new blocks and editor training (1 hour).
• Performance guarantee: page load with 10 blocks under 1.5 seconds.

Common Mistakes and Solutions

When to Avoid Matrix

Matrix is inconvenient for:

• Sites with one content type (blog) — Rich Text suffices.
• Sites with a rigid grid (e.g., portfolio) — better structured via Entry Type.
• High-load projects (millions of blocks) — Matrix scales poorly; consider Headless CMS or custom solutions.

Otherwise, it is the standard Craft CMS tool, used in 90% of our projects. Our team has 5+ years and 50+ Craft projects, ensuring optimal Matrix configuration. To speed up your project, get a free consultation.

Configuring a Matrix with 5–8 block types and templates takes 2–4 days. Cost depends on the number of types and design complexity, determined after analysis.

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.