Not a document you publish. That distinction is what the invoices are for.
An editor edits them. A build finishes them. A network serves them.
In a visual editor on your own machine, or in any text editor.
The change is a readable diff in your own git repository.
Your host builds on push and serves finished pages from a CDN.
Every page is finished before anyone asks for it.
A default build is files. No database, no application server, no per-request rendering.
Editing happens on your machine against your files. There is no hosted dashboard for bots to find.
Compiled pages contain no eval and no dynamic code construction. A test in the compiler enforces it on every build.
Four security headers ship with every build, and a self-only content policy is one line away because the runtime is served from your own domain.
Add accounts or a database later and that is a second surface — one that fails closed: every write is denied until you say otherwise.
Images are converted to modern formats at build time, sized for the device asking, and fingerprinted so they can be cached indefinitely. Nobody has to remember to do it.
The editor publishes code; it does not deploy. Your host builds the site on every push and serves the result.
That separation is why there is no dashboard to breach — and why the site keeps serving perfectly well while nobody is editing it.
A typical 40-page brochure site for a small business. Illustrative estimates, so your costs will vary. The licence figure is not an estimate: Jx is MIT, with no subscription and no seats.
| Who can edit | Maintenance | Security surface | Lock-in | |
|---|---|---|---|---|
| WordPress | Anyone | Heavy | Server, database, plugins | High |
| Headless CMS + framework | Developers | Heavy | Server and API | Medium |
| SaaS site builder | Anyone | Light | The vendor's | Total |
| Static site generator | Developers | Light | Files only | Open |
| Jx | Anyone | Light | Files only | Open |
A static site generator scores as well as Jx on every column but one — and that one is who is allowed to change the site.
Use it, fork it, sell work built with it. No subscription and no seats.
JSON and Markdown in your own git repository. Human-readable, and version-controlled by construction.
HTML, CSS and a little JavaScript. Any web server in the world will serve them.
There is no export step, because the project already is the files. Changing host changes one setting.
We rebuild one site, or one section, on Jx. You judge the real thing against your real content.
The rest follows at whatever pace suits the calendar. Nothing about this is big-bang.
Your team is trained on the editor, and the component library we build is yours to keep.