This guide is a Work In Progress
This guide is targeted at anyone who is creating Tutorials, Videos, and/or Courses for Experience League. If you are a member of a documentation team, or contributing content someone else created or only posting content you create occasionally, we have guides for you! Take a look at these guides,
Now that we know you are in the right place, let’s start with an overview of the various systems you will need to be familiar with.
The goal of this guide is to help learn by using a learn-by-doing approach. When you complete this guide,
There are 4 main types of content you are likely to create,
Videos are typically 3-8 minutes in length. They should show the product in use, showing the UI, and avoid using PowerPoint. They should also avoid showing the speaker (e.g., talking head).
Experience League uses the term “Tutorial” in the site navigation. In the site navigation it is used as a catch-all category that differentiates documentation and how-to content (e.g., videos, tutorials - as defined in this guide).
Article - An article is very straight-forward, it is mostly a page of text that can include visual elements.like an image or an animated gif.
Course - A course is used to deliver self-guided learning generally targeted at helping the customer get to first active use of the solutions(s), general use of the solution(s) or expanding their use of the solutions. Courses also all for badging, are tied to user preferences, etc.
This is generally left up to the content author’s discretion. Think about the audience along with the various content definitions, and then consider which medium will be the most effective for the audience given the content you are delivering.
For instance, if you are trying to explain the best ways to code an integration, you most likely will want to display code samples and allow the user to download these samples. Generally, this better handled in a written/tutorial. In a similar way, if you are trying to show someone how to the use the product UI to configure settings, a video can be a very effective way to do this.
It is perfectly ok to mix content types, like including videos in tutorials. A course is usually made up of multiple videos.
It is always best to be sure you have the latest product information if you are going to be building enablement content.
The Knowledge Transfer (KT) wikis are the single source of truth for all things related to the product features. KTs are created and maintained by the product team. You can find KTs for all solutions in the KT repository.
If you are not familiar with the KT process, want more details on how it works, or if you are looking to add the KT process to your product, see this guide for more information.
If your solution doesn’t have a KT repository please discuss with the Product Management team. You can also reach out to Sean Schnoor if you need assistance.
There are 3 primary steps in the workflow,
All Experience League content (with the exception of product documentation) is tracked in the Knowledge Transfer (KT) project. Jira has many advantages,
If you don’t have access to the Knowledge Transfer (KT) Jira project reach out to Sean Schnoor.
As a content author you will primarily be creating Initiatives when creating Courses, and Stories for all other asset types. Each story or initiative maps to a single asset, 1:1.
The following will give you some guidance on how the status indicators are leveraged,
Take a look at this Quick Start that shows the steps to creating a KT ticket.
All content on Experience League is associate with a markdown (.md) page.
A very easy way to get started, assuming you are using a Mac and Chrome,
title: Dynamically generating documents with Adobe Document Generator
description: This is the description text that will show on Experience League.
feature: ???
topic: ???
role: Developer
level: Beginner
kt: 9208
thumbnail: 323577.jpeg
---
Missing description