Chapter 2. eXo Add-ons


You are looking at documentation for an older release. Not what you want? See the current release documentation.

In this guide, the term "eXo add-on" denotes anything that enhances the eXo extensibility - is developed and distributed by eXo or any third-parties or any individual developers. An add-on may comprise a set of extensions, customizations, xml configurations, applications, templates or any new services.

In eXo Platform, you can perform various extensibilities, for example, portal extension to extend portal, UIComponent plugin to add another UI component (Wiki actions, Activity types), or search connector. In-depth tutorials for those extensions come in the later chapters and sections. This chapter only focuses on the basic techniques of developing an add-on, including:

  • Portal extension

    Introduction to the portal extension mechanism and details to create a portal extension - the most commonly used technique that allows extending the portal container configuration.

  • Packaging

    How an add-on should be archived so that you can use the Add-ons Manager to install or uninstall it.

  • Deployment

    Ways to deploy an add-on into the eXo Platform server and detailed steps to perform a local deployment with the Add-ons Manager.

  • Publishing

    How to register an add-on in the catalog and information declared for one catalog entry.

  • JavaScript Safety

    It is very important that your application's JavaScript is safe from other applications' code and does not pollute global variables.

Copyright ©. All rights reserved. eXo Platform SAS
blog comments powered byDisqus