Please excuse my ignorance, what is JAMstack? I couldn't find an explanation on the landing page or the README.md.
Some "dynamic" server side content was also easily included in a cronjob. That way I fetched the Twitter feed of a few accounts and rendered this into the static HTML.
I did it, because it was really fast to build, could scale, development and deployment was easy for the HTML, etc.
What I didn't had at the time was FaaS and I think the architecture could benefit from this. I had Docker containers running the API and the reverse proxy needed to do some routing, so I still had a server running, but I didn't need a database. I had to teach the marketing department how to write Markdown in GitLab editors, though.
so, I guess that's good. I was afraid the M was going to be Meteor.