Table Of Contents
There comes a moment in every blogger's life when the hosted platform starts to feel small. You want your own design, your own URLs, maybe a page of footnotes that does not look like a ransom note. This is the moment you meet the static site generator.
A static site generator takes a folder of plain text files, usually Markdown, runs them through templates, and spits out finished HTML pages. There is no database and no login page for bots to attack. The Programming Historian lesson on Jekyll puts it well: a static site does not query a database when you visit, because the HTML pages are already built.
For digital humanities, this matters a lot. Flat files are easy to preserve, cheap to host, and readable by humans fifty years from now. That is the heart of minimal computing, which I wrote about in Digital Humanities Part 6. Your dissertation's companion website should not die because someone forgot to renew a database server.
Here are three generators, each with a different personality.
Before you start #
You will need three things for all of them:
- A terminal. On a Mac, open Terminal. On Windows, use PowerShell or WSL.
- A text editor. VS Code is fine. So is anything that saves plain text.
- Git, eventually. You do not need it on day one, but you will want it the first time you break something and wish you could go back in time.
Do not panic about the terminal. You will type perhaps six commands today. You have survived worse, including the course registration portal.
Build Awesome (formerly Eleventy, or 11ty) #
This is the one I use for this site, so consider me biased. Eleventy joined Font Awesome in 2024 and announced in March 2026 that it is now Build Awesome. Same project, same maintainer, and existing Eleventy plugins and build commands are meant to keep working. Version 4 of Eleventy will be Build Awesome version 4.
Build Awesome runs on JavaScript, so the project recommends Node.js 18 or newer. Check what you have:
node --version
Then make a project folder, set it up for npm, and install:
mkdir my-site
cd my-site
npm init -y
# To install, choose one of these:
npm install @11ty/eleventy@canary --save-exact
npm install @awesome.me/buildawesome@alpha --save-exact
Both lines install the same version 4 code. The first uses the familiar Eleventy package name, and the second uses the new Build Awesome name. --save-exact pins the exact version in your package.json, which matters while version 4 is still in alpha. You do not want a surprise upgrade the night before an assignment is due.
Add a file called index.md with a sentence in it, then start the local server with the command that matches your install:
npx eleventy --serve # if you installed @11ty/eleventy@canary
npx buildawesome --serve # if you installed @awesome.me/buildawesome@alpha
Open http://localhost:8080/ and there is your website. That is it. That is the whole trick.
One warning, because I have the scars. Keep the @canary or @alpha tag in the install command. As I write this, the plain latest tag for @awesome.me/buildawesome on npm still points to a 0.0.3 placeholder, so leaving the tag off installs a package that does nothing useful.
I wrote up my own move to the alpha in How Build Awesome alpha fixed my podcast build.
Why pick it: It is flexible, it lets you mix template languages, and it does not force a folder structure on you. Why not: That flexibility means more decisions, and decisions are where beginners get stuck.
Hugo #
Hugo is written in Go and ships as a single program. It is famously fast. It builds big sites in the time it takes you to reach for your coffee. The quick start asks for Hugo v0.158.0 or later, plus Git:
hugo new project quickstart
cd quickstart
git init
git submodule add https://github.com/gohugo-ananke/ananke themes/ananke
echo "theme = 'ananke'" >> hugo.toml
hugo server
Visit the address Hugo prints, and you have a themed site. To see posts marked as drafts, run hugo server -D.
Why pick it: One download, no JavaScript or Ruby setup, and blistering speed on sites with thousands of pages. Why not: Hugo's Go templates can feel like reading tax law written by a poet. Powerful, but strange.
Jekyll #
Jekyll is the elder statesperson, written in Ruby. The current release is v4.4.1 and it needs Ruby 2.7 or higher:
gem install jekyll bundler
jekyll new myblog
cd myblog
bundle exec jekyll serve
Then browse to http://localhost:4000. If you are on Ruby 3 and step four throws an error, run bundle add webrick and try again. This is the single most common Jekyll stumble, so now you know.
Jekyll's superpower is GitHub. GitHub Pages has built-in support for Jekyll, so you can publish a site without running any server at all. It also has deep roots in digital humanities. CollectionBuilder uses Jekyll to turn a spreadsheet of metadata and a folder of images into a digital collection, and Wax uses Jekyll and IIIF to build scholarly exhibitions with minimal computing principles. The Programming Historian even has a lesson on running a collaborative DH research blog with Jekyll.
Why pick it: Huge DH community, GitHub Pages integration, tons of tutorials. Why not: Ruby installs can be fussy, especially on older Macs. My own path was learning Eleventy by adapting a Jekyll template, which tells you how often people start here and wander off.
Which should you choose? #
- You want a DH collection or exhibit with minimal fuss: Jekyll, through CollectionBuilder or Wax.
- You want one program, no dependencies, and speed: Hugo.
- You want maximum control and a friendly community: Build Awesome.
Honestly, the best generator is the one you finish a project with. All three produce plain HTML, and all three read Markdown, so your words are portable. If you change your mind in two years, your posts come with you. That is the real lesson here. Static site generators are not only a faster way to make websites. They are a way of keeping your scholarship in formats you control.
Next week we turn to Omeka, which is what you reach for when your project is less "blog" and more "archive." In the meantime, pick one generator, install it, and get a single page running on your own computer. Then tell me which one won.
Tags : digital-humanities build-awesome 11ty hugo jekyll minimal-computing ht930 how-to
Webmentions
No webmentions yet.