Skip to content
HalftoneJournal

Publishing test site

How it works

The same articles and the same components, deployed two ways. Each edit is timed from the moment it is saved to the moment a reader can see it.

EditorContent repoBuild + deploySTATICContent storeEDGEReaders

Static

Every page is built ahead of time. A publish runs one build of the whole site and deploys it. Readers always get prebuilt HTML.

Build, 500 articles
3 s
Deploy
5 s
Edit to live
12 s p50 (local), ~1 min with CI
Response, cached
69 ms p50
Response, first request
197 ms p50

Edge

Articles render on request from a content store and are cached at the edge. A publish writes the article and bumps a version, so the next request renders fresh HTML. No build.

Edit to live
6 s p50
Response, cached
77 ms p50
Response, first render
271 ms p50

Nov 17, 2026 · one location · 500 articles

What both share

Watch the pill in the corner: it shows how the page you are reading was produced.