With all the CMSs & headless CMSs available, JAMstack might seem overly complicated to non-techies and the developer communities who can still clearly remember the 80s & 90s. Regardless of this, it continues to grow in popularity, in 2019 0,4% of web pages was built on Jamstack, but in 2020 that number more than doubled and 2021 looks likely to more than triple 2020 numbers.

If you are currently confused and don’t have a clue what I am talking about, I will explain. +- 8 years ago a new approach was developed to build websites and mobile applications in a static way instead of a dynamic way, but with dynamic capabilities. Still confused …. When you open a WordPress website, you will notice the page sections opening and displaying at different stages and it usually takes a really a long time, sometimes up to 30 seconds to load fully. This is due to the page being built and put together as it is loaded. Static site generators have the individual website pages ‘pre-built and ready to display in the background, which is why they load so quickly, as it’s only rendering the pre-built HTML page. JAMstack is a framework that combines the static site generator with the on-page dynamic ability to change as well.

JavaScript JavaScript is responsible for the dynamic workflow during the request/response. It’s what makes a site alive, and frameworks like React.js, Gatsby & Next.js are in charge of it.

APIs APIs provide HTML pages with added functions, such as content management, search, authorization, payments, and beyond.

Markup Markup in JAMstack is all the visible content on a website, a “collection” of pre-rendered HTML files. As discussed earlier all of this content is pre-built and waiting to be rendered.

So then the million-dollar question – Why change to JAMstack? Performance Security & Stability Scalability Cost Flexibility Pure Front-end Focus

Give it a try, you will not regret it!