Planet Drupal

Add a patch with Composer for a core or contributed Drupal project.

Gatsby and Next are both based on React and become more and more adopted, far beyond the Drupal sphere. Choosing a decoupled solution comes with a resource cost though (budget, team-wise), and might not be the right fit for every project. Working with these solutions is still time well invested.

Here is a really simple way to handle synonyms (or extra keywords) using Search API out of the box with a database server and no custom code involved. Use case: we want to do a full text search based on synonyms that does not appear on the frontend. These ones should be set from the Tags vocabulary. The method should be flexible regarding translations, available for content editors and easily generalizable.

The planet Drupal has now some data visualization based on Three.js an D3.js for the following questions: where are the Drupal peeps, how are they contributing, which languages are they talking, what are they working on? Get the answers on https://drupalearth.org

While working on migrations from Drupal 7 to 8 it could be necessary to convert tokens from formatted text fields + get an idea of how many of them are in the database for estimation, e.g. to see if it is possible to rely on Token Filter or if there are custom tokens/filters.

This article will explain how to use migration templates with a CSV that contains the Paragraphs data on several lines.

Here is a pretty simple way to maintain the hook_help() of a Drupal project, straight from the readme file. Markdown is preferred here to .txt so it can be reused on a GitHub, GitLab, ... repository as well.

CiviCRM is an old Drupal 7 friend and its relationships with Drupal 8 are in a pretty good way. Let's make them meet the Composer template for Drupal projects, a widespread setup that stores the vendor directory outside of the docroot. Lando will host the party by spinning up a local environment, however this method should be generalizable with any other development environment.

A walkthrough to join the dots between two posts about setting up Lando for Drupal and Solr for Drupal with Search API, and also a good opportunity to cover all the steps to spin up an evaluation or development environment for this setup. Lando comes with the great benefit for a team to share the server configuration alongside the project, so we have a predictable environment to deploy in production and do not add configuration maintenance overhead on the team, especially in the case of more advanced setup like Solr, Varnish, decoupled setup, ...

A few inspiring links related to the Decoupled Drupal Days.