Skip to content

feat: aem cloud service content distribution skills#67

Open
abhishekgarg18 wants to merge 3 commits intoadobe:betafrom
abhishekgarg18:feature/aem-cloud-service-content-distribution
Open

feat: aem cloud service content distribution skills#67
abhishekgarg18 wants to merge 3 commits intoadobe:betafrom
abhishekgarg18:feature/aem-cloud-service-content-distribution

Conversation

@abhishekgarg18
Copy link
Copy Markdown
Collaborator

Created a complete skill suite for AEM as a Cloud Service content distribution, covering publishing workflows, Preview tier management, programmatic APIs, troubleshooting, and
orchestration.

Skills included:

  • content-distribution (main orchestrator with intent routing)
  • publish-content (Quick Publish, Manage Publication, Tree Activation, scheduling)
  • preview-tier (Preview tier workflows, UAT testing, stakeholder review)
  • distribution-api (Official Replication API, OSGi event handlers, bulk operations)
  • troubleshoot-distribution (diagnostics for stuck content, CDN cache, Sling jobs)
  • orchestrator (go-live preparation, incident response, CDN optimization)

Reference documentation:

  • architecture.md (3-tier architecture, Sling Content Distribution, CDN)
  • cloud-guardrails.md (rate limits, best practices, capacity planning)

Key features:

  • 9 markdown files with 3,703 lines of comprehensive documentation
  • 100% Cloud Service-specific (no 6.5 LTS content)
  • Real-world examples with Java code using official Replication API
  • Preview tier native support (Cloud Service exclusive feature)
  • Automatic Sling Content Distribution (vs manual replication agents)
  • Integrated Adobe CDN with auto-purge
  • NO migration-related content (publishing/deployment only)

Latest Updates (2026-04-13)

Critical API corrections applied (commit: 8eac80b):

  • Fixed documentation to use official Replicator.replicate() API (not JCR properties)
  • Corrected false claim that Replication API is "removed" (it exists and is the official method)
  • Removed all migration-related references (4 instances)
  • Added Cloud Service capacity limits (max 100 paths/call, 10MB size limit)

Verification Sources

All code examples and API usage verified against official Adobe documentation:

Primary Documentation:

API References:

Additional References:

Location: skills/aem/cloud-service/skills/content-distribution/

Abhishek Garg and others added 3 commits April 10, 2026 17:57
Created a complete skill suite for AEM as a Cloud Service content distribution,
covering publishing workflows, Preview tier management, programmatic APIs,
troubleshooting, and orchestration.

Skills included:
- content-distribution (main orchestrator with intent routing)
- publish-content (Quick Publish, Manage Publication, Tree Activation, scheduling)
- preview-tier (Preview tier workflows, UAT testing, stakeholder review)
- distribution-api (JCR-based publishing, OSGi event handlers, bulk operations)
- troubleshoot-distribution (diagnostics for stuck content, CDN cache, Sling jobs)
- orchestrator (go-live preparation, incident response, CDN optimization)

Reference documentation:
- architecture.md (3-tier architecture, Sling Content Distribution, CDN)
- cloud-guardrails.md (rate limits, best practices, capacity planning)

Key features:
- 9 markdown files with 3,703 lines of comprehensive documentation
- 100% Cloud Service-specific (no 6.5 LTS content)
- Real-world examples with Java code and workflows
- Preview tier native support (Cloud Service exclusive feature)
- Automatic Sling Content Distribution (vs manual replication agents)
- Integrated Adobe CDN with auto-purge
- Based on official Adobe documentation

Location: skills/aem/cloud-service/skills/content-distribution/

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
Address PR review feedback:
- Remove migration workflow from orchestrator capabilities (README.md, SKILL.md)
- Remove migration use cases
- Delete entire "Migration from AEM 6.5 LTS" section from README
- Delete "Migration from 6.5 LTS Guardrails" section from cloud-guardrails.md
- Replace migration note with reference to separate migration skill
- Remove broken references to non-existent sling-distribution.md, cdn-integration.md, preview-tier.md files
- Add note that additional reference documentation will be added in future updates

All migration-related content removed per PR requirements.
Documentation now focuses solely on Cloud Service content distribution.

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
CRITICAL FIXES:
1. Replication API EXISTS in Cloud Service (not removed)
   - Corrected false claim that com.day.cq.replication.* is "REMOVED"
   - The Replicator interface, ReplicationOptions, ReplicationStatus all exist
   - Official Adobe Javadoc confirms API availability

2. Use official Replicator.replicate() method (not JCR properties)
   - Replaced undocumented JCR property approach with official API
   - Updated all code examples to use replicator.replicate()
   - Added proper OSGi service injection examples

3. Removed all migration-related content
   - Changed "Migrating large content trees" to "Publishing large content trees"
   - Changed "Site migration" to "Bulk site publishing"
   - Changed "Controlled content migration" to "Specific content deployment"
   - Removed reference to non-existent "migration skill"

4. Added Cloud Service capacity limits
   - Maximum 100 paths per replicate() call (recommended)
   - Absolute limit: 500 paths (throws ReplicationException)
   - Maximum 10MB content size per call
   - Recommend Tree Activation workflow for bulk operations

VERIFIED AGAINST:
- https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/operations/replication
- https://developer.adobe.com/experience-manager/reference-materials/cloud-service/javadoc/com/day/cq/replication/package-summary.html
- https://developer.adobe.com/experience-manager/reference-materials/cloud-service/javadoc/com/day/cq/replication/Replicator.html

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
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.

1 participant