Skip to main content
All CollectionsModular approach
Export module for AEM
Export module for AEM

Launch export of modules from eWizard to AEM as experience fragments.

Yuliia Skrybantovych avatar
Written by Yuliia Skrybantovych
Updated over a month ago

Contact your administrator to configure the module export for AEM.

Exporting modules from eWizard to Adobe Experience Manager (AEM) as experience fragments is a streamlined process that bridges content creation and omnichannel delivery. This integration allows you to leverage modules and seamlessly upload them into AEM for reuse across various channels.

Once your module is ready for the target use, you can launch its export in the following way:

  1. Unfold the module more options and click Export.

  2. In the Export popup, select AEM.

  3. Enter the export details that define your module target destination:

    • Path—the AEM directory where the HTML part of your module is placed upon export.

    • DAM—the AEM directory where digital assets—text, title, subtitle, button, image, block, placeholder, and column—present in your module are placed upon export.

The Path and DAM metadata is set by default, but you can change it if needed. The path to the AEM directory must always start with /.

Properly defined Path and DAM metadata during export streamlines searchability and empowers effective categorization within AEM.

  1. You can also select the following checkboxes:

    • Include AEM styles—to add an AEM package with configuration files and a file with eWizard content styles to the exported module.

    • Include AEM experience fragment template—to add an AEM package with configuration files and module template settings to the exported module.

If you select the checkboxes, the resulting ZIP archive contains 3 packages.

  • The clientlib content package bundles the styles needed for eWizard modules based on custom templates. Its AEM clientlib replaces the default clientlib in the eWizard AEM Connector and is referenced by a dedicated AEM experience fragment template.

  • The template content package defines a new AEM experience fragment template for eWizard modules based on custom (branded) module templates. Its primary purpose is to establish a dependency on the clientlib category linked to a specific eWizard module template. Additionally, it activates the configuration of component sets with content policies in AEM.

  • The experience fragment content package transfers eWizard modules to AEM, wrapping all configured content into AEM experience fragments. For modules based on custom (branded) eWizard templates, the dedicated template content package and clientlib content package must also be installed.

  1. Click EXPORT.

Upon successful export, download the resulting ZIP archive from the email notification you receive and use it in your Adobe Experience Manager environment.

Did this answer your question?