Skip to content

Fixing publishing problems (Studio)

StudioHow-to3 min read16 views

Tagged

Publishing is normally one click; see Publishing and Sharing Your Studio Project for the happy path. When Studio refuses to publish, or the published result isn’t what you expected, work down this list.

Accessibility findings and publishing

Studio does not block publishing on accessibility findings (a project carrying open findings, a 2.4:1 color contrast and an image missing alt text, published end to end with no gate, warning, or “publish anyway” step; a “Publishing disabled: project is not compliant” gate does not exist). The checker is advisory, so run it yourself before a public launch:

  1. Open the editor’s actions strip and click Check accessibility status; pages with findings show a ! marker (see Improving Accessibility).
  2. Work through the findings popover. Each finding is a clickable row pairing a plain-language summary with the technical detail, for example “insufficient color contrast of 2.4 (foreground #ffffff, background #54afed), expected 4.5:1” or “Image elements do not have [alt] attributes”; clicking a finding selects the offending element on the canvas.
  3. Fix the findings (adjust colors, add alt text, set Aria labels under Properties → Accessibility), re-run the check until the page comes back clean, and repeat for every flagged page.
  4. Use View accessible version in the publish success dialog, or the accessible preview (see Previewing Your Project), to see the rendering assistive technology gets before you go live.

Because nothing forces the check, make it part of your publish routine rather than waiting for a gate that won’t come.

I published, but my edits aren’t showing

Publishing produces a snapshot: edits after publishing never change the live version until you publish again. Studio regenerates the static pages at the same link, so your readers’ URL never changes — check that you actually republished after the last edit before hunting for a caching problem.

The link stopped working

  • Was the project unpublished? Taking a project offline (dashboard tile → More options (…) → Settings) makes the published version inaccessible at its link immediately — the project itself, with all its edits, stays safely in your dashboard and the tile offers Publish again.
  • Are you sharing the right address? A published project lives at a link of the form https://<host>/<account>/<project>/index.html. The address in your browser bar while you’re editing is the editor, not the reader link — copy the public URL from the success dialog or the Published Link button in the top bar instead.

Publish Offline vs publishing

The Publish options dropdown also offers Publish Offline — a downloadable copy that reads without an internet connection. It is a separate output, not a stage of cloud publishing: an offline copy never appears at your project’s live link, and republishing online doesn’t refresh a copy you already downloaded. If the goal is “readers can open the link,” use the normal Publish.

Publish seems stuck or nothing happens

Watch the progress dialog — Studio generates the static pages and reports “Your project is live” when done. If the dialog stalls unusually long, reload the editor and check the dashboard tile before retrying: the tile’s state (published or not) is the source of truth. (No Studio-side stall has been observed. The known “90%” stall affects the flipbooks pipeline (Replicate/Flow) and is tracked separately on the FAQ page.) If a retry keeps failing, note the project and time and contact support rather than publishing in a loop.