Generating static content and saving to a CDN is just a really inefficient way of caching dynamic content.
Disagree; updating your content when (and only when) it changes sounds a lot more efficient than dynamically generating whenever it's requested and then putting a cache in front of that.
Witch static webpage generators, your non-technical editors get all the benefits from editing flat-text files with markdown and git, instead of relying on a sys-admin to watch the state of the database for them.
The JAMstack pattern allows storing static content as editable flat-text files, and dynamic comments in a database without mudding everything within the same CMS code; it's just a better separation of concerns.
Generating non-changing content statically for speed and SEO beforehand and using dynamic components where necessary doesn't seem like a bad trade-off.
I guess fully dynamic server-side rendering (with a cache in front of it) would be the easiest to manage, but not hip anymore I assume.
Tied to community building, is there a Jamstack solution for forums? This is a very similar use case to comments.