EP Static Publish
EP Static Publish lets you keep editing in PageMotor while visitors get plain files from Cloudflare. It draws every public page as a signed-out visitor sees it, uploads only what changed, and can republish by itself after you save.
It can also send one page, with its own files, to an address on the ElmsPark edge.
Published by ElmsPark Studio.
Overview
Section titled “Overview”There are two places a page can go.
- Your own Cloudflare Worker. The whole site is published as static files to a Worker on your Cloudflare account. The first publish creates the Worker and a workers.dev preview address. The last five versions are kept, so you can put an earlier one back.
- The ElmsPark edge. One page goes to an address on the edge, as a new version. This is for landing pages, such as a page an advert points at.
Requirements
Section titled “Requirements”- PageMotor 0.11.5 or later
- A Cloudflare account, and an API token made from the Edit Cloudflare Workers template, scoped to that account
- For the edge: an edge address, its page store ID and a brand name, which ElmsPark gives you
Installation
Section titled “Installation”ep-static-publish.zipcomes with an EP Suite licence. ElmsPark supplies it directly (see EP Suite plugins); after install it updates through your site’s Updates screen.- Upload it via Plugins → Manage Plugins. Activate.
- Open the plugin’s settings and fill in the Cloudflare group, then save.
Publishing the whole site to your Worker
Section titled “Publishing the whole site to your Worker”Fill in the Cloudflare group:
- Account ID, the long hex ID in your Cloudflare dashboard address.
- API token. It is stored encrypted. Leave the box blank to keep the saved one.
- Worker name. Any name made of letters, numbers and hyphens. It is created on your account on the first publish.
- Public address, the host name visitors use, such as
www.example.com. Pages are drawn with this address so links and canonical tags are right.
Then use the buttons in the Publish group:
- Check site draws every page without uploading anything, and lists the pages that need PageMotor when someone visits (forms and live widgets).
- Publish now draws the site and uploads only the files that changed.
- Restore puts one of the last five versions back.
Other settings:
- Preview mode tells search engines not to index the static copy, for use while testing on workers.dev.
- Leave out these pages, one path per line, for pages that depend on a link, a login or a query string.
- Auto-publish republishes a minute after your last content save or design change.
- Render address (advanced) is where the server reaches itself. The default is
https://127.0.0.1.
Pages with forms or live widgets
Section titled “Pages with forms or live widgets”With Relay off, publishing stops while any page has a form or live widget, because it would not work as a plain file.
With Relay on, such pages keep working:
- By default the page stays a plain file. A small script on it sends only that page’s own requests (form posts, live data) through Cloudflare to your PageMotor site, and fetches fresh security tokens when the page loads.
- With Relay whole pages ticked, those pages are served entirely from PageMotor instead.
The relay needs your PageMotor site to stay up. Editor address (relay) is where Cloudflare reaches it. The relay never opens your admin, API, MCP or OAuth addresses to the public.
Publishing one page to the ElmsPark edge
Section titled “Publishing one page to the ElmsPark edge”Fill in the Edge (one page) group:
- Edge address, the host name the edge serves the page on, such as
go.example.com. The edge must already be set up for it. - Edge page store ID, 32 characters, which ElmsPark gives you. The API token above needs Workers KV Storage: Edit, which the Edit Cloudflare Workers template includes.
- Edge brand, the name the edge files the page under (lower-case letters, numbers and hyphens).
- Page to publish, the path of the page on your site, such as
/spring-offer/. - Edge path, where it goes on the edge address. Leave it blank to use the same path.
- Fallback address, a full
https://address where a visitor can still buy. The edge sends visitors there whenever it cannot show the page.
Then press Publish page to edge in the Publish group.
What travels with the page
Section titled “What travels with the page”The page is drawn as a signed-out visitor sees it. Its stylesheets, scripts, images and fonts go into the version too, including the images and fonts its stylesheets use, and the page is pointed at those copies.
Links to your site’s other pages point at your public address. Protected uploads never leave your site.
When the edge refuses a page
Section titled “When the edge refuses a page”The page is refused before anything is sent if:
- it is very short, or has no buy link marked with
data-bridge. The edge would take such a page down within a minute; - the edge does not serve that address yet;
- it has a form or live widget, and the edge address has no relay to your site;
- the page and its files come to more than 20 MB.
Publishing over something else
Section titled “Publishing over something else”If something not published from your site is at that address, or it changed since you last published it, the button stops and says so. Tick Replace a page not published from here to publish over it. The edge keeps the old version in its history.
The address only moves to the new version once every file is stored. Afterwards the plugin reads the page back to check it arrived. The edge can take up to a minute to show the new version everywhere.
For agents
Section titled “For agents”EP Static Publish registers these actions under EP_Static_Publish for admin agents over the PageMotor API and MCP:
| Action | What it does |
|---|---|
static-preflight | Draws every page without uploading, and reports the pages that need PageMotor when someone visits. |
static-publish | Publishes the site to your Worker, uploading only what changed. |
static-status | Progress of the current or last job, the preview address, whether the public copy is behind, and the stored versions. |
static-rollback | Puts an earlier Worker version back. 1 is the version before the current one. |
static-edge-publish | Publishes one page to the ElmsPark edge. Optional source, path and replace. |
Each starts a background job. Read the result with static-status.
Troubleshooting
Section titled “Troubleshooting””Publishing stops and lists pages with forms”
Section titled “”Publishing stops and lists pages with forms””Those pages need PageMotor when someone visits. Turn Relay on, or leave the pages out.
”The edge says the page has no data-bridge marker”
Section titled “”The edge says the page has no data-bridge marker””The edge keeps a page up only when it carries a buy link marked with data-bridge. Add one to the page, then publish again.
”The edge does not serve this address yet”
Section titled “”The edge does not serve this address yet””The edge address must be set up on the edge before a page can go there. Ask ElmsPark to add it.
Feedback and corrections
Section titled “Feedback and corrections”For a question, a bug report or a feature request, open a ticket at help.elmspark.com. A real person, helped by AI, writes the reply. Usually within a few hours.
Changelog
Section titled “Changelog”- Changing this plugin’s settings over the API now needs an admin token. Producer tokens and AI apps connected through a producer account can still read the settings. Saving from the Admin screen works exactly as before.
- Now on the ElmsPark update channel. This is the first release you can install and update from your site’s Updates screen. It includes everything below from 0.1.0 to 0.3.1.
- Publish one page to the ElmsPark edge. A new “Publish page to edge” button sends one page of your site to an address on the ElmsPark edge, as a new version, then points the address at it. The page is drawn as a signed-out visitor sees it.
- The page’s own files go with it. Its stylesheets, scripts, images and fonts, including the images and fonts its stylesheets use, travel inside the version. Links to your site’s other pages point at your public address. Protected uploads never leave your site.
- Checks before anything is sent. The page is refused if the edge would take it down (very short, or no buy link marked with data-bridge), if the edge does not serve that address yet, or if it has a form and the edge address has no relay to your site. A version over 20 MB is refused too.
- No silent overwrites. If something not published from your site is at that address, or it changed since you last published it, the button stops and says so. Tick “Replace a page not published from here” to publish over it; the edge keeps the old version.
- Never half-published. The address only moves once every file is stored, and the plugin reads the page back afterwards to check it arrived.
- For agents: the same publish is the new action static-edge-publish.