Resources for internal Adobe writers and contributors.
Feel free to add links below.
Markdown is a lightweight markup language that is both easy to read and easy to learn. Therefore, it has rapidly become an industry standard. To write articles in Markdown, we recommend that you first download and install a Markdown editor. Popular options include:
You can also use command-line tools for performing Git tasks.
If you are unfamiliar with Git or GitHub, check out these resources.
When creating videos for users, upload the videos to Adobe TV. Do not use YouTube, Vimeo, or another third-party platform.
Sean Schnoor’s team manages video content for Experience Cloud. Before you create a video, check with Sean or a member of Sean’s team to make sure that you have access to the proper location within Adobe Media Publishing Cloud (MPC) and that you avoid duplicating existing content.
Create a KT Story in the KT project for each video.
Here’s an example KT Story. Adding the KT Story will prompt the localization team to pick-up the video and add subtitles and TTS.
When storing a video for AEM in MPC it should go in a newly created folder in the Help & Support > Experience League bucket.
There should be a 1:1 mapping of folder to English video. The folder name should be the exact same name as the video file.
Navigate to Adobe Media Publishing Cloud.
Navigate to the folder where you want to add the video.
You will need to have proper access and permissions to upload videos. Contact Sean Schnoor or his team for details.
Click the upload icon from the top right corner.
Drag and drop the videos to the dialog box or click to browse to your local location of the video. Add the title and description to your video.
Once the upload is complete, click on Get Code under Embed Codes to access the publish link.
Copy the link to the video from the Shareable Link, as shown below.
Once you have the link, you can share the link or add the specific video to your documentation with the following syntax:
If you have questions about uploading videos, contact Sean Schnoor or a member of his team.