Ah… we all got used to it: opening a view, clicking Advanced, and suddenly diving into a whole world of relationships, contextual filters, and other “special” settings.
For some, it was a ritual — like opening an old book to a favorite page. For others — a minor annoyance, an extra click every time.

With Drupal 11, that little movement is now a thing of the past.

As Drupal continues its evolution toward a cleaner, service-oriented architecture, developers must adapt to API changes that improve flexibility and maintainability. One such change in Drupal 11.3.0 is the deprecation of node_type_get_names(), a function long used to retrieve node type labels.

This article walks you through:

With the release of Drupal 11.2.5, a subtle but important change has landed that affects how sites interact with Composer and rsync via the Package Manager. If you’ve been relying on configuration to define executable paths, it’s time to refactor.

🚫 What Changed?

For security reasons, Drupal core has removed the ability to configure paths to Composer and rsync via configuration files. This means:

As Drupal continues to evolve, version 11.3.0 brings a significant shift in how developers interact with node revisions. The NodeStorage class, once a go-to for revision-related operations, has seen most of its methods deprecated. This change is part of a broader effort to streamline the API and encourage the use of entity queries.

Let’s break down what’s changed, why it matters, and how to adapt your code.

🔧 What’s Deprecated?

The following methods in Drupal\node\NodeStorage are now deprecated:

With the release of Drupal 11.3, the new DrupalInstalled class has been introduced for site builders and developers, simplifying cache management and container rebuilds.

What’s New

The Drupal Scaffold Composer plugin now generates a file:

Introduction:

Frontend development used to rely on HTML and CSS files connected manually. Today, developers use modern tools to generate up-to-date, browser-compatible CSS.

Tailwind CSS is a modern utility-first CSS framework, perfect for building custom themes in Drupal 10. It allows developers to create unique designs quickly and efficiently without writing excessive CSS.

Drupal is constantly evolving, and keeping up with changes in its core APIs is crucial for module developers. One important update in Drupal 11.3 affects how developers work with the ImageFactory service and its toolkit. In this article, we’ll explain the change, why it matters, and provide a clear example of how to update your ImageFactory subclasses to use the getToolkitId() method safely.

Understanding Revisions in Drupal

In Drupal, revisions (or versions of content) allow you to track changes over time. Every time an editor saves content, a new revision can be created.

Example:

• An editor publishes an article → Revision #1 is created (default).
• A week later, the editor updates the article → Revision #2 is created (becomes default).
• The database keeps both revisions, but visitors see only the default version.

Revisions let you:

If you’ve ever worked on theming in Drupal, you know the pain: enabling Twig debug or disabling caches usually required digging into services.yml, updating settings.php, or installing contrib modules.

With Drupal 10.1, this process has been simplified. A new Development settings page in core now allows developers to manage these features directly from the admin UI.

👉 Navigate to: Configuration → Development settings