In the first tab of the plugin editor, you'll be able to set general settings for your plugin. You can modify the plugins name, URL, icons, and select the few categories relevant to the plugin. This is important to make your plugin searchable by Bubblers.

Shared technical settings

The second tab lets you define a few technical settings for your plugin.

This plugin uses jQuery 3. If you are building an element that relies on jQuery 3, check this box. The API will give you access to the jQuery plugin.

HTML Header. If you need to insert some HTML in all the pages of an app that use this plugin, you can enter the HTML here. Analytics services, for instance, usually require to add a HTML snippet on all pages. If you need users to be able to enter a key in an HTML snippet (for instance a Google Analytics tracking code), you can add the dynamic key in your snippet between the sequence of characters _*_, such a _*_API KEY_*_. Once a user uses your plugin in their app, this key will be a setting to be filled in the Plugins tab, and the key will be replaced by the actual value in Run-mode.

Additional keys. If you need your plugin's users to enter some keys in the Plugins tab, you can enter these key definitions in this tab. These keys will be made accessible in the context object that is sent to all the functions used in your elements and actions (see the following sections for more details). Note that if you are adding API connections to your app, the API call tab will let you pick the different keys that are need for your API to function.

Shared assets and resources. If your plugin implementation requires some assets (images, CSS file, JS files), you can upload them to Bubble's storage and use their URL in your code. All assets are accessible through Bubble's CDN, ensure high speed when accessing the files.