We’ll keep using the AdobeDocs repo to write documentation with the same Markdown syntax. However, we’re building to a new pipeline and switching the output from
docs.adobe.com to the
We’re now in the testing phase of Experience League output.
During the testing phase, AdobeDocs repos are connected to both the current pipeline (
docs.adobe.com via AEM) and the upcoming pipeline (
experienceleague.adobe.com via Git bundle). Content is validated for each pipeline using a different set of rules. In nearly all cases, content that is valid for
docs.adobe.com will also be valid for Experience League. There are exceptions for both pipelines.
To see the validation status of repos on Experience League, see the
ExL tab in Jenkins:
When you commit any change to the master branch on AdobeDocs, validated content is packaged (quickly!) for Experience League and uploaded to a server.
You can check validation for your repo here:
Updates to AdobeDocs repos are activated periodically (currently every 6 hours: 5am/11am/5pm/11pm PDT) on
Note that user guides are not yet stitched together properly in doc sets. We’re still working on this functionality, which we refer to as work on the “manifest.”
If your repo is hooked up to EXL, you can change the domain for any docs.adobe.com article to see that page rendered in Experience League.
AEM Main Landing (optional) - We’re not sure if we’ll use this, but it’s here if we need it.
Customer Intelligence - Do we need a landing page?
Customer Journey Analytics - Do we need a landing page?
Journey Orchestration - Do we need a landing page?
Real-Time Customer Data Platform - Do we need a landing page?
Old ad hoc landing page for tutorials - Do we need a new landing page for all tutorials?
Use Jira to create Experience League issues and link them to the docs migration epic:
Click the + sign to add an issue to the Docs Migration epic.
Here’s the ExL Backlog for reference.