This page is part of my digital garden.

This page might be unfinished or have typos. These pages are meant as part of a public living notebook to be edited over time. For more, visit the page explaining the concept of a digitial garden.

Static Websites

Static websites have become extremely popular these days. That’s because storage drives have gotten so big and the costs of serving files behind a highly optimized server are almost zero.

Even the cheapest servers ($15/year) can not compete with a couple powerful servers shared among thousands of customers focused on serving files that rarely change as fast as possible.

These days static websites are made using one of several Static Site Generators (SSG)1. This website is static and uses Hugo. But static websites became popular after Github added support for Jekyll and it’s the standard choice. There is also E11venty, Next.js, Pelican, and others.

The point of these programs is to avoid the toil of maintaining a bunch of HTML pages directly and instead let you write blog posts in Markdown for instance and convert that to HTML when you’re ready to publish. Generating the HTML from the various templates and markdown files is the “static generation” part because after this it’s kind of assumed you won’t want to edit the html directly and instead just make changes and rerun the generator.


  1. Not to be confused with Server Side Generated which refers to pre-rendering what a React/Angular/Vue site should look like before it hits the browser. ↩︎

Last updated on