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.
Top comments (2)
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:
Special thanks to the folks on the community.netlify.com that provided these responses. I also wanted to summarize them here.