Publishing

Publishing on Stipple is git push. There is no separate deploy step and nothing to remember.

The pipeline

On every push to your default branch:

1. Stipple fetches your docs folder at that exact commit.
2. The site is built — pages, navigation, and branding from docs.json.
3. The full-text search index is generated from the built pages.
4. llms.txt, llms-full.txt, and sitemap.xml are emitted alongside the site.
5. Everything uploads to edge storage and the new version goes live atomically.

Because all artifacts come from the same commit, your site, search, and agent surfaces can never disagree with each other — or with the product that shipped.

Build status

The console shows every deployment with its commit, status, and build log. A failed build never replaces the live site; the previous version keeps serving until a good build lands.

Rolling back

Revert the commit and push. The pipeline treats a revert like any other change, which means your docs history is exactly your git history.