In this topic you will learn how a plugin developer can localize a Brightcove Player plugin. Note that this is NOT the same as using the built-in localization for the player itself. As is suggested in the Quick Start to Plugin Development , the application will be developed locally then converted into a plugin.

In this topic, you will learn how to create a player of a specified version and then test that version of the player with a plugin. The plugins can be your own creations, or Brightcove supplied plugins. You will be given three options for testing: Using Studio to create a player and add the plugin and configurations. Using Studio to create the player, then in HTML programmatically add the plugin. Using the Player Management API and curl . The curl tool is used at the command line to leverage the Player Management API. For an introduction to using curl, see the Quick Start: Player Management document. If you are familiar with HTTP client tools, like Postman , they can also be used. The advantage of this approach is that you can choose any version of the player you wish, not only those that are available in Studio.

In this topic you will learn via a hands-on introduction about plugin development and use.