Mercè’s smart phone screen broke recently. Luckily I was able to get a screen replacement for her old OnePlus 3T. Putting everything back was a challenge in itself, but thanks to this YouTube I was able to succeed.

I have become more aware of my privacy and security of late. There hasn’t been any particular reason for that, but a gradual process of retaking control of my data. I try to discern what core value is moving me whenever I start feeling strongly about something. In this case, is the right of sanctuary. This is not my term, but rather something I learned reading The age of surveillance capitalism.

I am trying to find a viable replacement for twitter that people can subscribe to. For now I’ll stick to blog posts in the “notes” category.

Recently I had an incident with my Macbook Pro. My MagSafe connector was very hot when I got up. So hot that it gave me a blister in my finger.

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

Open source has won! It powers software everywhere. From automated irrigation software to supercomputer kernels. This has enabled the industry to evolve at a vertiginous pace that is changing the world.

I have been very vocal about the JSON:API module. I wrote articles, recorded videos, spoke at conferences, wrote extending software, and at some point I proposed to add JSON:API into Drupal core. Then Wim and Gabe joined the JSON:API team as part of their daily job. That meant that while they took care of most of issues in the JSON:API queue, I could attend the other API-First projects more successfully. I have not left the JSON:API project by any means, on the contrary I’m more involved than before. However, I have just transitioned my involvement to feature design and feature sign-off, sprinkled with the occasional development. Wim and Gabe have not only been very empathic and supportive with my situation, but they have also been taking a lot of ownership of the project. JSON:API is not my baby anymore, instead we now have joint custody of our JSON:API baby.

Though it seems like yesterday, Contenta CMS got the first stable release more than a year ago. In the meantime, Contenta CMS started using Media in core, improved Open API support, provided several fixes for the Schemata module, written and introduced JSON RPC, and made plans to transition to the Umami content model from Drupal core. A lot has happened behind the scenes.

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

It may sound surprising to hear about brand consistency from a back-end developer. This is traditionally a topic for UX and marketing experts. Nevertheless, brand consistency is a powerful trend that’s affecting how we architect content APIs.

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?