DocumentationAEMUser Guide

Getting Started with the Experience Modernization Agent getting-started

Last update: June 17, 2026
  • Applies to:
  • Experience Manager as a Cloud Service

CREATED FOR:

  • User
  • Admin
  • Developer

Learn the first steps to get started using the Experience Modernization Agent and the Experience Modernization Console.

NOTE
If you are interested in using the Experience Modernization Console, you can request access through your account manager to ensure a smooth onboarding experience.

Prepare an Edge Delivery GitHub Repository prepare-repo

NOTE
Using an AEM Sites and Universal Editor project? Follow Getting Started for AEM Sites/Universal Editor setup steps.

  1. Select an Edge Delivery Services repository for use with the Experience Modernization Console.

  2. Ensure that the AEM Code Connector is installed in the repository.

    • This allows the console to inspect your code.

  3. Ensure that the AEM Code Sync GitHub app is installed in the repository.

    • This allows Edge Delivery Services to sync your code.
    • If your repo is based the on the tutorial, this step is already complete.

Open the Experience Modernization Console open-console

  1. Navigate to aemcoder.adobe.io.
  2. Log in with your Adobe ID.

Demo Mode demo-mode

The console launches in demo mode when you first sign in. This mode allows you to explore an existing site where you can try out migrating additional pages. A banner at the bottom the screen indicates that you are in demo mode.

Demo mode

Connect Your Site connect-repo

When ready to begin working on your own site you can exit demo mode by connecting to your own project.

  1. Click Switch site in the demo mode banner.
  2. This will prompt you to authorize the AEM Code Connector app using your GitHub credentials. Click Authorize AEM Code Connector.
  3. Back in the console, specify the Preview URL of the site. The preview URL can be obtained by previewing any document in the site, or by constructing it from branch, site-name and org. The system will retrieve the associated Github Project automatically. Alternatively, you can search through your authorized GitHub projects to find a site.
    Connecting to GitHub project
  4. Click Checkout to workspace once the site has been verified.
  5. When prompted to Replace existing workspace, click Replace workspace.
    Replace existing workspace

Your GitHub project and site is now connected to the console.

If demo mode has been exited but a new project has not been connected, subsequent visits to Experience Modernization agent will force a site to be connected first.

Site connection

Console Home console-home

When you visit aemcoder the Home Page will appear until a chat conversation has been started. The home page allows you to get started chatting by either typing your first prompt or by selecting one of the suggested prompts.

Console home

Start Prompting start-prompting

Now that your console can access your code, you are ready to start prompting.

  1. To get started you can import the content of a site:

    • “Migrate the page https://wknd-trendsetters.site.”

  2. This imports the content of the site.

    • The console observes separation of concerns and handles content and presentation separately.
    • The initial import of a site’s content may take several minutes.
    • The console presents you with ongoing feedback as it begins its work, including an overview of its planned steps.
      Content import

  3. Once the site is imported, the Workspace panel shows the pages. Select a page to preview it in the right panel.
    Content imported

  4. Now that you have content, you can prompt to import the styles from the same source.

    • “Import the general styles from https://wknd-trendsetters.site.”

  5. As with the initial content import, the import may take several minutes and the console provides feedback as it processes your request and imports the styles. Once the task is complete, click Refresh preview in the right panel to view the styled content.
    Styles imported

Now you have both the content and styles imported into the console.

TIP
Check out the prompting guide for more ideas on how to prompt the agent and what its skills can do.

Upload Content upload-content

To upload your content to Document Authoring:

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

    • By default you are in Content view when entering the console.
    • Your view is indicated by the selected View Picker item in the workspace area of the console.

  2. The Upload content dialog opens with the destination org and repo pre-filled from your project settings.

    • If an fstab.yaml is not present in your connected repository, you will need to manually enter your Organization and Repository…
    • If you used the boilerplate, an fstab.yaml is provided.

  3. Select the files you want to upload and click Upload.
    Upload content dialog

  4. The console indicates upload process by disabling the Upload button.

  5. Once complete, a notification appears at the bottom of the console.
    View in AEM

To access the uploaded content in Document Authoring, optionally click View in AEM in the notification when the upload completes, or navigate to https://da.live/#/{organization}/{repository}.

Content in Document Authoring

Your imported content is now in Document Authoring.

TIP
If you are working on an AEM Sites and Universal Editor project, uploading content to AEM works slightly differently. Refer to Getting Started with the Experience Modernization Agent for AEM Sites/Universal Editor Projects for specific upload instructions.

Push Code Changes push-code-changes

Once you are satisfied with the changes you have made to your code, you can push them to your GitHub repository.

  1. Switch to Changes view (branch icon in the view picker).
    Code view
  2. In the list of files changed, if some files show up as untracked, click their + button to stage them.
  3. Click Push button on the top-right.
  4. In the Push changes dialog, choose to push changes to a new PR (default) or the current branch and click Confirm to push.
    • When in doubt, you can push to the current branch to keep things simple.
  5. Once complete, a notification appears at the bottom of the console.
    View PR

If you wish to directly access the pushed changes in GitHub, click View PR in the notification when the push completes.

Code in GitHub

Your code is now in GitHub.

Preview Site preview-site

To view the changes in the preview environment:

  1. Go back to Document Authoring.

    • It may still be open in a browser tab you opened after clicking View in AEM after uploading the content.
    • Or navigate to https://da.live/#/{organization}/{repository}

  2. Open one of the pages that you previously uploaded to AEM.

  3. Click the paper plane icon (top right) and select Preview.
    Publish to preview

Congratulations! Your migrated content and styles are now live on the AEM preview environment.

Published preview content

If you pushed your code to a branch other than main, the preview opened from Document Authoring will not show the styles. Change to the branch by updating the URL of the preview and you can see your styles.

Troubleshooting troubleshooting

Allowlist IP Addresses allowlist-ip-addresses

If your site is behind a firewall or access restrictions, you can allowlist the following IP addresses so that the backend services can scrape your site:

  • 34.228.136.112
  • 54.90.51.39
  • 3.224.194.242

Additional Resources additional-resources

The following documents may be useful as you continue to explore the Experience Modernization agent and its console.

recommendation-more-help
experience-manager-cloud-service-help-main-toc