Aller au contenu principal

Rolling back a publish

You publish, the live site looks broken, and you need to revert. Every Docsio publish creates a snapshot — rolling back is one click.

The fast path

Project settings → Versions → find the previous publish in the list → click Roll back.

Confirms in a modal. Live site reverts within ~60 seconds. Version history keeps everything; the rollback itself becomes a new entry, so you can roll forward again if you change your mind.

What gets rolled back

Everything in the project's project_files for that snapshot:

  • Page content (the markdown).
  • Sidebar config (_category_.json files).
  • Theme config (docsio.json — colors, fonts, navbar items).
  • Static assets (logo, favicon, images you uploaded).

What does NOT roll back:

  • Custom domain DNS — the domain stays pointed at the same place. (You probably don't want to roll this back anyway.)
  • Team members — adding/removing teammates isn't versioned.
  • Subscription state — billing isn't versioned.
  • Analytics history — past visitor data is preserved across rollbacks.

Snapshot retention

  • Free plan: the last 7 publishes are retained.
  • Pro plan: unlimited history.

Older snapshots on the free plan auto-delete in FIFO order — the moment you publish your 8th time, snapshot #1 is gone. If you might want to roll back to a specific version, tag it before it ages out.

When rollback isn't enough

A few scenarios where rollback alone won't fix the issue:

Database/secret leaked into a published doc. Roll back is necessary, but you also need to:

  1. Roll back to a clean version.
  2. Manually scrub the .md files in your sandbox.
  3. Re-publish.
  4. Rotate any leaked secrets externally — they're already in search engine caches, AI training data, etc.
  5. Contact support@docsio.co to wipe the leaked snapshot from version history (we can do this for you).

Pushed bad content via GitHub Sync. Roll back the Docsio version and push a clean commit to your repo. Otherwise the next sync will re-introduce the bad content.

Custom domain went down. Not a rollback issue — check DNS in project settings → Domains. See Custom domains.

What rollback can't fix

  • A typo in your docsio.json that broke navigation across all versions. (Re-edit in the editor; rollback then re-edit.)
  • Pages that have been hard-deleted (not via the editor — directly in your sandbox terminal). Hard-deleted files aren't in project_files and won't be in any snapshot.
  • Customer data or analytics — those aren't versioned content.

Test your rollback path before you need it

We've seen teams have an outage and learn for the first time that they don't know how to roll back. Avoid this:

  1. Make a small, clearly-labeled test edit ("Test rollback — temporary").
  2. Publish.
  3. Roll back to the previous version.
  4. Confirm the test edit is gone.

Two minutes of work and you'll never panic about it again.