Home

A WordPress editor. A static site. No database.

Jamground is a website whose content lives as plain files in git, is edited in `wp-admin`, and is published as static HTML. The unusual part is that no WordPress runs on any server — the editor is WordPress compiled to WebAssembly, running inside the browser tab of whoever is writing.

The result is a site with an editing experience people already know, and none of the operational surface that usually comes with it.

What that buys you

• Nothing to patch. There is no PHP, no database and no WordPress on the server, so the usual maintenance and the usual attack surface are simply absent.
• Every change is reviewable. Editors work in `wp-admin`; what comes out is a set of file changes someone can read and approve before anything goes live.
• Every change gets its own preview, built automatically, at its own address.
• The published site is static files. It is fast, it is cheap to serve, and it keeps serving if everything else is down.

Where to go next

• **Why Jamground** — the problem this solves, and what it costs.
• **Architecture** — the three moving parts, and how a change reaches production.
• **How to Use** — the editorial workflow, start to finish.