UlikaDocs
Open Ulika

Getting started

  • Ulika documentation
  • How Ulika works
  • Requirements
  • Quickstart

Connect a site

  • Connect from the dashboard
  • Connect with the CLI
  • Connect with an AI agent
  • Approving a connection
  • Private previews
  • The GitHub App
  • Connect Vercel

Integrations

  • GitHub integration
  • Vercel integration
  • Netlify
  • Claude Code
  • Codex
  • MCP tools

Editing

  • The editor
  • The style panel
  • Sections and pages
  • Mobile preview, autosave and drafts

Publishing

  • Publish your changes
  • History and restoring a version
  • When a publish fails

Team

  • Team roles
  • Inviting people

Projects

  • Project settings
  • Delete a project
  • Website code

Troubleshooting

  • Needs attention reasons
  • Vercel problems
  • GitHub problems
  • CLI errors and exit codes
  • Frequently asked questions

Security and privacy

  • Security and privacy overview

CLI

  • CLI reference
  • CLI changelog

Publishing

Publish your changes

How publishing works in Ulika: the review dialog, what happens after you click Publish, how quickly visitors see changes, and what to do when a publish waits.

Last updated October 10, 2026

Editing in Ulika changes a draft. Publishing is the step that puts the draft on your real website. Ulika shows you exactly what will change before anything goes out, and then waits until your live site proves it is serving the new version.

Who can publish#

Publishing needs the publish permission, which the owner and editor roles have. Viewers cannot publish. If your role cannot, the Publish button is disabled and its tooltip says "Your role cannot publish changes." See Roles.

Start a publish#

There are two places to start:

  • In the editor, click Publish in the top bar. Ulika first saves any pending edit. If it cannot, you see "Your edits need to be saved before publishing." Use Retry in the top bar and try again.

  • On the project's own screens, the Publish button. When there is nothing to publish it is disabled and says "Everything is already published."

Review the changes#

The dialog is titled Ready to publish? and says "3 changes will be published to your website." (with your real number). Below is every change, grouped by page or area. Each row shows the old value crossed out, an arrow, and the new value, so you can spot a mistake before it is public. Search-details-only changes read "Search details updated." and items read "Item content updated."

Two buttons at the bottom:

  • Cancel closes the dialog. Nothing is lost; your drafts stay saved.

  • Publish 3 changes (the number changes) starts the publish. With one change it reads Publish 1 change.

Discarding all draft changes#

Under the list, Discard all draft changes throws away every unpublished change in the project at once. It asks "Discard all 3 draft changes? This cannot be undone." with Keep them and Discard. Afterwards you see "Draft changes discarded. The editor now matches the live website." This needs edit permission. To reset a single page instead, use Go back to the live version in the editor (see Mobile preview, autosave and drafts).

What happens after you click Publish#

While Ulika works, the button reads Building your site… and the dialog title changes to "Building your site…". It explains: "Usually about 30 seconds. You can close this window; it finishes on its own." Behind the scenes:

  1. Freeze: Ulika takes a snapshot of the draft as it is at that moment. Edits you make afterwards do not sneak into this publish.

  2. Send it to your site's build: depending on how your site is connected, Ulika either commits one small file, .ulika/content.json, to your GitHub repository (so your host rebuilds on the push), or triggers your Vercel deploy hook. Either way your code is not changed; only content values are.

  3. Wait for proof: Ulika checks your live site until it serves exactly this snapshot. Only then does the publish count as done and show up in History.

It checks every 1.5 seconds for the first 90 seconds, then every 3 seconds up to 5 minutes, then every 5 seconds. If a build takes longer than 90 seconds the dialog says "Still building your site…" and "This is taking longer than usual. Your changes are saved and it will finish on its own." Ulika stops watching after 15 minutes. If that happens you see "Publication is still being checked. Reopen Publish to resume checking." Your drafts are not lost.

You can close the dialog at any time. Ulika also checks pending publishes in the background: when Vercel reports a deployment is ready, and on a regular sweep.

When it succeeds#

A toast says Live on your website and "Search engines update in about 30 seconds." The dialog closes after the rebuild is confirmed. If the changes were shown early (see the next section), you are not told twice.

How fast visitors see it#

Many sites need a rebuild before a change shows. The rebuild typically takes tens of seconds, but the real time depends on your host and project, and is not guaranteed. Ulika removes most of the waiting with an instant layer.

The instant layer#

The connector adds a small script to your published pages. Each time a visitor opens a page, the script asks Ulika once for the newest published content. If that is newer than the build the page came from, it patches the text, links, images and styles in the page in place. When the rebuilt site is ready, it already contains the same values, and the script does nothing.

What it covers, and what it does not:

Shown right awayWaits for the rebuild
Text, links, images and styles that your build marked as editableItems in collections, page search details such as titles and descriptions, fields your build has no marker for, and styles on elements the build has not marked yet

If every change in your publish is in the first column, the dialog switches to Live on your website while the rebuild is still running, with the line "Visitors see your changes now. The rebuild that search engines read is still finishing." Otherwise the dialog stays on "Building your site…" until the rebuild is proven live.

Caching: Ulika's answer to the script is cached at the edge for 5 seconds (and may be served slightly stale for up to 30 more while it refreshes), and a visitor's browser asks again after 2 seconds. These are cache settings, not promises about when each visitor sees your change.

Good to know:

  • The instant layer reads only the frozen snapshot of what you published, never your live drafts, and only plain text values and the styles Ulika accepts.

  • It does not run inside the editor.

  • A publish that is waiting for you to merge a pull request is not shown early.

  • If the rebuild then fails, the early values stop being served and visitors go back to the previous version. See When a publish fails.

  • The script is shipped unless "live" is set to false in .ulika/connector.json in your repository.

When a publish waits for you#

With GitHub delivery, two situations pause a publish until you decide. The dialog shows a notice with one main action. Your drafts are safe in both.

Waiting for the pull request to be merged#

Title: Waiting for the pull request to be merged. This happens when your repository's default branch is protected so Ulika cannot push directly. Ulika opened a pull request with your publication instead.

  • Click Open the pull request and merge it on GitHub. The publish goes live as soon as it is merged.

  • To publish directly next time, add Ulika to the bypass list of that branch's ruleset (the repository rules link in the notice opens your repository's rules page).

Your repository's .ulika/content.json was changed outside Ulika#

Title: Your repository's .ulika/content.json was changed outside Ulika. Someone edited that file on GitHub since Ulika last published. To avoid destroying their change, Ulika stops: "Nothing was published, and nothing on GitHub was overwritten. Your drafts are saved."

  • Overwrite with Ulika's version publishes your draft over that file. If it fails you see "Could not overwrite" and the reason.

  • View the commit on GitHub shows the outside change first so you can decide.

Publishing again while one is running#

If you click Publish again while a publish is still building:

  • If nothing changed since, Ulika reuses the one in progress.

  • If you saved more edits in the meantime, the new publish replaces the old one with a fresh snapshot, so nothing is left behind. The old one is closed without going live.

  • A publish waiting on a person (a pull request, or a changed file) is kept rather than replaced.

Errors when you click Publish#

MessageWhat it meansWhat to do
"Publish failed" with "There are no draft changes to publish."Nothing differs from what is live.Nothing; your site is up to date.
"Finish the verified Ulika installation before publishing to this site."The project has no working connection to publish through yet.Finish connecting the site first.
"Another publication is already in progress."Two publishes started at the same moment.Wait a moment and try again.
"Publication not confirmed"Ulika could not prove the new version is live. The reason is shown.See When a publish fails.

After publishing#

Every successful publish appears in History with who did it, when and how many changes, and you can go back to any earlier version from there.

Was this page helpful?

PreviousMobile preview, autosave and draftsNext History and restoring a version

On this page

  • Who can publish
  • Start a publish
  • Review the changes
  • Discarding all draft changes
  • What happens after you click Publish
  • When it succeeds
  • How fast visitors see it
  • The instant layer
  • When a publish waits for you
  • Waiting for the pull request to be merged
  • Your repository's .ulika/content.json was changed outside Ulika
  • Publishing again while one is running
  • Errors when you click Publish
  • After publishing
Ulika documentationFAQ · CLI reference · Terms · Privacy