The operating assumption is that you're still going to be doing dynamic work on the site but that it will all be client side.
You'll end up rendering huge JSON blobs with your public data in your markup for your client side JavaScript to do things with. Text is cheap. The client side does all of the heavy lifting but you'll probably need things like accurate time, which you can get by rendering pages using NGINX SSI module to render server time on pages. Obviously this won't stop some users from manipulating this information maliciously so you have to be careful what you use and where.
Naming this thing was always amusing to me though -- I'd been working with clients to switch from WP to essentially JAMstack years before it was ever named anything. Then suddenly I', in the JAMstack business.
The operating assumption is that you're still going to be doing dynamic work on the site but that it will all be client side.
You'll end up rendering huge JSON blobs with your public data in your markup for your client side JavaScript to do things with. Text is cheap. The client side does all of the heavy lifting but you'll probably need things like accurate time, which you can get by rendering pages using NGINX SSI module to render server time on pages. Obviously this won't stop some users from manipulating this information maliciously so you have to be careful what you use and where.
Naming this thing was always amusing to me though -- I'd been working with clients to switch from WP to essentially JAMstack years before it was ever named anything. Then suddenly I', in the JAMstack business.