Coding to SOLID software design principles makes custom Drupal code more maintainable. Take a look at how wrapped entities and the Typed Entity module can make code more SOLID.
All software companies rely on open source. FOSS needs maintainers to stay motivated. In this article, I propose an action item to improve the life of these volunteers with a small change.
Gabe, Wim and Mateu have tagged a stable release of the second version of the JSON:API module. This took a humongous amount of work and the maintainers are very excited to announce the 2.0 release.
Until now, each agency had their own Node.js back-end template that they used in every project. There has not been much collaboration. Contenta JS is meant to bring consistency and collaboration.
It may sound surprising to hear about brand consistency from a back-end developer. Nevertheless, brand consistency is a powerful trend that’s affecting how we architect content APIs.
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. How can we improve this situation?
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.
During the week of DrupalCon, we discussed some limitations of decoupling Drupal. We concluded that we need a reliable, flexible, and secure way for Drupal developers to decouple everything else.
The Subrequests module aggregates multiple requests of any kind into a single one, providing multiple responses in one single HTTP round-trip with zero server configuration.
