Just Publish

Put a website live at a public URL. Use this when the user wants to publish, launch, or get a page online - e.g. 'I need a website', 'put up a page for my business', 'make this live'. Takes static fil…

Read the files of a site you already published, so you can make a targeted edit instead of rebuilding the whole site from memory. Returns a complete manifest (every file's path, size, content-type, sh…

Change one or a few files of an already-published site, leaving every other file untouched (a merge - unlike deploy, which replaces the whole site). Ideal for small edits: fix a typo in index.html, sw…

One-screen orientation: Just Publish turns static files into a live public URL with no build step and no git. On this endpoint the person is identified by the email address passed to deploy. Explains …

The recommended loop for changing an existing site: get_site_files to read current state + version, edit, update_site_file with expected_version. Covers conflicts and when to fall back to deploy.

Rules for the files array: relative paths only (no .., no leading /), text vs. base64 encoding, per-file and per-site size caps, routing (/foo serves /foo/index.html).

Non-negotiables: every site needs index.html at root; deploy REPLACES all files (omitted = deleted) while update_site_file MERGES; the edit_token is the only way to change a site and must be saved.

Inline UI shown after deploy: a live-going-up animation, the live site URL with a "View your site" button, and (for a freshly published site) a gentle verify-your-email step.