> ## Documentation Index
> Fetch the complete documentation index at: /docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Publish

> Publish saved work from Fimo Studio and open the live site.

Use Studio to publish work that is already saved to the site. Publishing makes the site's configured Production source revision public. New sites use `main`. Publishing is separate from Preview.

## Publish from Studio

**1. Review Preview**

Check the final pages and content in Preview. Resolve any remaining Branch work before you publish.

**2. Open Publish**

Select **Publish** in the top-right of the site header. The panel shows the publication status, live URL, active
custom domains, and last published time when available.

**3. Publish**

Select **Publish** in the panel. Wait for the status to finish before you close the site or share the URL.

**4. Open the live site**

Open the published URL and repeat your key page, link, form, mobile, title, and description checks.

> [!NOTE]
>
> If you cannot publish, the panel tells you that you do not have permission. Ask a site owner to review your site
> access.

## If a publication fails

When a publication does not finish, your live site keeps the version it already had. You do not need to keep the panel open to find out:

* **Publish** shows **Latest update failed** and what went wrong, until a newer publication finishes. If your site was published before, it also says the previous version remains the active release.
* The person who published and the people who manage the site get an email, unless they turned off **Publication failures** in **Account settings → Notifications**. Its **Open Publish** button opens this panel with the failure explained, so you can publish again from there.

To read the build output, run `fimo publish list` to find the attempt and `fimo publish logs <id>` to print its log, when your role allows it. See the [CLI reference](/docs/reference/cli.md).

## Publish again after changes

Saved changes do not update the public site. Review the new state in Preview, then publish again to replace the live version.

If you are working in the repository and need to push local changes first, use the [CLI deploy and publish flow](/docs/deploy/overview.md). You do not need to repeat the Studio procedure afterward.

## Before launch

* Review titles and descriptions in **Settings → SEO**.
* Confirm the intended URL in **Settings → Domains** or with the CLI.
* Keep a useful restore point in [Version history](/docs/studio/version-history.md).
* Follow the [launch checklist](/docs/environments/launch-checklist.md) for live verification.

## What's next

> [card] [Launch checklist](/docs/environments/launch-checklist.md)
>
> Verify the site before and after publishing.

> [card] [Version history](/docs/studio/version-history.md)
>
> Restore an earlier state if needed.

> [card] [Custom domains](/docs/deploy/custom-domains.md)
>
> Set the public address.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.