If you want the Widget to open from a specific button, link, or element on your app or website, you can create a custom launcher. For instance, you could set up the Widget to run each time a user clicks the "Changelog" link on your website. This guide will show you how to create a custom launcher that perfectly matches your website.

It is advised to have some basic knowledge of HTML and JavaScript, though it is optional to complete this quickstart. HTML Introduction and JavaScript MDN both have more details.

The Widget can be added to your website in two different ways. The recommended approach is the first method, using the embed script tag. This method involves copying a code snippet from your Onset Dashboard and inserting it into the HTML code of your website. When the page loads, the Widget will be displayed within an iframe on your website.

The second method of embedding the Widget is by installing it via NPM. The process involves downloading the widget package from the NPM repository and integrating it into your website. This method is suitable for developers who want to customize the Widget and have more control over its implementation.

Both methods can achieve the same result of having the Widget displayed on your website, but the embed script tag method is the more straightforward option for most users. The NPM installation method is better suited for more advanced users and web development projects that require more customization and control over the Widget.

Before using a custom launcher, it is a good idea to disable the Widget's built-in launcher button. To accomplish this, set the customTrigger property to true. This instructs the Widget that you prefer to use a different launcher than the one already included.

Once the Widget is loaded and ready, the global `onsetWidget` instance exposes helpful methods that make using a custom launcher a breeze. In this tutorial, we will be focusing on the show, hide, and toggle functions.

 - shows/hides based on the Widget's current state.

You can learn about all the available methods here.

There are various ways of integrating and using the custom launcher. It all depends on your setup. Here are two examples:

Here is a simple example of how to use the widget methods in React:

The Widget doesn't rely on any frameworks or plugins from outside sources. Here is an example of how to build a custom launcher using HTML and simple JavaScript.

The Widget's JavaScript API makes integration seamless. It provides a range of options, events, and methods that you can use to customize the Widget's appearance and behavior to fit your specific needs. The 

 provides detailed explanations of all available functionality, so you can quickly get up to speed with how to use the API effectively.

Create a Custom Widget Launcher

Release notes are for everyone. They provide useful information on the new features and improvements in each release. We built Onset to streamline the process of product releases and improve communication between product owners and stakeholders.

In most cases, keeping an updated log of release notes can be very cumbersome and messy. Which eventually leads to the abandonment of the entire process. Onset strives to eliminate the clutter and, encourage strict version control consistent formatting, and act as a single source of truth for all your product updates.

Often, release notes are drafted by engineers or technical product leads who speak the same language. However, they’re not always consumed by a tech-savvy reader. Release notes should be understood and accessible by everyone, so be mindful of what you log. Avoid using complicated technical jargon, and never, ever dump GitHub commit logs into your release notes.

It’s assumed that your client success or sales team members have promised to follow up with their customers on product updates, feature requests, or bug fixes. For that reason, teams outside of product and engineering should be able to easily find and review your product changes without any hassle.

If a tree falls in the forest and no one hears it, does it make a sound?

And choosing how you update your team is crucial. Status updates sent via email and slack give confidence to stakeholders on what has changed in your product in a way that is comfortable and convenient to them.

Automating your processes, communicating your updates, and strengthening your relationships is possible with Onset. Because how you share is just as important as what you share.

Release Notes Are for Everyone

Take control of what information is being shared about your platform. With Onset, you can publish your product releases publicly and in your own way.

Publishing public release notes for your products is a great way of keeping your customers in the loop and helping potential clients gain insight into how your tool is developing. Onset Public Pages allows users to subscribe to your projects and get updates directly in their email without you having to lift a finger.

Onset Public Pages are built to fit you and your company. That means you share as often as you want, to whom you want, and in the words that you chose.

Fully customizable, Onset Public Pages give you the ability to edit and adjust what your audience sees. Meaning you can customize your public page by uploading your logo, setting a brand color and custom domain, and more.

Release notes show the pulse of your product. Onset helps you share your way.

Create a Custom Widget Launcher

Release Notes Are for Everyone

More Visibility With Public Release Notes

Make every release count.