Create a Trail for an Enablement Site
Learning Objectives
After completing this unit, you’ll be able to:
- Describe how to create a trail.
- Describe how to add a module to a trail.
Create a Trail
Modules can stand on their own, and don’t have to be part of a trail. But to help learners complete a series of related modules, you can organize those modules in a trail. Cindy, a content creator at Pure Aloe, wants to add the Pure Aloe Sales Strategies and Pure Aloe Competitors modules, which she created in the previous unit, to a trail.
In the Trailmaker Content workspace, Cindy clicks Add Content and selects New Trail.
On the Edit Trail page, she enters the trail’s information.
- The badge art for the trail (1).
- A custom color for the trail (2), which is the color for the trail header and the trail icon’s background. Trailmaker automatically darkens the header color to help the trail icon stand out.
- A title (3).
- A unique API name (4), which is the programmatic name that appears in URLs to the content. Accept the suggested API name, which is based on the title you entered, or enter a custom name. Each trail API name must be globally unique.
- A short description (5).
Filter values that help learners find the content when they search your enablement site (6).
The filter rules that we discussed in the previous unit for modules also apply to trails. Trailmaker requires you to select at least one filter value for each category. You can select default values, or a user with the Manage Site Settings permission can customize the available values.
Add Modules to a Trail
Next, Cindy adds the modules to the trail. From the Edit Trail page, she clicks Add Module, which opens a window with the following options.
-
Create a module, which navigates to the Edit Module page that we saw earlier.
-
Add a module from your workspace, which allows Cindy to select a module that she’s already created in her workspace.
-
Add a module by API name, which allows Cindy to reference a module that’s not currently in her own workspace.
Why would Cindy want to reference modules that don’t exist in her own workspace? Referencing by API name is useful for:
- Modules that have already been published on your enablement site.
- Modules that other content creators create and add to the same release as the trail.
Because Cindy wants to reference the modules that she’s created in her own workspace, she selects Add a module from your workspace.
A search box appears where Cindy can view a list of modules in her workspace. She selects Pure Aloe Sales Strategies and clicks Done.
She repeats this step to add the Pure Aloe Competitors module.
In the next unit, you look at how Cindy can add the trail and modules to a release, which is the next step in getting her content published.
Resources