Configuration reference
These are the fields that change how the deployed widget looks and behaves.api.tenantId is an identifier, not a secret. See Security and data.Panel behavior
- A pill button is fixed to the top right of the viewport. On narrow viewports it moves closer to the corner.
- Clicking it slides in a panel anchored to the right edge, roughly 680px wide, and full width on screens under 700px.
- A fullscreen toggle in the panel header expands the panel to the full viewport width; the same button collapses it back.
- Pressing Escape exits fullscreen if the panel is expanded, and otherwise closes the panel.
- Clicking the dimmed backdrop, or the close button, closes the panel.
- While the panel is open, scrolling on the underlying page is locked, and the visitor’s scroll position is restored on close.
The button position, the panel width, and the
BETA badge on the button are fixed and cannot be configured. Only one widget instance runs at a time; initialising again tears down the previous instance first.Isolation from your page
The widget mounts into a shadow DOM root attached to a single container element appended to your page. All of its styles are injected inside that shadow root. This means the widget cannot inherit or leak CSS from your site, with the deliberate exception of the font family, which it inherits so the button blends with your typography. The container is positioned with the maximum stacking order so it renders above your own fixed headers and overlays.Controlling the widget from your own code
Once the script has loaded, a small API is available onwindow:
window.HermanWidget.mount(element, config) and window.HermanWidget.unmount().