Build in Etch. Go live on your client's own WordPress.

Approved pages go from SpecShot to the client's site as Etch drafts, then live one page at a time, with a roll back for every deploy.

The SpecShot plugin is built and waits on a test run before its release. SpecShot never hosts client sites.

Coming soon

A sample deploy to a client's own WordPress: approved pages applied as drafts, then taken live page by page.

From approved page to live page.

Four steps, each one yours to start. The client's site does the building, in Etch.

How a deploy works

Pairing a sample site: a one-time code from the project, typed into the plugin. Codes expire after 15 minutes.

The Etch Connector turns a design into real Etch blocks and styles that stay editable in the builder.

The whole design lands in one root block, and a rebuild replaces only that block.
Class rules become Etch class styles, and the design's tokens become Etch variables under the project's prefix.
The site's own styles and variables win. A class the site already uses differently is renamed.
Components, slots and loops carry over where the site's Etch supports them, with plain blocks where it does not.
Links between project pages become WordPress permalinks.
Every build can run dry first, so you see what would change.

On a site with Automatic.css, the build follows the site's settings instead of fighting them.

Design values are written as Automatic.css variables with the design's value as the fallback, so the site's settings win.
The plugin's brand pass sets the five color roots and the heading and text fonts, and leaves the spacing and radius scales to Automatic.css.
Every brand pass shows a dry-run diff first, takes a backup, and can be restored.

SpecShot builds the pages. The site, the host and the final click stay with you.

SpecShot never hosts a client site and never holds a WordPress password.
The plugin pulls its work from SpecShot. The only call SpecShot makes to the site is a wake-up with no content.
Every package is signed, bound to one site, and cannot be replayed.
Going live and rolling back are a person's click in SpecShot. No agent and no MCP tool can do either.
When a page goes live over an existing one, WordPress keeps the old content as a revision, and Roll back restores it.

When can I use it?
The plugin is built and waits on a test run on a real Etch and Automatic.css site before its release. It is not released yet, and this page will say when it is.
Does SpecShot host my client's site?
No. The site stays on the client's own WordPress and host. SpecShot never hosts a client site and never holds a WordPress password.
Do I need Etch and Automatic.css?
Etch is needed for the build panel. Automatic.css is optional: when the site has it, the build follows its settings.
Can my AI agent publish to the site?
No. An agent can design and revise pages in SpecShot. Going live and rolling back are always a person's click.

Brief a project and have your agent build it now. The WordPress deploy follows when the plugin is released.