Skip to the content
Documentation
Help Start
Reading in:
  • German: 9,059 of 9,059 pages
About the help in other languages
All help pages

Static publishing compared with static site generators

An honest comparison of Exponential's static publishing with Jekyll, Hugo, Eleventy, Astro and headless setups - where a CMS that publishes static copies wins, and where a generator is the better tool.

Download as PDF

Address: https://doc.exponential.earth/exphelp/viewer/help/web-framework-developers/static-publishing-compared-with-static-site-generators.md

On this page

Static publishing compared with static site generators

If you know Jekyll, Hugo, Eleventy or Astro, static publishing will look familiar in its output and different in how it gets there. This page compares them honestly.

What you'll have at the end

A clear idea of when to use Exponential's static publishing, when a generator, and when both.

The basic difference

Static site generatorExponential static publishing
Content lives inMarkdown files in git, or a headless CMSExponential's content repository, edited in its editor
Who editsdevelopers, or editors through a git-based UIeditors in a full CMS, with versions, workflows, roles and translations
How the site is madetemplates render files at build timethe real site is rendered, then crawled as an anonymous visitor and rewritten
Previewa local dev serverthe dynamic site itself, plus a preview of each build
Historygit commits of the sourcesversions in Exponential, plus one tagged commit per publish
Build speedvery fasta crawl; minutes for hundreds of pages, partial builds for single pages

Where static publishing wins

  • Editors who are not developers. They get a real editor, images, relations, scheduling and roles.
  • An existing Exponential site. The same templates make the dynamic and the static site; nothing is written twice.
  • Mixed sites. Search runs in the browser, forms can post to the live site, member areas stay dynamic.
  • Safety. Only what an anonymous visitor sees is published; drafts and private content never reach the build.

Where a generator wins

  • Docs-as-code with pull-request review of Markdown, where everyone edits in git anyway.
  • Very large sites rebuilt very often, where a crawl is slower than rendering from files.
  • No server at all, not even for editing. Exponential needs PHP and a database somewhere, if only on a laptop or in CI.

Using both

The output is plain files in a folder, so anything that deploys a folder deploys it: GitHub Pages, GitLab Pages, Netlify, Cloudflare Pages or rsync to any web server. You can also keep a generator for your docs and publish the marketing site from Exponential.

Details of the output: The build format. Command line and CI: Static publishing from the command line and CI.

Make yours now

Judge it on a real site: Make a free website in 15 minutes.

Something wrong on this page? Report an error

Documentation license

This documentation is free documentation, licensed under the GNU Free Documentation License 1.3 or later.

Exponential Copyright © 1998-2026 Exponential Foundation and 7x