This is a re-post of the article I wrote for the Lullabot blog.

As part of the Decoupled Hard Problems series, in this fourth article, I’ll discuss some of the challenges surrounding routing, custom paths and URL aliases in decoupled projects. 

This is a re-post of the article I wrote for the Lullabot blog.

The Schemata module is our best approach so far in order to provide schemas for our API resources. Unfortunately, this solution is often not good enough. That is because the serialization component in Drupal is so flexible that we can’t anticipate the final form our API responses will take, meaning the schema that our consumers depend on might be inaccurate. How can we improve this situation?

This is a re-post of the article I wrote for the Lullabot blog.

As part of the API-First Drupal initiative, and the Contenta CMS community effort, we have come up with a solution for using Drupal image styles in a decoupled setup. Here is an overview of the problems we sought to solve:

This is a re-post of the article I wrote for the Lullabot blog.

At this point, you may have read several DrupalCon retrospectives. You probably know that the best part of DrupalCon is the community aspect. During his keynote, Steve Francia, made sure to highlight how extraordinary the Drupal community is in this regard.

Contenta is a Drupal distribution that gives you modern API capabilities out-of-the-box with JSON API, which amongst other features allows you to fetch nested resources in one request, and plans to include a similar GraphQL service soon. It’s ready to feed content to your JavaScript-powered website, phone app, TV, or even the mythical fridge application.

This is a re-post of the article I wrote for the Lullabot blog.

Design patterns

Software design patterns are general and reusable software design solutions to a defined problem. They were popularized in 1994 by the “Gang of Four” after their book Design Patterns: Elements of Reusable Object-Oriented Software.