Drupal Layout Builder Setup: Custom Sections & Layouts Guide

Editors often ask for the ability to drag-and-drop blocks without developer involvement. Drupal's built-in layout builder, available since version 8.7, provides a visual Drupal visual editing experience integrated into Drupal. This comprehensive Drupal Layout Builder setup guide will help you master the tool. We have configured it for dozens of projects and know how to get the most out of it without pain. Our certified Drupal developers guarantee a seamless setup. On one project with 500 pages, unique layouts increased response time by 40% — costing the client $10,000 in extra server costs — we had to redesign the approach. With proper caching, we cut costs by 50% and improved page load times by 20%.

How Layout Builder Solves Editor Problems

A typical situation: a marketer needs to quickly change a landing page structure — add a carousel, move a form capture. Without Layout Builder, you'd have to write a new content type or dig into Twig. With this tool, drag-and-drop is right on the page. Two modes: a common template for all content of a type and individual layouts for each node. The second mode is powerful but also a source of problems: each unique page generates extra database queries. Editor time savings on edits — up to 70%, equating to over $10,000 annually in content management costs.

Step-by-Step Setup of Layout Builder

1. Install modules via Drush:

   drush en layout_builder layout_discovery -y
   drush cr
   

2. In the admin, go to Structure → Content Types → select the type → Manage display. Click "Enable Layout Builder".
3. Choose mode: Defaults (one layout for all nodes) or "Allow each content item to have its layout customized" (unique layout per node).
4. Configure the default layout: add sections, blocks, fields. This is where you add Drupal sections and blocks.
5. Restrict available blocks using the Layout Builder Restrictions module to enforce Drupal block restrictions (see below).

Setup for a Content Type

After enabling Layout Builder, open the "Manage layout" tab. You'll see an empty grid. Add a section (e.g., one column) and place blocks — node fields, custom blocks, views. For content types with hundreds of nodes, use only Defaults mode; individual layouts heavily load the database.

How to Create a Custom Section?

Sections are registered via a layout plugin. Example: Hero with Sidebar. You can create custom sections in Drupal with ease.

// custom_layouts/layouts/my_hero/my_hero.php
namespace Drupal\custom_layouts\Plugin\Layout;

use Drupal\Core\Layout\LayoutDefault;

/**
 * @Layout(
 *   id = "my_hero_layout",
 *   label = @Translation("Hero + Sidebar"),
 *   category = @Translation("Custom"),
 *   template = "layouts/my-hero",
 *   regions = {
 *     "hero" = { "label" = @Translation("Hero Area") },
 *     "sidebar" = { "label" = @Translation("Sidebar") }
 *   }
 * )
 */
class HeroSidebarLayout extends LayoutDefault {}

Twig template layouts/my-hero.html.twig:

<div class="layout-hero-sidebar">
    <div class="layout-hero-sidebar__hero">
        {{ content.hero }}
    </div>
    <aside class="layout-hero-sidebar__sidebar">
        {{ content.sidebar }}
    </aside>
</div>

After creation, clear cache — the section will appear in the list when editing.

Restricting Blocks with Layout Builder Restrictions

Without this module, an editor could insert a block that breaks the layout. The Layout Builder Restrictions module allows you to specify which blocks are available in each section per content type. Install:

composer require drupal/layout_builder_restrictions
drush en layout_builder_restrictions -y

Configure: Structure → [content type] → Manage display → Layout Builder → Restrictions. There, set a whitelist of blocks for each section.

Why Layout Builder Might Be Slow?

Drupal Layout Builder performance can be optimized with the right caching. Main causes:

• Blob data of unique layouts — parsed each time.
• Lack of layout caching — repeated DB queries.
• Many blocks on a page (more than 20).

Also, for content types with more than 50 nodes, avoid individual layouts. Proper caching improved performance by 3x on one of our projects. The Drupal Performance Documentation emphasizes the importance of caching for Layout Builder.

Layout Builder vs Paragraphs (Comparison)

Layout Builder is more convenient for marketers — visual drag-and-drop. It is up to 3x more efficient than Paragraphs for creating landing pages. Paragraphs is more convenient for developers — clean data structure, predictable template output, good API support. Choice depends on the task: if maximum flexibility for editors without code is needed — Layout Builder; if the project is complex or headless — Paragraphs.

What's Included in Setup

Our Drupal Layout Builder setup service with a proven track record includes:

Timeline

Layout Builder setup for 2-3 content types with custom sections — from 3 to 5 business days. Timeline may vary depending on layout complexity and integration with other modules. Typical projects cost $2,000-$5,000, ensuring a high return on investment.

Typical Errors and How to Avoid Them

• Not enabling Restrictions — editor breaks layout with unsuitable blocks. Solution: always configure Restrictions.
• Giving individual layouts to all nodes — kills performance. Solution: give individual layouts only to content types with few nodes (up to 50).
• Ignoring caching — Layout Builder generates many queries. Solution: enable BigPipe and Dynamic Page Cache.

If you need help setting up Layout Builder or want to avoid typical mistakes, contact us. Our engineers have over 5 years of experience with Drupal and have configured Layout Builder for 40+ projects. Get a free consultation on caching and custom sections. We guarantee a successful implementation within the agreed timeline.

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.