Add custom widgets to Communities
Extend the functionality of the Communities application by adding custom widgets. To make the widgets available for use in Communities, configure the widgets in the widget definition file, widgets-config.xml.
We can use custom widgets to bring additional functionality to the Communities application. Making custom widgets available gives community owners greater control and flexibility over the content of a community. The widgets must use the iWidget specification, based on JavaScript, XML, HTML, and CSS. Widget files are stored on an HTTP server. The widgets can be bundled as EAR applications and deployed on IBM WebSphere Application Server. They can also be hosted in LAMP, .NET, and other environments.
We need to register the widgets developed by iWidget developers to make them available for use in Connections. We do this by configuring the widget attributes defined by the iWidget developer in widgets-config.xml.
We can add three types of custom widget to IBM Connections:
Mandated Exists in every community and cannot be removed or hidden. Mandated widgets can exist outside a community, for example, they can show up in a search results page. This type of widget can be placed in any of the three columns on the overview page. Mandated widgets can also be placed in the first column under the tag cloud in Communities. In Communities, the Recent Update and Members widgets are mandated widgets. Added by default Display by default. Can be removed or hidden. Can be moved to a different location. In Communities the Forums, Bookmarks, Files, and Status Updates widgets are all added by default. Not included by default. Close the widget palette. widgets can be added, removed, hidden, and moved by community owners. Any widget can be used as a mandated, default, or optional widget.
See
Parent topic:
Administer widgets and remote applications
Related: