Getting Started

A template is an app which adds the capability to create, edit, preview, publish, and play out a new type of content. Templates consist of: HTML5 code (HTML, CSS, JavaScript). Static assets, such as graphics, images, fonts, and animatio...

Player API Flow The Player API defines the flow of control between the player and the template, and allows for seamless orchestration of content.  In order to achieve gapless and glitchfree switches between content, the API allows the templ...

A template must contain a manifest file, called 'template.json' which is described in more detail in the next section.  The manifest file contains the name of the template's main HTML file.  The HTML file may in turn reference script f...

The manifest file provides vital information about the template to the system: { "name": "My First Template", "contentBasePath": "", "application": "template.html", "options": { "apiVersion": 2, "templateVersion": 3...

Optional fields are marked with a * Text The text field is an ordinary single-line text box: { "type": "text", "key": String, "caption": String, "default": String, * "required": Boolean * } Checkbox The checkbox  field is...

Player attributes are a mechanism for handling triggering in the playback-flow, as well as containing a data-payload. An attribute is scoped by default to the layout (the layer-set) but can also cross sync-groups, so that multiple players can share ...

The usual purpose of a template is to show some dynamic content on a player/display, as part of a channel and playlist. However, in the life cycle of template-based content, there are a number of different cases where the template is called to a...

Layout Target Resolution The Player will be running in a layout.  The layout specifies the target screen resolution, for example 1920x1080 for a standard full HD landscape screen or 1080x1920 for portrait.  This target resolution defin...