I think this is more a question of how you want to create and store your content and templates, like whether they exist as a bunch of Markdown files, database e

I think this is more a question of how you want to create and store your content and templates, like whether they exist as a bunch of Markdown files, database entries, a third-party API, etc. They're typically made to work in some sort of toolchain or ecosystem. For example, if you're working in the React world, Next.js can actually output static HTML pages that work fine without JS... just use the pages router and a static export (https://nextjs.org/docs/pages/guides/static-exports https://nextjs.org/docs/pages/guides/static-exports). That still lets you use all the power of JS and expressiveness of React components, minus the interactivity, of course (if you don't want JS). But you could still pass in components and such. It's a bit like writing serverside includes in the PHP or Perl days. The benefit of using Next is its incredible popularity; probably whatever question you have, someone else has already asked and ten people have answered it. The downsides are its complexity and its frequent changes; answers from just a year or two ago are probably irrelevant to the current version, and there is a steep learning curve at first. But in SSG mode with the pages router, it's pretty straightforward, and the filesystem-based routing makes it very clear what the final directory structure would be. For Markdown there's https://docusaurus.io/ https://docusaurus.io/ and https://github.com/rust-lang/mdBook https://github.com/rust-lang/mdBook Eleventy is another option for various templating languages: https://www.11ty.dev/ https://www.11ty.dev/ See also these lists: https://jamstack.org/generators/ https://jamstack.org/generators/ https://github.com/myles/awesome-static-generators https://github.com/myles/awesome-static-generators