2 ms·
I personally don't think of Jamstack sites/applications as being 100% static. The core nature of the Jamstack is the ability to extend functionality with APIs/m
by el_dev_hell 6y ago
I personally don't think of Jamstack sites/applications as being 100% static. The core nature of the Jamstack is the ability to extend functionality with APIs/microservices (jamstack.org have a diagram example: https://d33wubrfki0l68.cloudfront.net/b7d16f7f3654fb8572360301e60d76df254a323e/385ec/img/svg/architecture.svg https://d33wubrfki0l68.cloudfront.net/b7d16f7f3654fb85723603...)
Having separate systems is (at least in my understanding and experience) a core design feature of the Jamstack.
Your question is valid. Why not go all the way to a CMS? If the author wants dynamic features AND doesn't want to build them himself, he might want to reconsider Wordpress.