#Drupal Planet

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

Introduction:
When working on Drupal projects, installing and updating dependencies is a crucial step. All external modules and libraries are managed using Composer. The --prefer-dist option helps speed up this process and ensures more stable installations.

What --prefer-dist Does

Composer can fetch packages in two ways:

The Tale of the Retired Numbers in Drupal

Once upon a time in the cozy world of Drupal, there lived three humble numbers: 0, 1, and 2.
They had an important job — helping developers set the preview mode for content types.

When working with Laravel and Drupal, I noticed something striking: defining web routes feels vastly different between the two. Laravel offers what feels like an endless number of ways to register routes, while Drupal provides a single, standardized approach. Let me break this down.

1. How Laravel Defines Web Routes

In Laravel, routes for the web layer are typically defined in the routes/web.php file. But because of Laravel’s flexibility, there are many ways and places to register them: