May 26, 2019
I recently switched to using JAMStack principles for this website, and so far I’m liking it, although it does make things a bit more complicated.
What is JAMStack?
It’s a modern web development architecture based on:
- A | reusable APIs
- M | Prebuilt Markup
— From jamstack.org
There are a few benefits to this approach, but for me the biggest is better performance (aka faster websites). Actually one of the implicit requirements of JAMStack seems to be using a CDN to deliver the site content and assets, and I really feel like they should go ahead and throw “CDN” into the acronmym, maybe make it JAMStaCk or something?
Of course there are a few drawbacks as well. For one thing, JAMStack is touted as a more developer-friendly approach, but at the same time it seems less content-author-friendly and may be difficult to integrate at organizations where the content authors are not technical.