From ce9a48e7520ebe6b8c976deb8405dbe46d562ebe Mon Sep 17 00:00:00 2001 From: Stephen Rugh Date: Wed, 3 Jun 2026 16:00:26 -0500 Subject: [PATCH 1/2] clarifying aem vs DA difference Signed-off-by: Stephen Rugh --- src/content/docs/boilerplate/universal-editor.mdx | 5 +++++ src/content/docs/get-started/before-you-start.mdx | 2 +- src/content/docs/get-started/create-storefront.mdx | 4 ++++ .../docs/merchants/quick-start/universal-editor.mdx | 11 +++++++++++ 4 files changed, 21 insertions(+), 1 deletion(-) diff --git a/src/content/docs/boilerplate/universal-editor.mdx b/src/content/docs/boilerplate/universal-editor.mdx index 3845d270a..9a21d0e04 100644 --- a/src/content/docs/boilerplate/universal-editor.mdx +++ b/src/content/docs/boilerplate/universal-editor.mdx @@ -7,6 +7,11 @@ sidebar: --- import Link from '@components/Link.astro'; +import Aside from '@components/Aside.astro'; + + The Adobe Commerce boilerplate supports the Universal Editor (UE) for content and Commerce blocks. For setup, instrumentation syntax, and custom block workflow, see the DA.live documentation below. diff --git a/src/content/docs/get-started/before-you-start.mdx b/src/content/docs/get-started/before-you-start.mdx index a611dfb3d..2b7676f61 100644 --- a/src/content/docs/get-started/before-you-start.mdx +++ b/src/content/docs/get-started/before-you-start.mdx @@ -21,7 +21,7 @@ These tools help you build and deploy a storefront on Edge Delivery Servic |------|-----------------|---------------| | Adobe ID | Document Author (DA.live) and other Adobe experiences in this workflow expect you to sign in with an Adobe ID. | Open , then use the account menu in the header to sign in or create an Adobe ID. | | GitHub account | Site Creator creates or links a GitHub repository for your storefront code. | (personal or enterprise). | -| Document Author (DA.live) access | Site Creator runs inside DA.live and stores your starter content there. | and sign in with the Adobe ID from the first row. For workspace and authoring concepts, see . If your organization uses enterprise access, ask your admin for an invitation. | +| Document Author (DA.live) access | Site Creator creates your starter content in DA.live. This applies to the default Document Authoring path. If your project uses AEM Sites as the content source, DA.live access is not required. | and sign in with the Adobe ID from the first row. For workspace and authoring concepts, see . If your organization uses enterprise access, ask your admin for an invitation. | | Adobe Commerce backend | Every drop-in component — a ready-made Commerce UI package for cart, checkout, account, or product pages — connects to an Adobe Commerce backend. You need to know which backend type you have before you can configure the storefront. | See [Backend options](/get-started/backends/) to pick Commerce PaaS, Adobe Commerce as a Cloud Service, or Adobe Commerce Optimizer. | | Commerce Admin access and API values | Site Creator can read from your Commerce APIs when they are reachable. After the repo exists, [Storefront configuration](/setup/configuration/commerce-configuration/) asks for base URLs, GraphQL endpoints (Commerce's query language for reading and writing data), and credentials for a headless storefront (the storefront UI runs in the shopper's browser, not on the Commerce server). The exact fields depend on your backend. | Work with your Commerce administrator or solution partner to gather values before you paste them into tools. [Backend options](/get-started/backends/) lists services and limits per platform. When you have API access and a repository, the in DA.live can build a starter storefront configuration from your inputs. Use [Storefront configuration](/setup/configuration/commerce-configuration/) to learn what each field means. | | Node.js | You need Node.js before you run the Commerce boilerplate locally (`npm install`, `npm start`, and drop-in updates). Adobe lists which Node.js release to install in the Prerequisites section of . Adobe updates that Prerequisites line when the recommendation changes. The Commerce boilerplate on GitHub does not declare a Node version in `package.json` (there is no `engines` field), so match whatever Prerequisites shows when you read it. | Open Prerequisites on , install the Node.js release listed there from , then run `node -v` to confirm. | diff --git a/src/content/docs/get-started/create-storefront.mdx b/src/content/docs/get-started/create-storefront.mdx index e5f47056c..7bbfaef3a 100644 --- a/src/content/docs/get-started/create-storefront.mdx +++ b/src/content/docs/get-started/create-storefront.mdx @@ -62,6 +62,10 @@ The diagram caption and the numbered list below describe the same flow, so you c + + ## Which backend do you have? diff --git a/src/content/docs/merchants/quick-start/universal-editor.mdx b/src/content/docs/merchants/quick-start/universal-editor.mdx index d46f5a2d6..5f4464bba 100644 --- a/src/content/docs/merchants/quick-start/universal-editor.mdx +++ b/src/content/docs/merchants/quick-start/universal-editor.mdx @@ -4,6 +4,17 @@ description: Edit Commerce storefront content with the Universal Editor. See DA. --- import Link from '@components/Link.astro'; +import Aside from '@components/Aside.astro'; + + The Universal Editor lets you edit storefront content in the context of the rendered page. The content is then saved into your Document Authoring (DA.live) project where you can use most content orchestration apps, such as localization, bulk publish, Snapshots, and more. From f0ee67689d743686beef856aadc9eba8b6072038 Mon Sep 17 00:00:00 2001 From: Bruce Denham Date: Wed, 3 Jun 2026 22:19:44 -0500 Subject: [PATCH 2/2] Updates from review --- src/content/docs/boilerplate/universal-editor.mdx | 4 ++-- src/content/docs/get-started/create-storefront.mdx | 2 +- src/content/docs/merchants/quick-start/universal-editor.mdx | 2 +- 3 files changed, 4 insertions(+), 4 deletions(-) diff --git a/src/content/docs/boilerplate/universal-editor.mdx b/src/content/docs/boilerplate/universal-editor.mdx index 9a21d0e04..2acbf3612 100644 --- a/src/content/docs/boilerplate/universal-editor.mdx +++ b/src/content/docs/boilerplate/universal-editor.mdx @@ -9,12 +9,12 @@ sidebar: import Link from '@components/Link.astro'; import Aside from '@components/Aside.astro'; +The Adobe Commerce boilerplate supports the Universal Editor (UE) for content and Commerce blocks. For setup, instrumentation syntax, and custom block workflow, see the DA.live documentation below. + -The Adobe Commerce boilerplate supports the Universal Editor (UE) for content and Commerce blocks. For setup, instrumentation syntax, and custom block workflow, see the DA.live documentation below. - ## Commerce boilerplate structure Commerce differs from the standard DA.live approach (centralized `ue/models/blocks/` in ): **UE instrumentation JSON files live next to each block** at `blocks/{block-name}/_{block-name}.json`. A pre-commit hook composes these into the root-level `component-*.json` files the UE consumes. diff --git a/src/content/docs/get-started/create-storefront.mdx b/src/content/docs/get-started/create-storefront.mdx index 7bbfaef3a..4bba67ee2 100644 --- a/src/content/docs/get-started/create-storefront.mdx +++ b/src/content/docs/get-started/create-storefront.mdx @@ -63,7 +63,7 @@ The diagram caption and the numbered list below describe the same flow, so you c ## Which backend do you have? diff --git a/src/content/docs/merchants/quick-start/universal-editor.mdx b/src/content/docs/merchants/quick-start/universal-editor.mdx index 5f4464bba..ef2bffe29 100644 --- a/src/content/docs/merchants/quick-start/universal-editor.mdx +++ b/src/content/docs/merchants/quick-start/universal-editor.mdx @@ -8,7 +8,7 @@ import Aside from '@components/Aside.astro';