The Sales Pitch of Static Site Generation

megazear7 profile image megazear7 ・1 min read

I have recently developed a static site generator tool called Orison and for this reason among others I have been trying to "sell" people on static site generators; developers, architects, and non technical folks included. For many people the term "Static Site Generation" is synonymous with "small blog", "personal site", and "trivial use case" instead of phrases like "enterprise scale" and "unbeatable performance".

I am very thankful for everything that Netlify has done to popularize static site generation. However I wander if the naming of the term turns people away. In technical articles, presentations, blog posts, and in person discussion I often use the term "build tool", "build process" or something of that sort to describe the role that the static site generator plays in the JAMstack architecture.

I am curious as to what you have found. Is there a better term that I am missing? Should we instead focus on rebranding the term "static site generator"? Does it even matter?

Thank you ahead of time for any responses. The subjective human experience is often an under realized blocker to technology and especially in this case one that I think would be worth discussing.

Posted on by:

megazear7 profile



Loves to learn, create and share. Websites, games, stories or simply ideas. Sharing all the possibilities of a "blank canvas" on www.alexlockhart.me


markdown guide

I really cannot think of a better name in the context of static vs. dynamic. But possibly something completely different like Site Content Generator or Site Content Manager might be more appropriate


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.