Static Site Generators in the Age of AI on SSG Book

Course introduction

Mon, 01 Jan 0001 00:00:00 +0000

Static Site Generators in the Age of AI

Building and Maintaining Content with AI Agents

Chapter 0: Course introduction

Polla Fattah

What you will build

One small website that grows from chapter to chapter.

A working site on your own computer in Chapter 1
Published at a public address by Chapter 7
Improved by an AI agent, with every change reviewed by you
A plan for a website of your own in Chapter 19

Why a static website?

Your content is plain text in folders you control
The build produces ordinary files any browser can read
Hosting can be free: GitHub Pages serves public projects at no charge
Every change is recorded in Git and can be undone

What “static” means

A static site generator combines your writing, a layout, and settings into finished web pages before anyone visits.

Your First Hugo Website

Mon, 01 Jan 0001 00:00:00 +0000

Static Site Generators in the Age of AI
Building and Maintaining Content with AI Agents

Draft 0.2, September 2026
Checked with Hugo 0.150.0 through 0.166.0. Requires Hugo 0.146.0 or later for the template layout convention.

You have something worth sharing: notes from your work, an explanation you have written, a useful collection of resources, or a project you want others to understand. A website gives those materials a place where people can find and read them.

Write and Publish Content Locally

Mon, 01 Jan 0001 00:00:00 +0000

Static Site Generators in the Age of AI
Building and Maintaining Content with AI Agents

Draft 0.2, September 2026
Checked with Hugo 0.150.0 through 0.166.0 (standard and extended editions).

In Chapter 1, you changed a home page. Now you will give your website something more substantial to read: its first article.

The article will describe a small thing you have learned. You will give it sections, add links and a screenshot, and make it reachable from the home page. Along the way, you will learn the Markdown needed to make a piece of writing understandable both as a text file and as a web page.

Your First Hugo Website

Mon, 01 Jan 0001 00:00:00 +0000

Your First Hugo Website

Static Site Generators in the Age of AI

Chapter 1

Polla Fattah

Today’s goal

A readable home page headed My Knowledge Notebook, running on your own computer.

Success means you can say:

I know which file contains these words, I can change them, and I can put them back.

By the end of today you can

Start and stop a local Hugo preview
Find and edit the file that holds the home-page introduction
Explain the roles of the content file, the layout, and the browser preview
Recover from a small mistake and keep a working copy

No HTML, CSS, Git, or programming experience is needed.

Organise a Useful Website

Mon, 01 Jan 0001 00:00:00 +0000

Static Site Generators in the Age of AI
Building and Maintaining Content with AI Agents

Your website now has a home page and an article. You know how to edit both, but a new visitor does not know where your files are. They need clear routes through the information you have published.

In this chapter, you will add an About page, give Articles a useful landing page, introduce a Projects section, and collect a few resources. Then you will replace the small home-page navigation with links that work across the website.

Write and Publish Content Locally

Mon, 01 Jan 0001 00:00:00 +0000

Write and Publish Content Locally

Static Site Generators in the Age of AI

Chapter 2

Polla Fattah

Today’s goal

Give your website its first article: a short note about something you have learned.

Sections, a link, a screenshot, and a code sample
Reachable from the home page

Publish locally means it appears in the preview on your computer. Nothing goes online today.

Organise a Useful Website

Mon, 01 Jan 0001 00:00:00 +0000

Organise a Useful Website

Static Site Generators in the Age of AI

Chapter 3

Polla Fattah

Today’s goal

You know where your files are. A new visitor does not.

Give them clear routes through the site:

An About page
Landing pages for Articles and Projects
A short Resources page
Navigation that works on every page

Every destination must contain something useful.

Understand the HTML Behind Your Pages

Mon, 01 Jan 0001 00:00:00 +0000

Static Site Generators in the Age of AI
Building and Maintaining Content with AI Agents

You have written articles, created sections, and changed the navigation of your website. Now we will look at what the browser receives when it displays those pages.

The title on the screen is not simply large text. The navigation is not merely a row of coloured words. They have a structure that the browser can interpret. Understanding that structure will help you make deliberate changes, diagnose mistakes, and assess code suggested by an AI agent.

Practical CSS for Your Hugo Site

Mon, 01 Jan 0001 00:00:00 +0000

Static Site Generators in the Age of AI
Building and Maintaining Content with AI Agents

Your notebook already has a readable layout. In Chapter 4, you inspected its HTML and added a footer note. Now you will give that note a style and make two small adjustments to the reading experience.

The visible result is small but deliberate: the footer note sits below a thin rule in quieter text, body text reads a little larger, and your article’s section headings have clearer space above them. Everything else should look as it did at the end of Chapter 4.

Understand the HTML Behind Your Pages

Mon, 01 Jan 0001 00:00:00 +0000

Understand the HTML Behind Your Pages

Static Site Generators in the Age of AI

Chapter 4

Polla Fattah

Today’s goal

See what the browser receives when it shows your pages.

The title is not just large text; the navigation is not just coloured words
Both have a structure the browser interprets

That lets you make deliberate changes, diagnose mistakes, and judge code an AI agent suggests.

Practical CSS for Your Hugo Site

Mon, 01 Jan 0001 00:00:00 +0000

Practical CSS for Your Hugo Site

Static Site Generators in the Age of AI

Chapter 5

Polla Fattah

Today’s goal

Three small, deliberate changes:

The footer note sits below a thin rule, in quieter text
Body text reads a little larger
Article section headings get more space above them

Everything else should look as it did after Chapter 4.

Enough CSS to customise this site and check an agent’s changes; not a design course.

Track and Recover Your Hugo Site with Git

Mon, 01 Jan 0001 00:00:00 +0000

Static Site Generators in the Age of AI
Building and Maintaining Content with AI Agents

In the previous chapters, you kept copies of the project before continuing. Those copies helped you recover, but comparing them becomes awkward. Which one contains the footer improvement? What changed in the stylesheet? Can you recover a file without replacing the whole site?

Git gives your project a history of recorded checkpoints. In this chapter, you will record your working Hugo site, save one useful content change, and recover from a deliberately poor styling change.

Publish Your Hugo Site with GitHub Pages

Mon, 01 Jan 0001 00:00:00 +0000

Static Site Generators in the Age of AI
Building and Maintaining Content with AI Agents

Your website now has content, a readable layout, and a local Git history. This chapter gives it an address other people can visit.

You will put the existing repository on GitHub, let GitHub Actions build it with Hugo, and publish the result through GitHub Pages. Then you will make one small update and follow it from your editor to the live page.

Track and Recover Your Hugo Site with Git

Mon, 01 Jan 0001 00:00:00 +0000

Track and Recover Your Hugo Site with Git

Static Site Generators in the Age of AI

Chapter 6

Polla Fattah

Today’s goal

Backup folders helped, but they are awkward to compare.

Which copy has the footer improvement?
What changed in the stylesheet?
Can I recover one file without replacing the whole site?

Git gives the project a history of recorded checkpoints. Today it stays local: no GitHub account yet.

Publish Your Hugo Site with GitHub Pages

Mon, 01 Jan 0001 00:00:00 +0000

Publish Your Hugo Site with GitHub Pages

Static Site Generators in the Age of AI

Chapter 7

Polla Fattah

Today’s goal

Give your website an address other people can visit.

Put the repository on GitHub
Let GitHub Actions build it with Hugo
Publish the result through GitHub Pages
Follow one small update from your editor to the live page

A supplied workflow, explained: no need to master Actions or YAML first.

Work with an AI Agent on Your Hugo Site

Mon, 01 Jan 0001 00:00:00 +0000

Static Site Generators in the Age of AI
Building and Maintaining Content with AI Agents

You can now write a page, recognise its HTML and CSS, save a Git checkpoint, and publish an update. Those skills make an AI agent more useful: you can give it a specific job and judge what it actually changes.

Our first job is small. The Resources page already contains useful links. You will ask an agent to add a short section explaining how a reader might use them. The result should be easy to inspect: one new heading and three bullets in one Markdown file.

Give Your Hugo Content a Consistent Structure

Mon, 01 Jan 0001 00:00:00 +0000

Static Site Generators in the Age of AI
Building and Maintaining Content with AI Agents

Your website has one project page. Adding a second is easy: create another Markdown file and begin writing. After several projects, however, you might notice that one page explains its purpose, another lists tools, and a third never says whether the work has started.

A small shared structure makes those pages easier to write, compare, and maintain. It also gives an AI agent concrete requirements to follow. The structure should answer useful questions without making every page look like a long form.

Work with an AI Agent on Your Hugo Site

Mon, 01 Jan 0001 00:00:00 +0000

Work with an AI Agent on Your Hugo Site

Static Site Generators in the Age of AI

Chapter 8

Polla Fattah

Today’s goal

Ask an agent for one small, checkable change: a short section on the Resources page explaining how to use its links.

One new heading and three bullets
In one Markdown file
Reviewed by you before it is kept

We use Codex CLI. The aim is a repeatable method, not a tour of every AI tool.

Give Your Hugo Content a Consistent Structure

Mon, 01 Jan 0001 00:00:00 +0000

Give Your Hugo Content a Consistent Structure

Static Site Generators in the Age of AI

Chapter 9

Polla Fattah

Today’s goal

After a few projects, one page explains its purpose, another lists tools, and a third never says whether the work has started.

Agree what every project page should explain
Build a reusable starter for new projects
Add a second project: a planned reading list

A shared structure is easier to write, compare, maintain, and hand to an agent.

Use Hugo Templates to Display Your Content

Mon, 01 Jan 0001 00:00:00 +0000

Static Site Generators in the Age of AI
Building and Maintaining Content with AI Agents

Your two project pages now contain useful information in their front matter. The description, status, and tools are organised, but visitors cannot see them yet. You also maintain a separate list of project links by hand.

A template can use those existing values to produce the page. Change a project’s description once, and Hugo can use it both on the project page and in the Projects list.

Build Reusable Hugo Layouts

Mon, 01 Jan 0001 00:00:00 +0000

Static Site Generators in the Age of AI
Building and Maintaining Content with AI Agents

Your shared layout now does several jobs. It creates the HTML document, displays navigation and a footer, presents page metadata, and generates the Projects list. It works, but finding the right place for the next change takes more care.

We will give those jobs clearer homes. A base template will hold the common document structure. Small partial templates will hold reusable pieces. A Projects section template will decide where the project list belongs.

Use Hugo Templates to Display Your Content

Mon, 01 Jan 0001 00:00:00 +0000

Use Hugo Templates to Display Your Content

Static Site Generators in the Age of AI

Chapter 10

Polla Fattah

Today’s goal

Your projects store a description, a status, and tools, but visitors cannot see them. And you still keep the Projects list by hand.

Display a description
Show status and tools when they exist
Let Hugo generate the Projects list

Change a description once; it updates everywhere Hugo uses it.

Build a Resource Directory with JSON

Mon, 01 Jan 0001 00:00:00 +0000

Static Site Generators in the Age of AI
Building and Maintaining Content with AI Agents

Your Resources page contains a small collection of links. Markdown handles that well. As the collection grows, however, you may want every entry to have the same information: a title, an address, a short explanation, and a few topics.

We will store those repeated details in JSON and let a Hugo partial display them. The surrounding introduction and links to your own notebook pages will remain ordinary Markdown.

Build Reusable Hugo Layouts

Mon, 01 Jan 0001 00:00:00 +0000

Build Reusable Hugo Layouts

Static Site Generators in the Age of AI

Chapter 11

Polla Fattah

Today’s goal

One layout now does everything. It works, but every change needs care.

A base template for the shared document
Small partials for reusable pieces
A section template for Projects

Reorganising working code should preserve its behaviour. Check that first.

By the end of today you can

Move a component into a partial and pass it the context it needs
Connect a base template’s named block with its definition
Give Projects its own layout, sharing the rest
Check that content, links, and metadata survived the move

Start from Chapter 10, with status in the project list, and a clean tree (companion branch chapter-10).

Build a Resource Directory with JSON

Mon, 01 Jan 0001 00:00:00 +0000

Build a Resource Directory with JSON

Static Site Generators in the Age of AI

Chapter 12

Polla Fattah

Today’s goal

As the Resources list grows, every entry should carry the same information: a title, an address, a short explanation, and a few topics.

Store the repeated details in JSON
Let a Hugo partial display them
Keep the introduction and notebook links in Markdown

Add a resource by editing data; the template supplies the HTML.

Create and Maintain Content with AI Agents

Mon, 01 Jan 0001 00:00:00 +0000

Static Site Generators in the Age of AI
Building and Maintaining Content with AI Agents

In Chapter 8, you gave an agent a small, self-contained job: three bullets in one file. You could read the whole result in a minute. Real content work is larger than that, and its mistakes are harder to see.

In this chapter, you will produce a complete article from source material you supply, then connect it to the rest of the site. The work is divided into three requests: a plan, a draft, and a coordinated update across several files. You will review the claims in the draft against the source before publishing anything.

Check Every Contribution with CI/CD

Mon, 01 Jan 0001 00:00:00 +0000

Static Site Generators in the Age of AI
Building and Maintaining Content with AI Agents

Chapter 6 deferred branching until there was a concrete reason to use it. This is that reason. Every change you have made since then went straight onto main, and every push to main publishes.

In this chapter, you will add a second workflow that examines a proposed change before it can reach the live site. It builds the site and checks three rules this book has already established: directory flags must be real Booleans, internal links must stay relative, and articles and projects must carry a description. Then you will propose a change on a branch, break one of those rules on purpose, and watch the checks stop it.

Create and Maintain Content with AI Agents

Mon, 01 Jan 0001 00:00:00 +0000

Create and Maintain Content with AI Agents

Static Site Generators in the Age of AI

Chapter 13

Polla Fattah

Today’s goal

Chapter 8 was three bullets. Real content work is larger, and harder to check.

One new article, written from notes you supply
Linked from Articles, Home, and the resource directory
Three requests: a plan, a draft, a coordinated update

Supply the material, bound the task, check every claim, decide yourself.

Check Every Contribution with CI/CD

Mon, 01 Jan 0001 00:00:00 +0000

Check Every Contribution with CI/CD

Static Site Generators in the Age of AI

Chapter 14

Polla Fattah

Today’s goal

Every change so far went straight onto main, and every push to main publishes.

A second workflow that examines a proposal before it goes live
A branch and a pull request
A rule broken on purpose, and stopped

Machines check what can be a rule; you check the rest.

Help Readers Find and Use Your Content

Mon, 01 Jan 0001 00:00:00 +0000

Static Site Generators in the Age of AI
Building and Maintaining Content with AI Agents

Your notebook now has nine pages, a resource directory, a publishing workflow, and checks on every proposal. A visitor arriving at it has the navigation, and nothing else. They cannot search it, and a browser tab showing every page as part of the same long name does not help them keep their place.

In this chapter you will improve how the site describes itself and add a way to search it. You will give every page a useful document title and a description, inspect the sitemap and feed Hugo has been generating all along, and build a search page that filters a list of your pages as the reader types.

Help Readers Find and Use Your Content

Mon, 01 Jan 0001 00:00:00 +0000

Help Readers Find and Use Your Content

Static Site Generators in the Age of AI

Chapter 15

Polla Fattah

Today’s goal

A visitor has the navigation, and nothing else. They cannot search, and every tab title looks alike.

A distinct title and a description for every page
The sitemap and feed Hugo has generated all along
A Search page that filters as the reader types

And a page that still lists every destination when JavaScript does not run.

Publish in Multiple Languages

Mon, 01 Jan 0001 00:00:00 +0000

Static Site Generators in the Age of AI
Building and Maintaining Content with AI Agents

Your notebook is in English. If some of your readers would rather read Kurdish, or if your work belongs to a place where two languages are normal, the site should be able to say the same things twice.

In this chapter you will add Kurdish Sorani as a second language, translate the navigation and two pages, and give the document the language and text direction a browser needs. Kurdish Sorani is written in a Perso-Arabic script and runs right to left, so this is also the first time your layout has to work in the other direction. You will find and repair the one stylesheet rule that assumes left to right.

Add Interactive Features Responsibly

Mon, 01 Jan 0001 00:00:00 +0000

Static Site Generators in the Age of AI
Building and Maintaining Content with AI Agents

Readers who find something useful on your site may want to reply to it. A contact form is the obvious way to invite that, and it is also the point where a static site meets its actual limit.

Your site is a set of files. It has no program running on a server, so there is nothing on your side to receive a submitted message. In this chapter you will build a proper contact form, watch it fail to send, and then make it work in the one way a site like yours can without collecting anyone’s data: by handing the message to the visitor’s own mail program.

Publish in Multiple Languages

Mon, 01 Jan 0001 00:00:00 +0000

Publish in Multiple Languages

Static Site Generators in the Age of AI

Chapter 16

Polla Fattah

Today’s goal

Add Kurdish Sorani as a second language: a Kurdish home page and About page at /ckb/.

Translated navigation and a language switcher
The right language and text direction for every page
The layout working right to left
The English site unchanged at its existing addresses

Arabic, or any other language, works the same way.

Add Interactive Features Responsibly

Mon, 01 Jan 0001 00:00:00 +0000

Add Interactive Features Responsibly

Static Site Generators in the Age of AI

Chapter 17

Polla Fattah

Today’s goal

A contact form is where a static site meets its actual limit.

Build a proper, accessible form
Watch it fail to send
Make it work the one way that collects nothing: the visitor’s own mail program

Where does the work happen, and at what cost?

Maintain, Migrate, and Recover

Mon, 01 Jan 0001 00:00:00 +0000

Static Site Generators in the Age of AI
Building and Maintaining Content with AI Agents

Your notebook works. It is published, checked on every proposal, searchable, bilingual in part, and able to receive a message. Nothing about it is finished, because a website that nobody maintains does not stay still; it goes quietly out of date while appearing to work perfectly.

In this chapter you will make a maintenance pass over the site you actually have. You will find a page that now says something untrue, update what you depend on, archive work that has been superseded, and publish a mistake on purpose so that you can practise recovering from it after it has gone live. Then you will settle the questions that outlast any single change: credentials, licensing, privacy, cost, and who owns what.

Build Your Own Publishing Project

Mon, 01 Jan 0001 00:00:00 +0000

Static Site Generators in the Age of AI
Building and Maintaining Content with AI Agents

Eighteen chapters ago you did not have a website. You now have one that is published, checked before every change, searchable, partly bilingual, able to receive a message, and covered by a maintenance routine you wrote yourself. More importantly, you have done each of those things once, deliberately, and can explain why.

This chapter turns that into something of your own. You will choose a project, write a brief that says what you are not building, pick features by what they cost to keep rather than by what is possible, and test that brief before writing a single page. Then you will build it from a checkpoint, agree who reviews and who maintains it, and decide what “delivered” means.

Maintain, Migrate, and Recover

Mon, 01 Jan 0001 00:00:00 +0000

Maintain, Migrate, and Recover

Static Site Generators in the Age of AI

Chapter 18

Polla Fattah

Today’s goal

A site nobody maintains does not stay still: it goes quietly out of date while appearing to work.

A maintenance pass over the site you have
Update what you depend on; archive superseded work
Publish a mistake on purpose, and recover from it live
Credentials, licensing, privacy, cost, and ownership

By the end of today you can

Run a repeatable maintenance pass and act on what it finds
Update a pinned dependency in every place it is pinned
Retire a page without breaking a published address
Undo a live change without rewriting published history

Start from Chapter 17 (branch chapter-17): clean, pushed, and deployed.

Build Your Own Publishing Project

Mon, 01 Jan 0001 00:00:00 +0000

Build Your Own Publishing Project

Static Site Generators in the Age of AI

Chapter 19

Polla Fattah

Today’s goal

You have done every step once, deliberately. Now the decisions are yours.

Choose a project you can finish
Write a brief that says what you are not building
Pick features by what they cost to keep
Test the brief before building, then deliver

A site a stranger can use, you can maintain in a year, and whose quality you can account for.

Migrating a Database-Driven CMS to a Static Site Generator

Wed, 16 Sep 2026 00:00:00 +0000

Migrating an organization from a database-driven Content Management System (CMS), such as WordPress, Drupal, or a custom PHP and SQL stack, to a Static Site Generator (SSG) fundamentally alters the operational model of a website.

The transition eliminates runtime server execution, replacing dynamic database queries with deterministic ahead-of-time (AOT) compilation distributed globally over Content Delivery Network (CDN) edge caches.

Architectural Transition Overview

The core shift decouples content authoring and build-time compilation from the public delivery layer:

Static Site Generator Landscape: A Reference Guide

Tue, 15 Sep 2026 00:00:00 +0000

Static site generators span a wide range of languages, runtimes, and publishing models. Some are general-purpose build tools, while others specialize in documentation, scientific publishing, blogs, books, or framework-based applications.

This reference organizes the landscape by ecosystem and highlights the architectural focus of each generator.

JavaScript and TypeScript

General Purpose and Content-First

Eleventy (11ty) : Node.js-based generator supporting Liquid, Nunjucks, Markdown, WebC, and multiple other templating languages, with zero client JavaScript by default.
Astro : Component-islands architecture supporting React, Preact, Svelte, Vue, SolidJS, and plain Markdown or MDX with partial hydration.
Hexo : Fast Node.js blogging engine with extensive plugin and theme ecosystems.
Lume : Deno-native static site generator supporting Nunjucks, Vento, JSX, Markdown, and TypeScript.
Metalsmith : Functional, plugin-driven file manipulation pipeline for Node.js.
Assemble : Classic Grunt and Gulp-era generator powered by Handlebars.
Harp : Zero-configuration web server and static engine supporting Jade/Pug, Markdown, and EJS.
Phenomic : Modular static site compiler for React and Webpack ecosystems.
Wintersmith : Flexible, multi-format Node.js site generator.
DocPad : Early extensible Node.js document management and site builder.
Punch : Conventions-based site generator using Mustache.
Blacksmith : Logic-less template engine driven by Director and Plates.
Capri : Vite-based static compiler supporting partial hydration across diverse frontend libraries.
Elder.js : Opinionated, SEO-optimized static site generator designed for Svelte.
iles : Vite-driven static generator featuring islands of interactivity for Vue, Preact, and Svelte.
Abell : Low-level, lightweight static generator using custom .abell component syntax.

React Frameworks and Static Export

Next.js (output: 'export'): Full static HTML export from React server and client components.
Gatsby : React and GraphQL-based static generator with an extensive plugin ecosystem.
React Static : Minimalist, progressive React-first static site framework.
Cuttlebelle : React-driven generator that decouples data and editing from code components.

Vue.js Ecosystem

Nuxt (nuxi generate): Prerenders Vue.js applications into crawlable static HTML.
VitePress : High-speed Vue 3 and Vite documentation generator and successor to VuePress.
VuePress : Classic Vue-powered static site generator using Markdown and Webpack.
Gridsome : Vue 2 alternative to Gatsby powered by a local GraphQL data layer.
Saber : Extensible Vue-based static site generator with automatic routing.

Documentation and Technical Publishing

Docusaurus : Meta-maintained documentation framework built on React and MDX.
Starlight : Documentation platform built directly on top of Astro.
Slate : Markdown-based API documentation generator.
Docsify : Runtime Markdown compiler that renders documentation on the fly without a build step.
Docute : Lightweight alternative to Docsify for single-page documentation.
GitBook Legacy CLI : Original Node.js command-line tool for publishing Markdown books.

Angular and Svelte

Scully : Static site generator for Angular applications.
SvelteKit with adapter-static: Pre-renders static HTML pages for Svelte applications.
Sapper : Legacy predecessor to SvelteKit with built-in static page exports.

Go

Hugo : Extremely fast build engine written in Go, featuring built-in asset pipelines and zero runtime dependencies.
Goldsmith : Pipeline-based static generator inspired by Metalsmith and compiled to native Go.
Statically : Go-based static engine built around Markdown and Go standard templates.
Ponzu : Headless CMS and server written in Go that supports static JSON and HTML generation.
GoPublish : Minimalist publishing tool for transforming Markdown structures into HTML.

Rust

Zola : Fast, all-in-one generator using Tera templates, Sass compilation, and CommonMark.
mdBook : Official command-line tool used by the Rust team for creating programming and technical books.
Cobalt : Minimalist, opinionated static blog engine.
Seite : Modern static site generator featuring native Model Context Protocol (MCP) tool integration.
Crowbook : Converts Markdown books into HTML, EPUB, and PDF formats.

Python

Pelican : Veteran Python SSG supporting Markdown and reStructuredText with Jinja2 templating.
MkDocs : Markdown-driven generator focused on project documentation, widely paired with the Material theme.
Sphinx : Standard documentation tool across the scientific Python community, supporting reStructuredText and MyST Markdown.
Lektor : Flexible, desktop GUI-friendly flat-file content management system and static builder.
Nikola : Feature-rich engine supporting Markdown, reStructuredText, and Jupyter Notebooks.
Frozen-Flask : Freezes dynamic Flask applications into completely static file trees.
Cactus : Static site generator designed to deploy directly to Amazon S3 using Django templates.
Hyde : Early Python alternative to Jekyll built on Jinja2.
MyST Markdown / Curvenote : Scientific publishing engine converting technical Python code and notebooks into websites.
Bengal : Python generator designed for documentation and product sites.
Blurry : Schema-first, SEO-focused Markdown generator producing Schema.org metadata.
Dewar : Flask-like, lightweight static publishing pipeline.
Pagegen : Simple, syntax-flexible page generator.

Ruby

Jekyll : Foundation of modern static publishing, deeply integrated as the default builder for GitHub Pages.
Bridgetown : Modern Ruby static and progressive framework that modernizes Jekyll with Vite and esbuild.
Middleman : Sinatra-inspired modular site generator specialized in marketing and campaign sites.
Nanoc : Flexible, data-driven transformation pipeline supporting heterogeneous data sources.
Ruhoh : Universal static blog engine designed as a decoupled version of Jekyll.
Scruffy : Minimalist static builder focused on text-only and lightweight styling.

PHP

PHPJigsaw : Built on Laravel’s Blade templating engine, Mix/Vite, and Tailwind CSS.
Sculpin : Composer-based static generator powered by Symfony components and Twig templates.
Spress : Extensible static site generator built on Symfony micro-components.
Couscous : Generates developer documentation websites directly from Markdown files in GitHub repositories.
Capro : Lightweight PHP 8 static generator using Laravel Blade templates.
flatMark : Flat-file Markdown website generator requiring no database dependencies.
Phrozn : Component-based static site generator written in PHP.

C#, .NET, and F#

Statiq : Highly modular, extensible pipeline-driven document generator for .NET developers.
Wyam : Predecessor to Statiq using Razor templates and Roslyn-powered configuration.
AspNetStatic : Static generation engine that prerenders pages from existing ASP.NET Core pipelines.
DocFX : Microsoft’s technical documentation generator for .NET API references and Markdown.
Fornax : Static site generator written in F# using type-safe F# DSLs for page layouts.

C, C++, and Minimalist Tools

Soupault : C and OCaml DOM-based generator that manipulates raw HTML elements through HTML parsers rather than text template tags.
Tup : High-speed build system frequently adapted for low-latency static site pipelines.
Treehouse : Minimalist C-based Markdown processor generating lightweight static trees.
Smu : Small Markdown engine designed for fast shell-based static builds.

Haskell and Functional Languages

Hakyll : Haskell static site compiler powered by Pandoc with an xmonad-like DSL.
Franklin.jl : Julia static engine focused on mathematics and LaTeX-rich scientific writing.
Pollen : Lisp and Racket-powered digital book publishing environment created by Matthew Butterick.
Frog : Racket static blog generator using Markdown and Pygments.
Obelisk : Elixir static site framework leveraging Elixir concurrency and EEx templates.
Coil : Minimalist Elixir-based static site engine.
LambdaPad : Erlang-based static website compiler.
Cryogen : Clojure compiler built with Selmer and Markdown.
Perun : Clojure build pipeline targeting the Boot and Clojure ecosystem.

JVM Languages

JBake : Java generator supporting AsciiDoc, Markdown, FreeMarker, and Thymeleaf.
Orchid : Java and Kotlin documentation and site generator supporting multi-module builds.
Laika : Scala text-to-HTML, EPUB, and PDF compiler.
Gaiden : Groovy documentation engine for turning Markdown into clean reference sites.
Grain : Groovy static generator using metaprogramming capabilities.

Swift

SwiftPublish : Swift-native generator allowing entire websites to be declared in pure Swift code.
Saga : Code-first static generator in Swift with no configuration files or implicit build magic.
Ignite : Declarative, pure-Swift static site builder adopting SwiftUI-like syntax.

Perl

Blosxom : Historic flat-file blogging engine originally written as a single Perl script.
Statocles : Comprehensive CMS and static publishing platform for Perl developers.
Dotiac DTL : Django Template Language compiler ported to Perl for static page rendering.

R and Literate Data Science

Quarto : Multilingual technical publishing system for R, Python, Julia, and Observable JavaScript, powered by Pandoc.
Blogdown : R package integrating Hugo, Markdown, and R Markdown for data-driven websites.
Bookdown : Authoring framework built on R Markdown for multi-chapter technical books.

Shell, Awk, Make, and Minimal Utilities

BashBlog : Self-contained Bash script that generates a complete RSS-capable blog.
Site44 : Web service that compiles Dropbox folders into static hosting.
saait : HTML site generator written in C and Awk for simple, lightweight pages.
m4-bakery : Static generator using GNU m4 macro processing and Make pipelines.
gen_site : Ultra-minimalist Lua generator for developers working directly in HTML and Lua.
Hwaro : High-speed static generator compiled to native code using Crystal.

Choosing from the Landscape

The right generator depends less on the total number of features than on the shape of the project:

The Modern Static Site Generator Landscape

Mon, 14 Sep 2026 00:00:00 +0000

Static site generators (SSGs) have evolved from simple Markdown compilers into specialized build engines powering marketing platforms, software documentation, and high-performance content networks. While all SSGs share the core philosophy of shifting rendering costs from request-time to build-time, their underlying architectures, developer ergonomics, and runtime footprints vary considerably.

The modern landscape includes Hugo, Astro, Eleventy, Docusaurus, VitePress, Quarto, Jekyll, Next.js, and Nuxt. Each occupies a different place on the spectrum between zero-JavaScript content publishing and fully hydrated application experiences.

The Unreasonable Effectiveness of Static Sites in the Agentic Age

Sun, 13 Sep 2026 00:00:00 +0000

For nearly two decades, the architecture of the web was dominated by a singular assumption: a website is an interface on top of a dynamic SQL database. Systems like WordPress, Drupal, and custom monolithic applications took root because non-technical users needed a graphical user interface (GUI) to modify database rows, which a server runtime would reassemble into HTML on every incoming HTTP request.

The explosion of Autonomous AI Agents has upended that paradigm.

The Fourth Pillar: Architectural Necessity and Design Specification for a Universal Static Site Generator Standard Mark

Sat, 12 Sep 2026 00:00:00 +0000

For more than three decades, the visual taxonomy of the World Wide Web has evolved alongside its underlying architectural models. When developers communicate technical competencies, stack topologies, or system designs, they do not rely solely on prose; they rely on an established visual shorthand.

We immediately recognize the orange shield of HTML5, the blue shield of CSS3, and the yellow badge of JavaScript. Together, they form the canonical trinity of client-side web development:

The book's website is live

Fri, 11 Sep 2026 00:00:00 +0000

The website for Static Site Generators in the Age of AI is now online. It holds the complete draft of the book: nineteen chapters that build one small website from its first Markdown page through publication, review, and long-term maintenance.

Three pages will help you find your way in:

The book , in chapter order.
Learning paths , which suggest where to start depending on what you already know.
Learning topics , the thirty-three topics the book teaches.

The book is a working draft. Each chapter opens with a note recording how far it has been tested, and those notes will change as the chapters are tried with readers. Lecture slides and a hands-on playground are in preparation.