Drupal 11

Drupal 11.5 introduces Drupal 11.5 library ordering, a new feature that allows libraries to be loaded before or after another library without declaring a dependency. The new before and after keys make asset ordering cleaner, reduce unnecessary dependencies, and provide a more maintainable way to control JavaScript and CSS loading.

Drupal 11.4 brings one of the most significant developer experience improvements in recent years: a built-in command-line interface that can discover commands provided by Drupal modules.

Until now, Drupal Core included a limited CLI (core/scripts/drupal) that only supported a handful of core commands. Most developers relied entirely on Drush for command-line workflows.

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.

With the release of Drupal 11.3.x, the Views API has received an important change:
the long-standing access callback key used in Views handler definitions has been deprecated.

This update impacts module developers, site builders, and anyone defining custom Views handlers.

🚨 What Exactly Has Been Deprecated?

In earlier versions of Drupal, you could define access logic for a Views handler directly inside views_data():

🚀 Introduction

Drupal 11.3.0 brings a powerful update for themers and front-end developers:
themes can now implement hooks using Object-Oriented Programming (OOP) with the #[Hook()] attribute — just like modules have been able to do since Drupal 11.

This means no more long procedural functions in template.php.
Instead, you can organize your logic cleanly in classes inside the theme’s src/Hook directory.