re: The Sales Pitch of Static Site Generation VIEW POST

re: I really cannot think of a better name in the context of static vs. dynamic. But possibly something completely different like Site Content Generat...

I cross posted this to community.netlify.com and found some great advice. In summary:

  1. There's nothing static about a site generator when used in the context of a JAMstack. Focus on the JAMstack architecture and refer to the site generator piece as just that: a site generator and just skip the static part.
  2. For some people it might be best understood as server side rendering in advance. While not perfectly accurate it elucidates the benefits without giving the impression of limitations that do not really exist.
  3. For others the term "baked" vs "fried" might be a good description as this is a term that has been around for a while.
  4. Focus on selling the benefits and not the technology. Security, performance, decoupled architecture, and a flexible authoring process that is not tied down to the other technology choices that have been made.

Special thanks to the folks on the community.netlify.com that provided these responses. I also wanted to summarize them here.

Code of Conduct Report abuse