Skip to main content
Publishing makes the site’s saved changes public. Primo generates HTML, CSS, and JavaScript from your blocks and content and serves them on the connected domain.

​
Watch the workflow

​
Publish and view the finished site

Watch the workflow in Primo. Download video · Download captions
  1. Open Publish to review your changes.
  2. Choose Publish changes to build the site.
  3. View site opens the published result.

​
How It Works

When you publish, Primo:
  1. Compiles all blocks to optimized JavaScript
  2. Generates static HTML for every page
  3. Copies assets to the output directory
  4. Deploys files to your domain
Your site is accessible at https://yourdomain.com/ while the admin stays at https://yourdomain.com/admin/.

​
Publishing a Site

You need publishing access to a deployed site with a connected hostname. Local primo dev uses previews; deploy the CMS or build static files to make the site public. Save open content dialogs before publishing.
1

Click Publish

In the toolbar, click “Publish” (or press Cmd/Ctrl + P).
2

Confirm

In the dialog, click “Publish Changes” to confirm.
3

Wait for completion

Wait for the success message. Timing depends on site size, network speed, and your browser.
Open your public hostname in a separate tab. Check the homepage, a nested page, images, and navigation to confirm the saved changes are live.

​
What Gets Published

Every publish includes:
  • All pages
  • The block code and content needed to render your pages
  • All assets (images, files)
  • Site configuration
Even if you only change one thing, Primo rebuilds the entire site to ensure consistency.
Publishing applies to the whole site, including saved changes on other pages. By default, a CLI push updates the hosted draft without publishing. Review it before publishing.

​
Publish from the CLI

With CLI 0.2.1 or later and a server that supports the publication API, use primo publish to publish saved CMS changes, or primo push --publish to upload local files and then publish. Select one site with --only my-site when running from a workspace root. See Publish with the CLI for authentication, server requirements, and status checks.

​
Auto-Save Behavior

These changes auto-save:
  • Inline content edits
  • Adding/removing blocks
  • Reordering blocks
Manual save required for:
  • Block editor (code/fields)
  • Section editor
  • Site settings editor
Always save in the block/section/site editor before publishing.

​
Troubleshooting

Publish fails with an error:
  • Check the error message for the specific block or page causing the issue
  • Review recent changes
  • Fix the issue and try again
Changes don’t appear on live site:
  • Hard refresh your browser (Cmd/Ctrl + Shift + R)
  • Check any reverse-proxy or CDN caching rules; bypass caches for /admin and /api
  • Verify you clicked “Publish Changes” in the dialog
Images not loading:
  • Verify uploaded images resolve, or that external image URLs are reachable over HTTPS
  • Republish to ensure assets were copied

​
Next Steps

Using the Editor

Learn to create and edit pages.

Site Configuration

Configure shared content, styles, and metadata.