Skip to content

docs(kno-12444): document guides toolbar#1384

Draft
scotidodson wants to merge 1 commit intomainfrom
sd-KNO-12444-document-guides-toolbar
Draft

docs(kno-12444): document guides toolbar#1384
scotidodson wants to merge 1 commit intomainfrom
sd-KNO-12444-document-guides-toolbar

Conversation

@scotidodson
Copy link
Copy Markdown
Contributor

KNO-12444: [Docs] Document guides toolbar

Summary

  • Restructured debugging-guides.mdx to provide better TOC navigation options and add guides toolbar in place of live preview documentation
  • Added full guides toolbar documentation: activation, toolbar views, status badges, eligibility/visibility indicators, focus button, and toolbar controls
  • Moved live preview to a FAQ accordion for users on older SDK versions
  • Removed the old "Testing guides" wrapper section and flattened the page structure

Changes

  • content/in-app-ui/guides/debugging-guides.mdx — restructured page; added guides toolbar section with SDK requirement callout; moved live preview to FAQ accordion; updated dashboard preview callout to reference toolbar

TODO

  • Update based on newest designs
  • Add images where helpful

@linear
Copy link
Copy Markdown

linear bot commented Apr 8, 2026

@vercel
Copy link
Copy Markdown

vercel bot commented Apr 8, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
docs Ready Ready Preview, Comment Apr 8, 2026 11:28pm

Request Review

title="SDK requirement."
text={
<>
The guides toolbar requires <code>@knocklabs/react</code> v0.11.8 or
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
The guides toolbar requires <code>@knocklabs/react</code> v0.11.8 or
The guides toolbar requires <code>@knocklabs/react</code> v0.11.13 or

This is the latest version now.

Comment on lines +52 to +54
- **All guides.** Every guide in your environment.
- **Eligible.** Guides that pass all eligibility checks for the current user.
- **On this page.** Guides whose target element exists on the current page.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The filter has been updated to: All, Active, and Eligible.

| **Inactive** | The guide has not been published or is currently inactive. |
| **Archived** | The current user has already dismissed this guide. |
| **Not targeted** | The current user doesn't meet the guide's targeting conditions. |
| **Not found** | No component that can render this guide was found on the page. |
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
| **Not found** | No component that can render this guide was found on the page. |
| **Not queried** | No component that can render this guide was found on the page. |

The label has been updated to "Not queried" for this status.

Each guide row displays three eligibility ("Elig.") indicators. A filled dot means the condition passes; an X means it fails. All three must pass for a guide to display.

1. **Active.** The guide is published and active.
2. **Not archived.** The guide has not been dismissed for the current user.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
2. **Not archived.** The guide has not been dismissed for the current user.
2. **Archived.** The guide has not been dismissed for the current user.

We flipped this to remove the double negative, per Sam's suggestion.

- **Ready.** A component found the guide and is actively returning it for display.
- **Throttled.** A component found the guide, but throttling rules are holding it back.
- **Queued.** The guide is available but not yet ready to display because another guide is ahead of it in the display sequence.
- **Not found.** No component on the page can render this guide.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
- **Not found.** No component on the page can render this guide.
- **Not queried.** No component on the page can render this guide.

Two visibility ("Vis.") indicators show the guide's display state:

1. **Activated.** The guide's trigger condition has been met in the current location.
2. **Selectable.** The availability and readiness of the target component on the current page. Possible values:
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
2. **Selectable.** The availability and readiness of the target component on the current page. Possible values:
2. **Display.** The availability and readiness of the target component on the current page. Possible values:


Two visibility ("Vis.") indicators show the guide's display state:

1. **Activated.** The guide's trigger condition has been met in the current location.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
1. **Activated.** The guide's trigger condition has been met in the current location.
1. **Activation** The guide's trigger condition has been met in the current location.

### Toolbar controls

- **Drag handle.** Drag to reposition the toolbar anywhere within the viewport. The toolbar stays within viewport bounds and re-clamps automatically on window resize.
- **Sandbox.** Prevents engagement API calls (seen, interacted, dismissed) from being sent to Knock. Local state still updates so the UI reflects changes, but nothing is recorded in Knock. Use this to test continuously without needing to reset engagement.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
- **Sandbox.** Prevents engagement API calls (seen, interacted, dismissed) from being sent to Knock. Local state still updates so the UI reflects changes, but nothing is recorded in Knock. Use this to test continuously without needing to reset engagement.
- **Sandbox engagement.** Prevents engagement API calls (seen, interacted, dismissed) from being sent to Knock. Local state still updates so the UI reflects changes, but nothing is recorded in Knock. Use this to test continuously without needing to reset engagement.

- **Drag handle.** Drag to reposition the toolbar anywhere within the viewport. The toolbar stays within viewport bounds and re-clamps automatically on window resize.
- **Sandbox.** Prevents engagement API calls (seen, interacted, dismissed) from being sent to Knock. Local state still updates so the UI reflects changes, but nothing is recorded in Knock. Use this to test continuously without needing to reset engagement.
- **Ignore throttle.** Bypasses the display interval throttle window so guides can display immediately, regardless of when the last guide was dismissed.
- **Inspect target params.** Opens a panel showing the tenant and data params being used to evaluate guide [targeting](/in-app-ui/guides/create-guides#targeting) for the current user.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
- **Inspect target params.** Opens a panel showing the tenant and data params being used to evaluate guide [targeting](/in-app-ui/guides/create-guides#targeting) for the current user.
- **Settings & target params.** Opens a panel showing the tenant and data params being used to evaluate guide [targeting](/in-app-ui/guides/create-guides#targeting) for the current user.

Also, now the "Sandbox engagement" and the "Ignore throttle" toggles are folded into this expandable area, so maybe we want to bring them down here as sub bullets?


<AccordionGroup>
<Accordion title="How can I test guides with an older SDK version?">
If you're on `@knocklabs/react` v0.8.0 or above, but haven't upgraded to v0.11.8 yet, you can still preview guides in your application using live preview:
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Heads up: Live preview is effectively being replaced with the new toolbar, so it won't be there once we GA. We probably just want to nudge people to upgrade to >v0.11.13?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants