Embracing the Jamstack approach

Background

For the longest time, JavaScript has been a source of anxiety for me. I never truly comprehended the language, but over the past year, I've dedicated a substantial amount of time to learning it. While I wouldn't call myself an expert just yet, I've made significant progress. In the past, my focus was mainly on HTML, CSS, and some basic jQuery, which I still cherish.

In my professional journey, I've primarily engaged in front-end development within the WordPress and Drupal ecosystems. While these content management systems have their merits, I encountered challenges in certain aspects of front-end development, such as optimizing performance and images. Additionally, the ongoing tasks of keeping plugins and modules secure and up-to-date became time-consuming and somewhat tedious. I began to wonder if there was a way to break free from these constraints.

Embracing the Jamstack approach

The Jamstack approach immediately caught my attention when I first learned about it. It promised a smoother and more flexible developer experience, while also delivering secure and high-performance websites right from the start. The prospect of reducing backend complexity was particularly appealing to me:

Jamstack is revolutionising the way we think about workflow by providing a simpler developer experience, better performance, lower cost and greater scalability.

Source: https://jamstack.wtf/

Building websites has never been more enjoyable, rewarding, or inspiring. The very site you are currently visiting was originally constructed using Gatsby for static site generation, Strapi for content management, and deployed on Netlify . Today, the site is powered by Next.js with content managed in Sanity , and is hosted on Vercel .