This article explains how to preview content on
experienceleague.corp.adobe.com, how to publish (or activate) content manually, and how to configure your repo to auto-activate. We use “publish” and “activate” synonymously.
Publishing content works on a repo level. You cannot publish only individual articles or guides.
When you successfully commit changes to the
main branch, the changes are pushed to
experienceleague.corp.adobe.com for preview. View the Slack summary for a list of preview links.
If validation fails, your updates will not be available for preview until validation succeeds.
If validation succeeds, the Slack summary displays either a Publish or a Publish Now button, depending on whether auto-activate is enabled in your repo.
In the Slack summary, click Publish or Publish Now.
If necessary, sign in to Jenkins (VPN or Corp required).
If you’re a contractor, you might need to get access rights. Contact IT to request to add
https://docs.ci to the list of approved servers for the “Vendor_Basic” VPN.
Click Build to run the activate job for the repo.
You’ll get a Slack notification when the activation job is complete.
You can activate content by running the activate-exl job in Jenkins. When you run this job, all content is automatically activated, including articles, assets, and the TOC.
The changes should go live on
experienceleague.adobe.com as soon as the job has completed.
If your repo does not appear in the pulldown menu, contact Bob. (Or, click Configure and add your repo name without
As a rule, don’t commit to main unless you’re ready to activate the content soon after previewing it.
There is no connection between activating English and localization repos. Localization repos are configured to auto-activate. If you commit to main successfully but don’t activate, your changes will go live in other languages.
You can configure a repo so that content is automatically activated on a successful push to production. We recommend that you turn this on only after you’re comfortable with the new workflow.
The next time you commit to main, after validation passes, your edits will automatically be published to
experienceleague.adobe.com when the next pickup occurs (currently every two hours). See the next section for the publishing schedule.
If you want your changes to go live immediately, run the activate-exl job.
Auto-activated content is published thirty minutes past every odd hour PST. So if you publish your content at midnight PST, you can expect it to be published shortly after 01:30 PST. The following table provides an overview for our worldwide authors.
|PST||Odd hours on the half hour|
|MST||Even hours on the half hour|
|EST||Even hours on the half hour|
|GMT||Odd hours on the half hour|
|CET||Even hours on the half hour|
|EET||Odd hours on the half hour|
|IST||Odd hours on the hour|
The schedule is based on PST. Therefore when the US begins/ends DST (second Sunday of March/first Sunday of November), this schedule will shift for the rest of the world that observes DST later/earlier and for those that do not observe DST at all.
If you need your changes to go live sooner than scheduled, run the activate-exl job.
Here’s some background info for the EXL pipeline.
To hook up a repo to the EXL pipeline:
When you commit changes to the main branch of a repo that is connected to the pipeline, the following actions occur:
experienceleague.adobe.comin the next pickup that occurs every two hours. If you run the
activate-exljob in Jenkins, the content goes live to production as soon as that job finishes.