Drupal

Drupal offers multiple ways to build flexible, editor-friendly pages. Two of the most powerful tools are Paragraphs and Layout Builder. Both solve different problems, and understanding when to use which — or how to combine them — is key to building scalable Drupal sites.

This article explains the differences, strengths, weaknesses, and best practices for using Paragraphs and Layout Builder in real-world Drupal projects.

Impostor syndrome is often described simply as “a person doubting themselves.” For professionals — developers, architects, engineers — this explanation is too simplistic.

Interestingly, impostor syndrome frequently affects highly skilled specialists, not beginners. These are people with experience, proven results, and systematic thinking.

So the real question is: does strong knowledge of fundamentals prevent impostor syndrome, or is it mainly a psychological phenomenon?

Drupal 11.4 introduces a major improvement in entity loading performance. If you’re a developer or site builder, this change could significantly reduce the number of database queries on your site and speed up page loads.

What Are Single Cardinality Fields?

Single cardinality fields are fields that can only have one value per entity. Common examples include:

When working with Drupal entities, many developers assume that access control “just works.” This is only partially true. Drupal does provide a robust access system — but only when you interact with entities using the Entity API.

However, if you run raw SQL queries, write custom EntityQuery logic, or misconfigure Views, you can accidentally expose sensitive content to unauthorized users.

Drupal has supported multiple database engines for many years, including both MySQL and PostgreSQL. While MySQL remains the de-facto standard across most Drupal installations, more developers today are exploring PostgreSQL as an alternative — especially those who already rely on it for enterprise applications and microservices.

But is PostgreSQL a practical choice for a real Drupal project in 2025?
This article breaks down everything you need to know.

Automatic Entity Linking, Smart Suggestions, and Linkit-style UX — Now in Core

Drupal 11.3 introduces a long-awaited feature: native support for linking to entities directly from CKEditor 5, powered by a new Entity Links text filter and a built-in Entity Link Suggestions Plugin.

If you ever used Linkit, this will feel very familiar — but now it’s supported natively by Drupal core and integrated with the new Link Target Handlers architecture.

How Drupal Finally Solved URL Generation for CKEditor 5

Drupal 11.3 introduces a major improvement to how URLs are generated for internal entities, especially when working inside CKEditor 5. The new Entity Link Target system allows entity types to declare exactly how their hyperlink should be generated — whether they represent content, files, media, or even virtual objects like menu links.

This article goes far beyond the official change record, providing a full technical deep dive with flow diagrams, architectural notes, and production-ready examples.

With Drupal 11.3, the way Twig templates access object methods has received a significant upgrade. The new TwigAllowed attribute provides developers and themers with a more secure and explicit method to control which object methods can be called from Twig.

The Problem with Legacy Method Access

Before Drupal 11.3, Twig templates could automatically access certain methods of objects based on magic prefixes like get, is, and has. For example:

Drupal 11.3 introduces several important improvements to the validation system, making it more flexible and fully compatible with Symfony. In this article, we’ll cover three key updates:

1. CompositeConstraintInterface – the interface for composite constraints.