Positionning (Trigger)
The Trigger Options allow you to control how and where your changelog is displayed, ensuring it catches your users' attention at the right moment. Here’s a detailed guide to the available triggers.
Trigger Options
Each trigger option is designed to accommodate different styles and levels of visibility, allowing you to match user interaction with the aesthetic and functional flow of your platform.

By choosing the appropriate trigger and customizing it to your needs, you can ensure that your changelog effectively engages your users.

Temporarily suspend access to the changelog without removing the integration.

Usage:
Ideal for when you need to temporarily disable the changelog.
To re-enable, select another trigger option.
Steps:
Select Disable from the Type dropdown in the General section.
The changelog will not be displayed until a different trigger is selected.

Display the changelog as an omnipresent floating icon in the bottom right corner.

Features: Ensures the changelog is always within reach.
Steps:
Select Float from the Type dropdown.
Customize the floating icon text if desired.
📌 When to Use
Choose the Float trigger when you want:
A persistent call-to-action always visible on screen
A ready-made button with built-in styling and customization (no code required)
To highlight updates in a modern, eye-catching way without needing layout changes
A quick setup with minimal dev involvement
It's ideal for most teams looking for a simple yet elegant changelog trigger that just works out of the box.
Draw attention to the changelog with a pulsating effect.

Features: Requires attachment to an element on your website.
Usage:
Transform the bound element into an interactive component that opens the widget.
Steps:
Select Pulsating from the Type dropdown.
Copy the provided snippet and paste it into your website’s HTML to bind the pulsating effect to an element.
📌 When to Use
Use the Pulsating trigger if:
You need to match your design system perfectly
You want complete control over where and how the trigger appears
You already use internal components and just want to plug in the logic
Use a side badge for a discreet yet accessible entry point to the changelog.

Steps:
Select Side Badge from the Type dropdown.
Customize the badge text if needed.
📌 When to Use
Choose Side badge when you want:
A subtle but accessible changelog trigger
Something that floats and persists but doesn't interrupt the main UI
Full visual customization while staying within the Jimo UI editor
Fully tailor the trigger, embedding it seamlessly into your site’s design schema.

Usage: Requires knowledge of HTML/JavaScript and access to your website’s source code.

Steps:
Select Custom from the Type dropdown.
Create the trigger element in your HTML (e.g., a button).
Set up a click listener to open the widget when the element is clicked.
📌 When to Use
Choose the Custom trigger if:
You need total freedom over design and interaction
You want to integrate the changelog into an existing button or UI component
You have developers available to implement the logic
Each trigger option is designed to accommodate different styles and levels of visibility, allowing you to match user interaction with the aesthetic and functional flow of your platform.
Last updated
Was this helpful?





