Events
The Experience League Events page (https://experienceleague.adobe.com/en/events) provides information about upcoming events as well as video recordings of past events.
Adding events
- To add upcoming events, contact Sean Schnoor for information.
- To create articles for past events, make sure that the event video is uploaded to MPC (see Upload an event recording). Then create an event article in the on-demand-events.en repo. A common approach is to copy/paste information from a similar video and update the information.
Contact Sean Schnoor or the Technical Marketing team for details.
Clone the Events repo
Clone the on-demand-events.en repo.
The on-demand-events.en repo is on the new GitHub Enterprise Cloud environment. If you have an issue with your sign-in, see GitHub setup - Signing in to GitHub Enterprise Cloud.
Events setup
Folders and filenames
The folders in the on-demand-events repo are for author organizational purposes only. The structure of this repo is not reflected in the URLs on the site. The main reason for this is that events can reside in any folder in the repo as long as the filename is unique across the entire repo. For example, analytics/get-started.md and campaign/get-started.md would result in a collision because the files are flattened on output. In this case the recommendation is to include the product name in the file.
Event URL pattern: https://experienceleague.adobe.com/en/on-demand-events/<filename>
Frontmatter
The frontmatter fields will be familiar to anyone who has authored other articles, they use the same values and operate the same way as articles. These fields are in the metadata section of the YAML file.
The event metadata uses V1 values, but product is used instead of solution. Soon, metadata will switch from old V1 metadata to V2 metadata.
event-date.)event-date for sorting per UGP-16034.) Using last-substantial-update might be used in the future.doc-type: Event or type: Event. We should change this to type instead of doc-type at some point to avoid confusion. Use both for now to be safe.index: false to prevent event from appearing in searchYAML format
For metadata with multiple values, use structured yaml instead of comma-delimeters.
Comma-delimited (avoid unless legacy)
role: Admin, Developer
level: Beginner, Intermediate
Structured yaml
Use structure yaml in particular when mulitple values are required for product, role, series and speaker. For
role:
- Admin
- Developer
speakers:
- name: Jessica Meyers
picture: https://i.pravatar.cc/300
title: Director of Marketing Operations and Technology at Terra
- name: Oliver Moretti
picture: https://i.pravatar.cc/300
title: Sr. Product Manager Adobe Analytics
product:
- Marketo
- Workfront
- Experience Platform
Body
The event body uses markdown syntax with a link to MPC videos at the top of the document above the title and the event details below the title.
Use only basic markdown for events. Some syntax such as shade boxes will cause the page to be displayed incorrectly.