Docs that stay in sync with main

Three documents your team actually needs. Generated from your repos.

User guide, technical doc, release notes — kept in sync with main.

docs.example.com/user-guide
Get started

Introduction

Klevox Context turns your repositories into a hosted documentation site for the audience you choose. Connect your GitHub organization, pick the audiences that matter, and we generate a site per audience on every merge to main.

How it works

  • • Install the GitHub App once at the org level.
  • • Group the repos that make up one product into an Application.
  • • Choose audiences — end users, engineers, release readers.
$ klevox connect github.com/acme/api
The stake

Docs as a chore — or docs as an output of your code?

Today

Someone writes the docs. The code moves on. The docs rot. The team stops reading them.

commit
docs untouched
drift
With Klevox Context

Every merge to main regenerates the docs that mention what changed.

commit
docs regenerated
live

Your docs, your platform.

Publish to Starlight Astro, Mintlify, GitBook, Docusaurus, or our hosted site. No lock-in, no migration.

The three documents

One Application. Three audiences. Three hosted sites.

Pick which audiences you need. Each gets its own generated documentation site, with its own URL.

End users

User Guide

How to install, configure, and use your product. Public by default.

docs.example.com/guide
Get started

Installation

Install the CLI with a single command. Works on macOS, Linux, and Windows.

npm install -g @acme/cli

Verify the install by running acme --version.

View sample →
Engineers

Technical Doc

Architecture, modules, internals. Private by default with link-share.

docs.example.com/tech
Architecture

Request lifecycle

Every request flows through the edge gateway before hitting application services.

export async function handle(req) {
const ctx = await resolve(req)
return router(ctx)
}
View sample →
Release readers

Release Notes

What changed, when, and why. Updates on every merge to main.

docs.example.com/releases
v1.4.0FeatureMay 14

Workspace SSO via Okta.

v1.3.2FixMay 6

Webhook retry backoff corrected.

v1.3.1FixApr 29

Faster build cache invalidation.

View sample →
How it works

From repo to hosted docs in five steps.

No configuration. The GitHub App handles the rest.

  1. acme-inc
    api-platform
    Project name
    01Create a project

    A workspace for the docs you’re about to ship.

  2. KlevoxInstalled
    github.com/acme-inc
    12 repositories
    02Connect GitHub

    Install the Klevox GitHub App once at the org level.

  3. api
    web
    worker
    infra
    03Select repositories

    Pick the repos that make up your product.

  4. 04Generate

    We parse, render, and publish your hosted docs.

  5. docs.acme-inc.ioLive
    05Live doc site

    Your docs, hosted and kept in sync with main.

Always current

Your docs always reflect what's on main.

Every merge to main triggers a regeneration of the docs that mention the changed code.

Main branch only. No stale snapshots. No manual updates.

PR merged to main
Regenerating affected docs
Docs updated — live

Frequently asked

The short answers. Book a demo for the long ones.

Stop writing docs your team will outdate.

Join the waitlist for Klevox Context.

Built by the team at Klevox Studio.