Asset kit

  • Feature group: asset kit
  • Released with version 2.5.0
  • Last updated in version 2.5.4

Asset kit

Asset Share Commons Asset kit is a set of functionality that aids in the automated creation of “asset kit” pages. Asset kit pages are well-defined collections of assets that are displayed on a single, shareable web page. Examples of asset kits include “press kits” and “look books”.

Asset kit comes with workflows that help creator the asset kit pages form asset folders or collections, and replicating the pages to AEM Publish service.

Overview video


The expected use of the Asset kit is as follows:

  1. AEM developer configures or extends the asset kit functionality as required on AEM.
  2. AEM workflow administrator creates a AEM Workflow model with the asset kit workflow steps and configures them accordingly.
  3. Author populates an AEM assets folder or collection (the payload) with the assets that are part of the asset kit.
  4. Author puts the payload under the AEM Workflow model (created in step 2).
    • Currently, the only OOTB way to do this is:
      • Tools > Workflow > Models > select the Workflow Model > Start Workflow > specify the payload (asset folder or collection) path
    • Custom development can add special Create asset kit buttons to the AEM Author service interface that automatically start the workflow on asset folders or collections.
  5. Asset kit automatically creates (and optionally activates) the asset kit page
  6. The asset kit page URL cannot be shared with external users that require access to the kit’s assets.


The following are the common configurations and extensions before using Asset Share Common’s asset kit.

  • Create a custom Asset kit component that displays the kit’s assets and the specific data they require. Custom asset kit components can implement custom HTL but use (directly or via delegating) the Asset Share Commons AssetKit Sling Model.
  • Create an Asset kit page template
    • Populate the template’s initial content with components the Asset kit creator workflow step updates based on the payload.
    • Populate the template’s structure content with any component’s that are common (and their content), across all asset kit pages.
    • Update the Page policy to include any custom CSS or JS client libraries required for the asset kit page to render to your brand standards, and function according to requirements.
  • Create custom component updaters to update the asset kit page, and any components (already in place via the template’s initial content) with
  • Optionally, create a custom page path generator if the asset kit page path should be something other than yyyy/mm/uuid.