Docs Developer Site
DeveloperDocsXpStableAdminWidgets

Widgets

Contents

Introduction

Widgets are visual components that dynamically extend Admin UI. Widgets may or may not be context-dependent (require id of selected content and current branch).

Implementation

Widget is essentially a special, admin-only kind of web application. Like all other XP components, widgets are defined by a controller and a descriptor.

To create a widget, add a new folder in your project structure, i.e. src/main/resources/admin/widgets/<widget-name>. The folder must contain both a descriptor (<widget-name>.xml) and a controller (<widget-name>.js).

Descriptor

Widget descriptor defines a display name, a list of roles required to access the widget and interfaces it implements. The descriptor file must match the widget folder name, i.e. admin/widgets/<widget-name>/<widget-name>.xml.

Sample descriptor file: 
<widget>
  <display-name i18n="phrases.my-dashboard-widget">My dashboard widget</display-name>
  <description i18n="phrases.my-dashboard-widget-desc">Description of my dashboard widget</description>
  <interfaces>
    <interface>admin.dashboard</interface>
  </interfaces>
  <allow>
    <principal>role:system.admin</principal>
    <principal>role:myapp.myrole</principal>
  </allow>
</widget>

Controller

To drive the widget, we will need a controller. The controller typically renders the widget’s HTML template. Depending on the widget implementation it may also handle any further server requests from the widgets interface.

The controller file must match the widget name, i.e. admin/widgets/<widget-name>/<widget-name>.js:

Example controller file: 
exports.get = function (req) {
    return {
        body: '<widget>My dashboard widget</widget>',
        contentType: 'text/html'
    };
};
Depending on the interface a widget is implementing, controller may be initialised with parameters, for instance providing a specific context.

Icon

Widgets may also have icons. Simply place an SVG or PNG file into the widget folder, i.e. admin/widgets/<widget-name>/<widget-name>.svg`

Widget icon will not be used for Dashboard widgets, only for Content Studio widgets.

Widget Types (Interface)

Widget interface is simply a unique identifier (or widget type, if you will) that links the widget to its extension point (i.e. Dashboard or Content Studio’s context panel). XP currently supports one type of widgets: Dashboard Widgets (interface admin.dashboard).

Content Studio supports other types of widgets that will be embedded inside the Content Studio UI. Read more about Content Studio widgets here

Dashboard Widgets

XP XP 7.12.0 7.12.0

Dashboard Widgets will be identified by interface admin.dashboard and displayed on the Admin Dashboard screen.

Following properties are supported in <config> of Dashboard Widget descriptor:

  • width

Used to specify widget width. Supported values are: small (25% of the screen width), medium (50%), large (75%) and full (100%).

medium is a default value for width config, if width is not specified or unsupported value is used.

  • height

Used to specify widget height. Supported values are: small (25% of the screen height), medium (50%), large (75%) and full (100%).

medium is a default value for height config, if height is not specified or unsupported value is used.

  • header

Specifies whether widget will automatically have a header with widget title (coming from display-name field in descriptor). Default value (when nothing is specified) is true which means that widget will have a header by default. To hide the header, use <header>false</header>.

  • style

Specifies whether XP will apply default styling to the widget (default). If you want to have full control over widget styling, use <style>custom</style>.

  • order

Specifies desired order of the widget on the Dashboard (with 0 being the top-left position). If order is not specified, the widget will be placed after widgets with specified order.

Widgets with equal order or no order will be placed based on their size (to fit as many widgets as possible next to each other).

Dashboard Widgets

Widgets in the screenshot above are configured in three different ways (from left to right):

Custom styling, position 0, display name in the header, width 25%, height 50% (default): 
<widget xmlns="urn:enonic:xp:model:1.0">
  <display-name>Useful Links</display-name>
  <interfaces>
    <interface>admin.dashboard</interface>
  </interfaces>
  <config>
    <property name="width" value="small"/>
    <property name="style" value="custom"/>
    <property name="order" value="0"/>
  </config>
</widget>
Default styling, position 1, display name in the header, width 50% (default), height 50% (default): 
<widget xmlns="urn:enonic:xp:model:1.0">
  <display-name>Content Studio: Recent items</display-name>
  <interfaces>
    <interface>admin.dashboard</interface>
  </interfaces>
  <config>
    <property name="order" value="1"/>
  </config>
</widget>
Default styling, last position, no header, width 25%, height 100%: 
<widget xmlns="urn:enonic:xp:model:1.0">
  <display-name>Statistics</display-name>
  <interfaces>
    <interface>admin.dashboard</interface>
  </interfaces>
  <config>
    <property name="width" value="small"/>
    <property name="height" value="full"/>
    <property name="header" value="false"/>
  </config>
</widget>

Contents

Contents

AI-powered search

Juke AI