DocumentationExperience League Authoring Guide

Playlists

Last update: Fri Sep 12 2025 00:00:00 GMT+0000 (Coordinated Universal Time)

You can create playlists to INSERT.

Clone the Playlists repo

Clone the Playlists repo.

The playlists.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.

Install the VSCode plug-in for playlists and slides

The ExL team has developed a Visual Studio Code plug-in with a visual editor to simplify playlist creation. Authors can use this visual tool to drag-and-drop Experience League tutorial pages, and the ID, title, description, and metadata will be automatically extracted and added to the YAML.

Download and install the VS Code Plug-in from this .vsix file on the releases wiki

  1. In VSC, open Extensions.

  2. Install the file from VSIX:

    Click Views and More Actions (the ellipses), then click Install from VSIX…

If you have questions or concerns when using the extension, reach out to the exl-playlists Slack channel.

Using the extension for playlists

Use the VSC plugin for playlists:

  1. Click the Adobe ExL Authors button in the activity bar.
  2. Click New Playlists and provide a file name.
  3. Add URLs by dragging from your browser or pasting into the input field.
  4. Organize your content by dragging items to reorder.
  5. Configure metadata including title, description, and publishing settings.
  6. Save and view your generated YAML file.

creating playlists

Playlist setup

Folders and filenames

The folders in the playlist 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 Playlists can reside in any folder in the repo as long as the filename is unique across the entire repo. For example, analytics/get-started.yml and campaign/get-started.yml 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.

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.

Metadata
What it does
title
Playlist title, used as the display title and the title for discovery (cards, internal and external search)
description
Playlist description, used as the display title and the title for discovery (cards, internal and external search)
solution
same as docs
role
same as docs
level
same as docs
feature
same as docs
feature-set
same as docs
publish
false publishes only to stage, true publishes to both stage and production.

Body

The playlist body uses a YAML syntax with a list of the MPC videos.

playlist: container object for videos.

video: contains an MPC ID, title and description

Playlist ID

Playlists use an ID that is derived from source filename, disregarding any directories. Using the example above, analytics/get-started.yml will receive the unique ID of get-started. Playlist markdown files do not go through CLUE to get an ExL ID.

Translation

Playlists use existing translations where possible, and this was one of the main drivers behind linking to tutorials instead of directly to the video. Because the tutorial page is the best source-of-truth for titles and descriptions, we are copying the already translated fields from these pages into the playlist data structure. Essentially, playlist translation requires only translating the title and description.

Builds

TBD.

Redirects

TBD.

recommendation-more-help
92f1a422-8a81-400b-85d3-388f0c36dfda