Skip to main content
Cayuse Design System Lato · 4pt grid · WCAG 2.1 AA

Patterns

Resource Center

The Pendo-powered help overlay, opened from a floating button in the lower-right of every page — plus the My Tasks tab that surfaces the user’s outstanding work.

Figma source: Resource Center ↗

Structure

PartSourceNotes
Pendo Resource Center ButtonPendoThe floating trigger. The Figma description reads simply: “From Pendo. Opens Resource Center Overlay.”
Resource CenterPendo, styledThe overlay panel.
My Tasks TabCayuseA tab within the overlay listing the user’s outstanding tasks.

The dead zone

The button floats above everything, and the file plans for it

Several artboards — the Footer and Product Navigation among them — carry a hidden layer marked “Dead Space for Pendo Widget — NO FOOTER ITEMS HERE.”

The Resource Center button sits in the lower-right corner of every page in the suite, above the page content. Anything placed there is covered. Reserve that corner in every layout — it is not empty space, it is occupied space that happens to be rendered by a third party.

Usage

When to use it

  • Reserve the lower-right corner of every layout for the widget.
  • Keep the My Tasks tab consistent with the task counts shown on Tiles — two sources disagreeing is worse than one.
  • Style the overlay to the design system where Pendo allows it, so it does not read as a third-party bolt-on.

When not to use it

  • Do not place footer items, floating actions or fixed elements in the lower-right corner.
  • Do not make the Resource Center the only route to essential help.
  • Do not let the widget overlap a modal dialog.

Accessibility

Third-party accessibility is still your accessibility

The Resource Center is rendered by Pendo, so its markup is largely outside the product’s control — but a user encountering a help overlay they cannot operate does not care whose code it is, and neither does an accessibility audit.

Worth verifying, and raising with Pendo if it fails: the floating button is a real button with an accessible name and reachable in the tab order; the overlay traps focus while open and returns focus on close; Escape closes it; and the button does not obscure content at 200% zoom or on narrow viewports, where a fixed corner element can cover a form’s submit button.