HELIX LABS · SAAS
Developer docs platform with instant search and versioning.
Shipped MDX pipelines, semantic search, and release-channel versioning so enterprise API teams stopped treating documentation as an afterthought.
- Client
- Helix Labs
- Sector
- Web Development · SaaS
- Timeline
- 6 weeks migration + 4 weeks polish
- Services
- Docs architecture, search, CI for content
The challenge
Enterprise buyers read docs before they read marketing
Helix sells APIs to regulated teams. Their docs lived in a static generator that could not express versioning cleanly, search returned stale snippets, and internal writers avoided publishing because the build was fragile. Sales engineers became the human search index — not scalable.
The VP Engineering asked for a credible migration before a flagship conference — six weeks for parity, four for polish. No downtime on public URLs. Maria led engineering; we paired with their developer advocacy lead from day two.
We rejected “move everything to a wiki” pressure from an internal tools team. The constraint was auth-aware docs with the same SSO model as the product console.
Our approach
Docs as code, with editorial guardrails humans actually follow
Framing. Documentation is a release artefact, not a marketing pamphlet. That meant CI gates, preview environments per PR, and owners on every nav section.
Architecture. Next.js + MDX with remark plugins for link checking and code sample extraction. Algolia indices split by release channel; middleware routed enterprise tenants to the correct index without leaking prerelease content.
Phasing. Week 1–2: inventory + redirect map. Week 3–4: MDX migration with automated diff reports for SMEs. Week 5–6: cutover behind a flag; week 7–10: search tuning and snippet design.
Judgment. We insisted on deleting duplicate pages instead of hiding them — politically spicy, SEO-correct for developer properties.
The outcome
Engagement rose; onboarding calls shortened measurably
Authenticated docs weekly active readers rose 62% after launch, while median time-to-first-call on API onboarding tickets dropped 34% using Helix’s support taxonomy. Migration landed in the committed six-week window; search cluster maintained 99.2% uptime during the conference spike.
Developer advocates resumed publishing because the pipeline felt like product engineering. Helix retained us lightly for index tuning; the programme closed with a contributor guide their open-source community adopted.
Results
Results in numbers
- docs engagementweekly active readers on authenticated docs
- +62%
- time-to-first-callsupport median for API onboarding tickets
- -34%
- migrationMDX cutover from legacy static generator
- 6w
- Search uptimeAlgolia cluster SLO during peak conference week
- 99.2%
What we learned
What surprised us — and what we changed mid-flight
Writers hated the first lint rule set — too noisy. We dialled rules back and shipped warnings before errors, which improved adoption. We underestimated how often legal needed redacted examples; we added a fenced “synthetic payload” pattern mid-programme.
Next time we would prototype search snippets with real customer questions in week one, not week seven. We also learned to schedule content freeze windows earlier around conferences.
Tech stack
What shipped in production
- Next.js
- MDX
- Algolia
- Vercel
Gallery
