At WeKnow, we've been using Gatsby with Drupal for projects lately as our decouple strategy.
We decided to use the same approach for our personal blog sites, and the latest version of this blog was launched using GatsbyJS. What does this mean, We are no longer using Drupal?
Yes, for this site we are no longer using the Drupal theme layer, Twig, theme preprocessing, and the always loved/hated render array. All the frontend was done using ReactJS a modern JS framework.
And no, because Drupal is still used as the backend taking advantage of the JSON-API contributed module.
Well after running an audit using lighthouse we obtain the following results.
No custom performance tasks are done yet, this is the out-of-the-box performance result by building the site using GatsbyJS.
gatsby-transformer-remark
plugin.gatsby-transformer-sharp
plugin .Gatsby is taking the world by storm and the JAMstack is here to stay. Join me at my BADCamp session How to keep Drupal relevant in the Git-based and API-driven CMS era, to learn what can we do to keep Drupal relevant and this new era to find out how we solve all those challenges and to learn more about this topic and understand how to decouple the "Content Management" from the “Production Environment".