All Posts

The first post of this series focused on setting up easily a multilingual Drupal and React environment for a museum Audioguide web app. This one describes the steps to achieve a MVP that displays a list and a detail page of Audio contents, so we have the opportunity to cover several basic concepts under React : Components (add from a package repository, inherit, compose, create), Routes (default route and wildcard), Fetch to consume Rest, Localization via React Intl.

The goal of this serie of posts is to achieve quickly a simple museum Audioguide web app based on a React isomorphic boilerplate with a Drupal 8 backend that uses the latest standards. The web app will be fully decoupled by being hosted on another domain than the Drupal one. As a real world case, we want it to be fully multilingual. This is the first post of a serie of 3. This first one focuses on having a Drupal and React setup that meets our requirements. The second one will define a MVP that will just fetch the audioguides list and a detail view (GET operation), the last one will then add extra features like getting user feedback (POST operation).

Just bookmarking here the amazing documentation that was produced during the Dev Days.

Many session were oriented towards coding attitude. It looks like we now have the time to let the technical specs of Drupal 8 a bit behind and focus on sharing developer experience.

The scope of this article is to illustrate the responsibilities of several tools and techniques used in the Drupal ecosystem (Composer, Drupal Console, Drush, Configuration management) to achieve quickly a simple custom Google Maps use case: an Address field will be defined on a content type. We want the address to be geocoded automatically for each node on save to display a Google Map. The display of the map will be achieved by a custom module to allow further extension.

Things have evolved quickly, we have now a huge bunch of helpers since 8.2.x in core for Drupal to Drupal migration: Migrate, Migrate Drupal and Migrate Drupal UI.

Summer was inspiring! A really pragmatic talk on how to apply Scrum from @dasjo at the Drupal Dev Days Milan acted as a kick-starter and we decided to apply it in our small Drupal dev team at Tilt Factory.

The l() function is deprecated in Drupal 8+, here is how to implement it.

The use case is to sort a list of users by job title, where job title is a term reference to a dedicated vocabulary. The sort is done by the job title term weight (defined via the vocabulary list).