Publish content
This article explains how to preview and publish content on experienceleague.adobe.com.
V2 publishing issues (temporary)
We’re experiencing publishing issues due to the large amount of content going through the pipeline. Jobs are being throttled by GHEC, Adobe I/O, and AEM EDS. The Engineering team is working on updating the pipeline configuration to make publishing more reliable.
Common issues
- You create a new article and add it to the TOC. The TOC is updated, but the link results in a 404. This is because the TOC job succeeded but the separate articles job is delayed or timed out due to throttling.
- You commit changes to main, but the updates fail to go through quickly. This is usually due to throttling affecting the entire pipeline. In some cases, you’ll get a Slack DocuMentor notification with links, but the content has not yet been updated.
- You commit changes to main, but the updates fail due to a syntax error not caught by validation. We’ve been fixing these validation gaps as quickly as we can, but we’re still running into these issues.
Temporary workarounds
First, if you committed to main but your content doesn’t go live, try a new PR with touch edits to the files that failed to update.
If the content still fails to go live, please report the issue in sccm-assistance.
We’ll send weekly status updates via email. We’ll also add occasional Slack updates.
Publish content
When you merge a PR to the main branch, content goes live by default to the following environments:
- production -
https://experienceleague.adobe.com/ - stage -
https://experienceleague-stage.adobe.com/ - dev -
https://experienceleague-dev.adobe.com/
The stage environment is useful for testing a new repo that is not yet hooked up to production. The dev environment is used by SCCM engineers for testing features.
Preview content
Add hold: true to the article metadata to publish to preview, not production. When an article is set to hold, updates you make to the article appear only in preview, not in production.
Remove the hold: true tag when you want to publish to production. The Slack notification provides URLs for both production and preview updates. Please don’t use hold: false.
If you add hold: true to a new article that you don’t want to publish yet, it’s a good idea to also add {hide-from-toc} to the TOC.md link to that article. See Hiding articles.
main branch, check the email address in Github Desktop > Settings > Git. It should be your Adobe email. Contact Bob if you still don’t get a notification.