CS Powerhouse Good to Press
Every post passes a gate before it goes live.
A local editor and release pipeline for static sites, built for developers and agencies. Edit on your own machine, publish to a server that has no CMS, no admin login and no database.
Status, plainly
Good to Press is not released. It is the public edition of the tool that already runs Aaron Belchamber's own sites, and the work to make it installable by anyone else is under way. The waitlist is how you hear when it is ready, and how the demand gets measured. Nothing on this page is for sale yet, and there is no price to quote.
It runs no AI. AI helped build it, and that is told on the case study; the tool you would install does not call a model.
What Good to Press is for
Deploy gates with rollback
A release runs source checks, build checks and, after upload, live checks against the real server. The build is uploaded beside the live one and swapped in by renaming directories, and the previous build is kept so a failed content check puts it back.
A block schema with no style fields
Pages are built from blocks that take content and a short list of named variants, never a color, a pixel size or a font. An edit cannot break the design, because the editor has no way to say how anything looks.
A release queue that checks first
Schedule a post and Good to Press proves it on a copy of the site before accepting the time. A post that would break the build is taken out of the schedule and you are told, instead of failing at the minute it was due.
WordPress import into blocks
The importer turns a WordPress export into editable blocks rather than frozen HTML. It has been proven on one site so far, so treat it as in development until three more exports have gone through it.
What "more secure" means here
It is a narrow claim, and it is checked rather than asserted. The public server holds only files: there is no CMS to log in to, no admin address to attack and no database behind the pages. The editor runs on your machine and refuses requests that did not come from itself. Each of these is a named check that runs on every release:
- No secret reaches the server. A source check fails the release if a secret is committed or about to be, and the build check refuses any file that must never be published.
- Nothing unexpected runs. After upload, a live check fails if the server serves anything executable that the build did not produce.
- No script from elsewhere. A build check fails if any page loads an asset from a remote origin, and one fails if a page uses client-side storage the site has not declared.
- Dangerous code patterns are refused. Source checks fail PHP that passes a raw request value into mail, SQL, file or include calls or runs shell commands, and fail browser code that assigns HTML from a string.
- HTTPS stays on. Live checks confirm plain HTTP redirects to HTTPS and that the site sends HSTS.
Sites that use the contact form or other PHP features still run PHP on the host. Good to Press checks that code; it does not make it disappear.
Where it sits next to Publii
Publii is a free, open-source desktop app that builds static sites locally and publishes them over SFTP or to hosts such as Netlify and GitHub Pages. It also imports WordPress exports, and it is a good choice if that is what you need.
Good to Press is aimed at a different part of the job: what happens between "I am done editing" and "it is live". If you run client sites and want every release checked, queued posts proven before their time and a bad build undone automatically, that is what this is for.
Limits in the first versionStated now so you can decide before you wait.
- Windows and Linux only. There is no Mac version yet.
- Scheduling needs the editor running. A post scheduled while your computer is off publishes the next time the editor starts, or through a host-side scheduled build on targets that offer one.
- No client self-editing. You edit the sites. Letting a client edit their own is planned for a later version.
- No Drupal import. Importing from WordPress is built; Drupal is not planned yet.
- Hosts. Uploading over SFTP/SSH comes first. Netlify, Cloudflare Pages and GitHub Pages are planned.
Three minutes, start to finish
A short walkthrough is coming: edit a page, schedule a post, watch the gates run and see a bad release undo itself. It will be embedded here once it is recorded.
Hear when Good to Press is ready
Join the waitlist and tell me what you would use it for. Signups are counted, and each one shapes what gets built first.