Context links on public sites
A plain link from your app to the help for a context key, for public sites: no token, no script. The site resolves the key for anonymous visitors and redirects to the topic.
Routes
| Route | What it does |
|---|---|
GET /context/app/key | Resolves the key as described in How a context resolves, and its fallback rules (the key, its parents, then the app default) in anonymous visitors' view, and answers 302 to the topic page, with #fragment when the key points at a section. |
GET /context/app?path=path | The same, for a path of your app, mapped to a key by the routes in help-contexts.yaml. Without a key or path, the app's default. |
<a href="https://docs.example.com/context/console/settings.sso">Help</a>What they answer
- Always the anonymous view, even for a signed-in reader, so the same link opens the same topic for everyone. A key whose targets are all hidden from anonymous visitors falls back, and never names a hidden topic.
- At the version the request is served: the public set's version, or the one the visitor chose with the version picker. See Let readers choose the version they read.
- 404 when nothing resolves or the app is unknown.
- On a private site, always 404: these links reveal nothing there. Use the help panel or the JSON API with a token instead (Embed the help widget, Help JSON API reference).