Skip to main content

Giving the JAMstack a go

Published: - 2 min read

A brief summary of how this portfolio was built using the JAMstack approach.

I've always been afraid of JavaScript, have never really understood or learned the language properly. Anyhow, the last year I've spent a lot of time learning JavaScript. Although I'm still far from an expert, I'd say I've improved dramatically. While earlier I almost only wrote HTML & CSS (which I still do and love) and some basic jQuery, I tried to get a hang of vanilla JavaScript and ES6 to actually build and deploy my own portfolio using Gatsby and the JAMstack approach.

Background

I've been doing front end development in WordPress and Drupal. Although I've enjoyed working with both CMS:es, some aspects of the front-end development have been challenging and complicated – things like performance- and image-optimisation for example. Furthermore, keeping plugins and modules secure and up to date to make sure that sites are up and running, it is not only time consuming but also one of the less inspiring parts of the job. What if I would be able to get away from that?

The JAMstack approach

The JAMstack approach immediately caught my attention once I read about it. Smooth and flexible developer experience, being able to deliver secure, fast sites right out of the box while reducing the backend complexity is pretty much all I've ever wanted:

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 a website has never been more fun, rewarding and inspiring. The site you're currently visiting is built using Gatsby for static site generation, with Strapi as headless CMS, Heroku (PaaS) for hosting Strapi and hosted on Netlify.

Last updated: