Every help text in your product, from tooltip to procedure. Write it once. Publish by key. Update without a release.

A settings screen with a tooltip, a field-help popover and a help panel, each fed by a key such as settings.api-keys, all pointing back to one help source

Type a tooltip. Publish it. Call it from your app.

The sentence you type below gets stored, published and served from the same endpoint your product would call. You get the URL, the code that reads it, and seven days to try it in your own build.

Editoreditor.save.button
Topic
Saving your work
Tooltip
Save

Type in the sentence. The highlighted word is a managed role, edited on the right.

1 change to publishPublish
Managed role
preview
NameRole
HTML representation
Your application
Hover the button to show the tooltip
data-help-key="editor.save.button"
Updating…

Everything here stays in your browser. Nothing is sent, stored or measured.

Now do it for real

The panels above are live, but they stay in your browser. Press the button and the same sentence gets saved, published and served from a real address you can call from your own development environment. No account needed.

Bring in what you already have. Turn it into topics, keep what matters, bin what doesn't.

Up your help game.

Bring your help texts together, from the one-line tooltip to the full procedure. Your app fetches them by key, and a writer publishes without a release. Writing is free, and each collection can have five help keys published without a plan.

Create your account
Stop hardcoding help

Articles on in-app help, and what it costs to keep it in your codebase.

We store your address to send you this, and nothing else. Unsubscribe in one click.