You are here:
External Tools and Dependencies for an Enablement Site
To create and publish content, your company relies on a few resources outside of your enablement site.
Required Editions
| Available in: Enterprise, Performance, and Unlimited Editions |
| User Roles | |
|---|---|
| This topic supports these enablement site roles: |
|
Word Processor or Collaboration Tool
We recommend that you use a word-processing tool to draft, review, and finalize your content before you begin working in Trailmaker Content. This way, it’s easier for content creators, subject matter experts, and other stakeholders to revise and comment on content that’s in development. When you start working in Trailmaker Content, you’re working in your own local workspace, and other collaborators can’t access the content that you created or imported there.
Video-Hosting Platform
To embed videos in your content, first store videos in an external platform, such as Vidyard, YouTube, or Vimeo. In your content, insert a reference to the video’s secure embed URL. For more information, check out Insert Images and Videos in a Unit.
Survey-Hosting Platform
To embed surveys in your content, first create a survey in an external platform. Make sure that the platform allows you to embed the survey in another website. For example, you can embed surveys created with Salesforce Feedback Management, SurveyMonkey™, or GetFeedback. In your content, insert a reference to the survey’s embed code. For more information, check out Insert a Survey in a Unit on Your Enablement Site.
Version Control System (VCS)
When content is in Trailmaker Content, we recommend that you use a VCS for storing your content backpacks and facilitating collaboration. A VCS provides a secure system outside of your enablement site where content creators and their collaborators can access a single source of truth for your content.
- When content creators update existing content, they can retrieve a backpack from your VCS and import it into Trailmaker Content so that they start working from the most recent version.
- When your company localizes content, your localization team or vendor can access the most recent version of your English content for translation.
- When your company releases a new version of content, a release manager can download the latest backpack from Trailmaker Content and check it in to your VCS.
To implement a VCS, work with your admins and other stakeholders to identify the system that’s right for your company, such as GitHub, Microsoft Teams, or Google Drive™. Choose a system that satisfies these criteria:
- Supports .zip files
- Tracks multiple versions of a file
- Restricts access only to specified users
For more information about using a VCS as part of a collaboration workflow, check out Considerations for Managing Content in Trailmaker Content.
Localization Vendor
If you want your content to be available in other supported languages, work with a localization team to translate your English source content. If your company doesn’t have an in-house localization team, engage an external localization vendor. For more information about the requirements and workflow to localize enablement site content, check out Translate Enablement Site Content to Other Languages.
