eds-da-content

Generate and validate Adobe DA and EDS compatible HTML and media references.

2|Updated Mar 12, 2026
One-click install
npx skills add https://github.com/aemcoder/skills --skill eds-da-content
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: eds-da-content
Source: https://github.com/aemcoder/skills/tree/main/skills/eds-da-content
Command: npx skills add https://github.com/aemcoder/skills --skill eds-da-content

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) and scripts (resource) components.

What problem does it solve?

This Skill prevents incorrect Adobe Document Authoring (DA) and Edge Delivery Services (EDS) HTML and media from breaking at preview/publish time, where many issues otherwise fail silently or render as plain HTML.

Core Features & Use Cases

  • DA + EDS content rule reference: Covers the exact HTML structure DA accepts and what EDS expects at delivery, including block identity, section structure, and required document skeleton tags.
  • Media and asset handling guidance: Documents how images, SVGs, video, PDFs, and fonts should be referenced and uploaded, including supported formats, size limits, and the Media Bus vs Content Bus behavior.
  • Platform contract and debugging heuristics: Explains the DA Source API and Admin API lifecycle (auth, upload semantics, preview/publish), plus a checklist of silent-failure rules to validate output before you upload.

Quick Start

Use the eds-da-content skill to verify your generated DA upload HTML before calling the DA Source API and previewing it on aem.page.

Frequently Asked Questions about eds-da-content

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
Why does my Adobe Document Authoring HTML break or render as plain HTML during EDS preview?

DA + EDS content fails silently during preview when HTML lacks byte-accurate block markup, section structure, or required document skeleton tags. Validating DA-stored documents against EDS delivery rules before calling the Admin API prevents these rendering failures.

How do I upload media correctly to the Media Bus for Edge Delivery Services?

Uploading media to the Media Bus requires referencing images, SVGs, video, PDFs, and fonts according to specific format and size limits. Following DA asset rules ensures binaries are correctly uploaded and delivered instead of failing silently.

What is the DA Source API lifecycle for previewing and publishing content?

The DA Source API lifecycle covers IMS authentication, upload semantics, and Admin API preview and publish endpoints. Satisfying these platform contract requirements ensures generated HTML uploads and previews correctly on aem.page.

Does the EDS block markup require a specific HTML document skeleton?

EDS expects byte-accurate block identity, section structure, and required document skeleton tags for correct delivery. Applying DA-compatible HTML constraints before upload ensures the content passes preview validation without silent failures.

How do I detect silent failures when generating DA and EDS compatible HTML?

Detecting silent failures in DA and EDS HTML requires validating output against a checklist of platform rules before calling the DA Source API. This validation covers block structure, asset references, and lifecycle requirements to prevent broken previews.

Can I use the Admin API to publish DA documents without IMS authentication?

Interacting with the DA Source API and Admin preview or publish endpoints requires IMS authentication to satisfy the platform contract. Without proper auth, document uploads and lifecycle actions will fail silently or be rejected.