DocumentationAEM as a Cloud ServiceUser Guide

Getting Started with the Experience Modernization Agent for AEM Authoring Projects getting-started-aem-authoring

Last update: Mon Mar 09 2026 00:00:00 GMT+0000 (Coordinated Universal Time)
  • Applies to:
  • Experience Manager as a Cloud Service

CREATED FOR:

  • User
  • Admin
  • Developer

For AEM authoring projects using the Universal Editor, preparation of the Experience Modernization Agent differs from the standard Edge Delivery flow. This document covers those setup differences. Once the steps below are complete, follow the main Getting Started with the Experience Modernization Agent guide.

Create Your Edge Delivery Services Project Repo create-repo

  1. Use the aem-block-collection-xwalk repository as your template (not the standard Edge Delivery Services boilerplate).
  2. Follow the Universal Editor tutorial to set up your repo.
    • Stop when you are asked to create a site in AEM.
  3. Delete paths.json and commit this change to main.
  4. Add the AEM Code Connector app to your repo.
    • This allows the console to inspect your code.

Create a New Site in AEM create-site

  1. In the AEM Sites console, select Create > Site from template.

  2. Select the AEM Site with Edge Delivery Services Template.

  3. Keep the name of the site (not the title) as provided.

    • The site name is used as the unique identifier.
    • The title can be changed for display.

  4. Click Create.

    • You are redirected to the Sites page.
    • Refresh the page if the new site does not appear immediately.

  5. If you have not already done it when setting up your repo, update fstab.yaml so it points to your AEM host, git owner, and git repo and commit those changes to main.

Continue with the Standard Getting Started Steps continue

Once the above steps are complete, you can continue with the standard getting started guide to begin migrating your content.

Content import

Follow these steps from the standard guide.

  1. Prepare an Edge Delivery GitHub Repository
  2. Open the Experience Modernization Console
  3. Connect Your GitHub Repository
  4. Start Prompting

Content imported

Once you complete those steps to migrate the content, continue with the following steps.

Validate Content validate-content

Validate the content of the selected page in the preview panel. Any errors will be displayed by clicking the Errors button.
Continue your chat conversation with the agent to fix the errors. Use the Add to chat feature to target fixes to specific elements of the page, parser files, or transformer files.

Contextual chat

Upload Content upload-content

To upload your content to AEM:

  1. Make sure you are in the Content view and click the Upload content button on the top-right.

  2. In the Create content package dialog, choose the pages to include in the package.

    • Optionally enter a Package name (defaults to the site name if left empty).
    • Use Select all, Clear selection, Expand all, or Collapse all to manage the list.

  3. Click Create package.

    Create content package – choose pages and create

  4. After the package is created, the Upload content package dialog shows that the package is ready.

    1. You can Download package to save it locally, or proceed to upload.
    2. Under Upload to AEM, confirm the AEM site and AEM host (pre-filled from your project settings).
      • Optionally leave Upload images checked to include images.
    3. Click Upload to AEM.

    Package ready to upload to AEM or download

  5. The dialog shows upload progress as pages and assets are sent to AEM. When the upload finishes, a success message and the upload log are displayed. Click Close to dismiss the dialog.

    Upload progress and completion in AEM

Your imported content is now in AEM. Continue with Push Code Changes in the main getting started guide.

Additional Resources additional-resources

recommendation-more-help
fbcff2a9-b6fe-4574-b04a-21e75df764ab