Edit and deploy in-app help. Write it once. Publish by key. Update without a release.

Start free trial
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.

Start here.

See the modelCollections hold topics, topics carry Help keys, and your app asks for a key. The whole model on one page, down to what a developer does once.Read on →Bring what you haveYour tooltips, field help and error messages are already written and scattered through source. A coding agent collects them into JSON, and one import turns them into topics.Read on →Connect itOne GET returns a published topic by its key. On your side it is a single function that takes a key and returns the text.Read on →

Publish the meaning too

The HelpCCMS Pro editor: a numbered procedure in the middle, panels for inline components, cross-references, glossary and content components on the left, a properties and metadata panel on the right, and beside it a documentation site, a list of search results and a panel of JSON output.

Every plan delivers your help text to your app. Pro delivers the structure around it, in the same response.

Alongside the HTML and the plain text, a Pro response carries a metadata block:

  • The full document structure in order: sections, procedures, steps, tables, notes and code blocks.
  • Every role, cross-reference and glossary term the topic uses, and where it occurs.
  • The topic id, its type, its Help key and your own external reference.

Software can read that. A search index, a retrieval pipeline or an agent gets the same source your readers get, with the structure still attached.

Pro costs 150 euro once, for the first 1,000 accounts.

Up your help game.

Bring your help texts together. Make them better. Reduce tickets. And don't bother an engineer for a tooltip. One price per writer, unlimited reads.

Start free trial
Stop hardcoding help

One short piece a week 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.