Skip to Content
Service offering

Documentation as Code

Documentation that lives outside your codebase is documentation that goes stale. We build Nextra sites where docs are MDX files in your repo, reviewed in the same pull requests as the code they describe, and deployed automatically on merge. This site runs on the exact stack we deliver, so nothing here is theoretical.

NextraMDXPagefind SearchGitHub ActionsStatic ExportPR Previews

What We Deliver

A Site Set Up Once, Themed to You

Nextra with your branding, static export, dark/light mode, and search wired up from the start — not a default template with your logo dropped on top.

A Structure That Matches How People Search

Directory layout and navigation designed around how your users actually look for things, with a URL structure that’s stable before content migrates in — so links don’t rot on day two.

Components Authors Actually Use

Callouts, badges, diagram blocks, and step-by-step components registered globally — no import statements, no fighting with CSS to make a page look right.

Deploys on Merge, Previews on Every PR

Merge to main builds, indexes, and ships to S3 with a cache invalidation. Every PR gets its own preview URL posted as a comment, so reviewers see the real thing before approving.

Reference Pages That Update Themselves

Scripts that turn OpenAPI specs, READMEs, and ADRs into MDX pages at build time, so API reference content doesn’t quietly fall behind the spec it’s describing.

Hosted on Your Infrastructure

S3 and CloudFront behind your own domain, provisioned with Terraform. No documentation platform subscription, no usage-based pricing, nothing running on someone else’s servers.

How Customers Benefit

Accurate
Docs Can’t Quietly Fall Behind
When docs sit in the same repo as the code, a PR that changes behaviour has nowhere to hide an out-of-date page. Generated reference content updates the moment the spec does.
Reviewed
Someone Actually Looks Before It Ships
Branch protection and PR previews mean broken links and missing pages get caught before merge, not reported by a confused user three weeks later.
Fast
Pages Load, Search Works Offline
Static export means pre-rendered HTML and no server round-trip. Pagefind search runs client-side against a local index — no external search service to wait on.
Owned
Nothing You Can’t Walk Away From
It’s a Next.js app and a folder of MDX files in your repo — no proprietary platform to migrate off of later, no lock-in to manage.
Proven
We Run This, Not Just Sell It
CNBS’s own site runs on this exact setup. Every pattern we hand over has already been through a real deploy, not just a tutorial.

How We Work

01

Content Audit

We look at what you have today — wikis, READMEs, scattered runbooks — and design a structure that maps cleanly onto Nextra’s directory-based navigation.

02

Setup & Components

Nextra goes in with your branding and a component library your authors will actually use. Templates get built for each content type so nobody starts from a blank page.

03

Pipeline & Hosting

Production and PR-preview pipelines, plus Terraform-provisioned S3, CloudFront, and DNS. We validate one full deploy end to end before moving on.

04

Migration & Automation

Existing content moves into MDX, restructured to fit the new layout. Generation scripts for OpenAPI and ADR content get wired into the build.

05

Handover

A contribution guide and a live walkthrough — how to add a page, use the components, and run the site locally. We’re available afterward if you want us, not because you have to.


Ready to fix documentation for good?

Let’s build a docs site your team will actually keep updated.

Tell us what you’re documenting today and where it lives — we’ll design a Nextra site that fits into your existing workflow instead of sitting next to it.

Get in touch →
Last updated on