Upgrading
Upgrade your DA project to the latest SDK and configuration.
Moving an existing SharePoint, Google Drive, or XWalk project onto DA's current SDK and configuration is generally described as low-complexity work, but it touches a handful of specific files. This guide walks through what changes.
Enable live preview
Add the following to the bottom of scripts.js:
(async function loadDa() {
if (!new URL(window.location.href).searchParams.get('dapreview')) return;
import('https://da.live/scripts/dapreview.js')
.then(({ default: daPreview }) => daPreview(loadPage));
}());Because the import only fires when a dapreview query parameter is present, this has no effect on normal page load performance.
Fix legacy 404.html
Older projects' 404.html often sets crossorigin="use-credentials" on script tags. That attribute blocks the external live-preview script from loading, so it needs to be removed.
Migrate indexes and sitemaps
Move query-index and sitemap maintenance out of hand-managed sheets and into a helix-query.yaml file at the project root, letting Edge Delivery manage them internally. Indexes defined this way are strongly typed rather than returning every value as a string, so downstream code that assumed strings may need small adjustments.
Authentication
Confirm preview and publish authentication is configured for the upgraded project via tools.aem.live.
Overlaying legacy content
If SharePoint or Google Drive content still needs to serve alongside DA content during a phased migration, configure a Config Bus fstab entry that overlays the two sources and their markup endpoints for the transition period.
Related guides
- Business/practitioner upgrade walkthrough —
da.live/docs/administration/upgrade - Content import guide — DA's GitHub wiki
- Permissions setup —
da.live/docs/administration/permissions