Read on Twitter
A bit late in the day, but my learning resources for the day today are about Jamstack. The JAM stands for JavaScript, APIs and Markup.
I'm still not convinced that this isn't just a buzzword for static site generators, but it seems to be more focussed on the development philosophy of only serving static HTML from a CDN.
By baking your data into your pages at compile / publish time rather than when the page is served, and frequently rebuilding and redeploying pages on content changes, most 'dynamic' content can be served statically with all of the associated SEO and performance benefits.
So without further ado, the resources:
New to JAMstack? Everything You Need to Know to Get Started - https://snipcart.com/blog/jamstack - A (slightly salesy) beginners guide to what the Jamstack is, and what it's for. This post identifies some popular technologies that you can use for each component of the stack.
http://Jamstack.org - https://jamstack.org/ - This site seems to serve as a general hub for information about the Jamstack concept and has a lot of examples of sites that use the stack.
JAMstack Course - Build websites that are simpler, faster, and more secure - - A detailed video tutorial from @freeCodeCamp and @philhawksworth on how to get started building a website using the Jamstack concepts.
This tutorial comes with example repositories so you can dive in without having to start from scratch.
My thoughts on Jamstack, from what I've learned so far, is that the best part of the concept is the value of rendering more things at build time rather than at request time.
The worst/most shaky part is the handwavy approach to 'oh you don't need servers any more, just use APIs'. For a complex dynamic system, of course you'll need something to serve those APIs - whether that's a server or a Lambda function is somewhat beside the point.
I imagine that a complex web application would actually use a combination of pre-rendered resources for things that change at the behest of publishers (e.g. blogs, products), and dynamic resources for things that change at the behest of users (e.g. messages, user interactions).
I'd like to see a less evangelistic description of the concept, which provides a more honest assessment of what the toolchain is good for, and what it's not - if someone knows of a good resource for this, please let me know!
