Skip to content

[ASSETS-61931]: Updating documentation for retaining external images in doc based authoring - #131

Closed
gazal2708 wants to merge 7 commits into
mainfrom
doc-update-main
Closed

[ASSETS-61931]: Updating documentation for retaining external images in doc based authoring#131
gazal2708 wants to merge 7 commits into
mainfrom
doc-update-main

Conversation

@gazal2708

@gazal2708 gazal2708 commented Nov 5, 2025

Copy link
Copy Markdown

@aem-code-sync

aem-code-sync Bot commented Nov 5, 2025

Copy link
Copy Markdown

Hello, I'm the AEM Code Sync Bot and I will run some actions to deploy your branch and validate page speed.
In case there are problems, just click a checkbox below to rerun the respective action.

  • Re-run PSI checks
  • Re-sync branch
Commits

@anuraggupta228 anuraggupta228 left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

make it concise. looks pretty long to read thru from readar pov.

summary, troubleshooting guide, scope, limitation, steps involved .. etc seems relevant.. rest all can be skipped.

Comment thread EXTERNAL-IMAGES-DOC-AUTHORING.md Outdated

## Overview

In document-based authoring (using Google Docs or Microsoft Word), when you insert images from AEM Assets with external URLs (Dynamic Media, Scene7, etc.), they are typically rendered as **anchor tags (`<a>`)** pointing to the image URL.

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

(using Google Docs or Microsoft Word) --> not needed

Comment thread EXTERNAL-IMAGES-DOC-AUTHORING.md Outdated

## Overview

In document-based authoring (using Google Docs or Microsoft Word), when you insert images from AEM Assets with external URLs (Dynamic Media, Scene7, etc.), they are typically rendered as **anchor tags (`<a>`)** pointing to the image URL.

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

they are typically rendered as

they are rendered OOTB as


1. **Detect anchor tags** that point to external image URLs
2. **Decorate them into `<picture>` elements** with responsive sources using the AEM Assets Plugin
3. **Configure handlers** for different image source types (DMwOAPI, Scene7, etc.)

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

for all the ref that can be embedded with hyperlinks from asset plugin, lets add it

Comment thread EXTERNAL-IMAGES-DOC-AUTHORING.md Outdated

**Key Difference from Universal Editor:**
- ❌ No `externalImageUrlPrefixes` feature flag support in document-based authoring
- ✅ External URLs are naturally retained as anchor tags

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

use OOTB keywords wherever seems the right fit..

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

2nd and 3rd points seems irrelevant from doc context.

Comment thread EXTERNAL-IMAGES-DOC-AUTHORING.md Outdated
- ✅ Frontend decoration handles everything automatically

**Key Benefits:**
- ✅ Responsive images with multiple breakpoints

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

multiple -> customizable

11. Original <a> tag replaced with optimized <picture> in DOM
12. Browser loads appropriate image based on viewport and format support

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

add code reference links to each .. would be intuitive for reader


### 📦 Installation

For complete installation instructions, refer to the official plugin documentation:

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

add reference to plugin repo. Avoid ambiguity/duplicacy

Comment thread EXTERNAL-IMAGES-DOC-AUTHORING.md Outdated

| Handler | Input Format | Output Format | Use Case |
|---------|-------------|---------------|----------|
| `createOptimizedPictureForDMOpenAPI` | DMwOAPI URL | AVIF sources | AEM Assets with Dynamic Media OpenAPI |

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

these looks useful but given you've already added steps involves in transforming the assets from to , then other deep dives with each step looks overkill

Comment thread EXTERNAL-IMAGES-DOC-AUTHORING.md Outdated
# Should return 200 OK
```

2. **Check CORS settings**

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

delivery url will never have CORS IMO

Comment thread EXTERNAL-IMAGES-DOC-AUTHORING.md Outdated
- AEM Assets delivery must allow your domain
- Check browser console for CORS errors

3. **Verify query parameters**

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

a lot of these steps looks overkill .. just curl, checking dam:roles , asset is approved should suffice, beyond that reach out to DM team should be instructed.

@gazal2708 gazal2708 changed the title Updating documentation for retaining external images in doc based authoring [ASSETS-57915]: Updating documentation for retaining external images in doc based authoring Nov 24, 2025
@gazal2708 gazal2708 changed the title [ASSETS-57915]: Updating documentation for retaining external images in doc based authoring [ASSETS-61931]: Updating documentation for retaining external images in doc based authoring Jan 6, 2026
@sdmcraft

Copy link
Copy Markdown
Collaborator

@gazal2708 , probably we should have all instruction docs consolidated in https://github.com/adobe-rnd/aem-assets-plugin repo. This repo is just an example site on how to use the plugin.

@gazal2708

Copy link
Copy Markdown
Author

Moving the documentations to aem-assets-plugin

@gazal2708 gazal2708 closed this Jan 13, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Adding documentations for retaining external images in doc based authoring and UE based authoring

3 participants