Zum Hauptinhalt springen

One-click publish

Publishing in Docsio is a single button. No staging environment to manage, no build pipeline to maintain, no deploy keys. Click → live.

How it works

When you click Publish (top-right of the editor):

  1. The current state of every page in your project gets snapshotted.
  2. Docsio builds your site — pages, search index, llms.txt.
  3. The build deploys to a global CDN at the URL you've configured.
  4. Within ~60 seconds, visitors see the new content.

You see each step in the publish modal. The whole thing usually finishes in 30-90 seconds.

Where it goes

By default, every project has a free subdomain at <your-slug>.docs.docsio.co. Always available, SSL automatic.

To use your own domain (docs.yourcompany.com), see Custom domains. Free on every plan.

Versions on every publish

Pro projects automatically save a version on every publish — see Version history for rollbacks.

With GitHub sync on

If you've connected a GitHub repo, Publish does an additional step: it commits your current draft to the configured branch as a [docsio]-tagged commit, then runs the build. See GitHub sync for details.

Rate limits

  • Free: 10 publishes per project per hour, 100 per month.
  • Pro: 30 per hour, no monthly cap.

If you hit the rate limit, the publish button is disabled with a countdown to the next available slot. You're rarely going to hit it — it exists to prevent runaway loops.

What if a publish fails

Failures are uncommon but visible. The publish modal shows the failure step with a short error and a retry button.

Most failures are transient (CDN provisioning, DNS race conditions). Retry usually works.

If it keeps failing, the previous successful version stays live — your real site is never broken by a failed publish.

Common patterns

  • Publish whenever, then iterate. No reason to batch changes. Each publish is fast.
  • Use version history as your "draft." Edit freely; if you regret a publish, roll back from version history.
  • Republish after settings changes. Theme tweaks, branding edits, and config changes need a publish to land on the live site.