Home
verso.md
Get started
For Support & Content

Help docs that
never go stale

Your help center, knowledge base, and support articles live in the same repo as the product. When the code changes, the docs are right there to update. No more 3-day gaps between shipping a feature and telling customers how to use it.

Support articles that reference real code

help/setting-up-sso.md
Published
1# Setting Up SSO
2
3## Prerequisites
4- Admin role on your organization
5- SAML provider credentials (Okta, Azure AD)
6
7## Steps
81. Go to **Settings > Authentication**
92. Click **"Add SSO Provider"**Support
103. Paste your SAML metadata URL
114. Map user attributes:
12 - `email` → User email
13 - `displayName` → Full name - `role` → Organization role

You've seen this before

Help docs always fall behind the product. Not when they live in the repo.

Before

Feature ships Monday. Help article updated Thursday. Customers confused for 3 days.

With verso.md

Feature and help article ship in the same PR. Zero gap.

Before

Support writes "click the Settings button" but Engineering renamed it to Preferences two sprints ago.

With verso.md

AI reads the actual UI code and suggests the correct label automatically.

Before

Help center lives in a CMS. Nobody remembers to update it when the product changes.

With verso.md

Help content lives in the repo. The PR won't merge until docs are reviewed too.

Code changes, docs update

Renamed an API field? The help article referencing it is in the same repo. Update both in one PR.

AI-powered accuracy

AI reads your actual code when helping you write support content. No more screenshots of outdated UIs.

Support + Engineering, same tool

Support writes the article, engineering reviews the technical accuracy. One PR, one workflow.

Ship fixes and docs together

Bug fix on line 42, updated help article on the same branch. Customers see the fix and the explanation at the same time.

Ask the code, write the article

Support doesn't need to bug engineering for every detail. The AI terminal reads the codebase and helps you write technically accurate help content.

AI Terminalconnected to acme/app
you→What settings are available on the SSO config page?
Looking at `src/app/settings/sso/page.tsx`... The SSO config page has these fields: - `metadataUrl` (SAML metadata URL) - `entityId` (Service Provider Entity ID) - `attributeMapping` with keys: email, displayName, role - `enforceSSO` toggle (requires all users to sign in via SSO)
you→The help article mentions "Settings > Security" but I think that changed. Where is it now?
You're right. The route moved in the last release. It's now at `/settings/authentication`, not `/settings/security`. The nav label is "Authentication" (see `src/components/settings/nav.tsx` line 34).
you→Update the article with the correct path
Updated "Settings > Security" to "Settings > Authentication" in your article.

Docs and code, always in sync

01
Code changes
Feature ships or bug is fixed
02
Docs flagged
Related .md files in the same PR
03
Support updates
Edit the help article in verso.md
04
Both ship
Code + docs merge together

Ready to try it?

Sign in with GitHub and start writing docs that live next to your code.

Get started, it's free