Skip to main content

​
First-Release Checklist

Use this checklist before the first public BLIPS docs publish.

​
1. Mintlify preview validation

  • import or connect the repo in Mintlify
  • confirm a .mintlify.app preview URL is created
  • confirm docs.json navigation matches the intended first-release structure
  • confirm generated OpenAPI pages appear only for the approved first-release endpoint set
  • confirm authentication, webhooks, reference/overview, reference/playground, and demo/* pages render in the expected locations

​
2. docs.blips.network binding

  • add docs.blips.network as the Mintlify custom domain
  • create the required Cloudflare DNS record for docs
  • confirm SSL provisioning completes
  • confirm the public docs open on the custom domain before announcing the site

​
3. Cloudflare DNS expectations

  • docs.blips.network should point to Mintlify using the DNS target Mintlify provides
  • demo.blips.network should not be bound until the BLIPSmvp runtime exposure path is ready
  • keep the website, docs, and demo surfaces on separate subdomains with clear ownership

​
4. When to enable real Try it

Enable real public Try it only after:
  • placeholder OpenAPI servers values are replaced
  • the public and/or sandbox hosts are stable
  • auth rendering is verified in Mintlify
  • request routing expectations are confirmed for the intended environment
Until then, keep the Reference previewable and generated Playground pages visible, but do not present them as live execution against real BLIPS hosts.

​
5. When to bind demo.blips.network

Bind demo.blips.network only after:
  • the BLIPSmvp runtime is available on a stable host
  • Cloudflare Tunnel or another approved exposure path is ready
  • any gating or safety controls for the demo surface are in place
  • the docs and website entry links are ready to point to the public demo hostname