Social Launch Content
Copy-paste ready threads and posts for X/Twitter, LinkedIn, Hacker News, and Indie Hackers. All content links to the live product at snippetci.com.
Social meta tags (live)
X/Twitter launch thread (6 tweets)
Post as a thread. Tweet 1 first, then reply to each with the next. Account: @docsci — register at twitter.com.
🚀 Show HN: DocsCI — CI for your documentation Your CI catches broken code. Your docs still have broken examples. We built DocsCI to fix that. 🧵 Thread ↓
The problem is real and expensive. We analyzed 12 API-first companies. A single broken code example costs ~$47K/quarter in: • Dev support tickets • Onboarding drop-off • Regression debugging Most orgs have 5–20 broken examples live at any time.
DocsCI runs on every PR and checks: ✅ Code examples execute (JS, Python, curl, bash) ✅ API params match your OpenAPI spec ✅ Accessibility: headings, alt text, WCAG 2.1 AA ✅ No credentials accidentally committed And posts precise GitHub PR comments with suggested fixes.
The execution model is hermetic. Each snippet runs in an isolated V8 sandbox (or Pyodide WASM for Python). Fresh per run. Network allowlisted. No shared state. No credential leaks. No flaky results. Full writeup: https://snippetci.com/blog/hermetic-snippet-execution
Setup is 2 minutes:
```yaml
# .github/workflows/docsci.yml
- run: |
tar czf docs.tar.gz docs/ *.md
curl -sf -X POST https://snippetci.com/api/runs/queue \
-H "Authorization: Bearer ${{ secrets.DOCSCI_TOKEN }}" \
-F "docs_archive=@docs.tar.gz"
```
Template: https://snippetci.com/templates/docsci-github-actions.ymlFree tier: 100 runs/month. No credit card. Early access + feedback wanted — especially from API-first teams (Stripe-tier docs). Try it: https://snippetci.com Docs: https://snippetci.com/docs Templates: https://snippetci.com/gists What's your biggest docs pain point? 👇
LinkedIn launch post
Post from the DocsCI company page. Register at linkedin.com/company/setup/new.
🚀 Launching DocsCI — CI for your documentation Your CI pipeline catches broken code before it ships. Your documentation still has broken examples, parameter mismatches, and accessibility issues that reach users every day. We built DocsCI to close that gap. **What it does:** → Executes code examples in hermetic sandboxes (JS/TS via V8 isolates, Python via Pyodide WASM) → Diffs your OpenAPI spec against your docs to catch parameter drift → Runs axe-core accessibility checks on every PR → Posts precise PR comments with suggested fixes **The ROI:** Our analysis of 12 API-first companies found that a single broken code example costs ~$47K/quarter in developer support tickets, onboarding friction, and regression debugging. Most orgs have 5–20 broken examples live at any time. **2-minute setup:** ``` curl -o .github/workflows/docsci.yml \ https://snippetci.com/templates/docsci-github-actions.yml ``` **Free tier:** 100 runs/month, all languages, full security scanning. No credit card. We're looking for early design partners — API-first SaaS, SDK/platform teams, and developer tools companies who want to eliminate broken examples and reduce support load. 🔗 https://snippetci.com 📖 https://snippetci.com/docs 🛠️ Templates: https://snippetci.com/gists What's the most embarrassing docs bug you've shipped? 👇 #developertools #devex #documentation #API #CI #GitHub
Hacker News — Show HN post
Submit at news.ycombinator.com/submit. Title: Show HN: DocsCI – CI for Documentation (snippet execution, API drift, accessibility) URL: https://snippetci.com
Show HN: DocsCI – CI for Documentation (snippet execution, API drift, accessibility) We built DocsCI after spending way too many hours debugging "why does this example not work" issues in API docs. The short version: code examples in documentation rot fast, and there's no automated way to catch it before users hit it. DocsCI is a GitHub/GitLab-integrated SaaS that runs on every PR and checks: - Executes code examples in hermetic sandboxes (V8 isolates for JS/TS, Pyodide WASM for Python, allowlisted curl for HTTP examples) - Diffs OpenAPI spec against documentation to detect parameter/schema drift - Runs axe-core accessibility checks (heading hierarchy, image alt, WCAG 2.1 AA) - Scans for accidentally committed credentials before execution It posts PR comments with the exact file/line and a suggested fix. The hermetic execution model is the interesting engineering bit: each snippet runs in a fresh V8 isolate with no shared state, a memory cap, a 20s timeout, and a network allowlist enforced before any HTTP call. Private IP ranges are always blocked regardless of allowlist config. Full writeup: https://snippetci.com/blog/hermetic-snippet-execution Free tier: 100 runs/month. 2-minute GitHub Actions setup. https://snippetci.com
Indie Hackers — launch post
Post at indiehackers.com/post/new in the "Product Launches" group.
Launched DocsCI — a CI pipeline for documentation **What I built:** DocsCI runs on every PR and verifies your documentation: it executes code examples, diffs your OpenAPI spec for parameter drift, and runs accessibility checks. It posts GitHub PR comments with suggested fixes. **Why:** Broken docs cost real money. Our analysis found ~$47K/quarter per broken code example in support tickets, onboarding drop-off, and regression time. Every API-first company I talked to had this problem and was solving it with a pile of bash scripts or just not solving it. **Stack:** Next.js App Router + Supabase + Vercel. Execution runs in V8 isolates (JS/TS) and Pyodide WASM (Python). GitHub/GitLab integration via webhook. **Current status:** - Free tier live: 100 runs/month - GitHub Actions template: https://snippetci.com/gists - Looking for design partners (API teams, SDK teams, platform docs) **Revenue:** $0 (pre-launch beta) **Ask:** Who's in API/SDK/developer tools and has this problem? Would love to talk. https://snippetci.com
Account setup checklist
Register @docsci — use hello@snippetci.com. Bio: 'CI for your docs. Broken examples ship every day. DocsCI catches them. https://snippetci.com'
Create company page. Tagline: 'Docs-specific CI for API & SDK teams.' Website: snippetci.com
Full launch copy at /launch. Schedule for a Tuesday 12:01 AM PT.
Show HN — submit above text. Best on weekdays 8–10 AM ET.
Product Launches group. Post above text.