All elearning courses at GitLab will utilize the Handbook as the Single Source of Truth (SSOT).
Below is an outlined example of how the field enablement team created a handbook first learning course using Articulate 360.
The Instructional Designer on the Learning & Development Team maintains a Content Creation Best Practices Guide to provide team members with a guide when creating learning content.
Instructional designers use the ADDIE instructional systems design (ISD) framework to design and develop courses. The workflow of course development will be as follows:
Our goal is that each course will have an associated Handbook page including learning objectives, static learning content, quizzes, and applicable links.
Consider the following when documenting course content in the handbook:
This training video provides an example of how iframes can be used to display sections of the handbook in a Rise 360 course. The same can be done in Level Up.
In the team Articulate - Rise 360 license, there is a block template for iframes. You can access this template in the
block templates section and add your iframe code directly.
Consider copying and pasting the iframe tag below to apply the strategies outlined in the training. GitLab team members can access this Google doc resource for ease of access to iframe tags that can be copied and edited when building courses using Articulate360 tools.
<iframe src="link-to-your-page" title="title for iframe metadata" scrolling="yes" height="500" width="800"></iframe>
Interactivity such as games, drag-and-drop, matching, and other interactive components in a published elearning course will not be accessible via the Handbook; however, all information conveyed to learners through the elearning course will have an associated Handbook page as needed. This will make sure that despite the interactivity of the elearning course, learners will have access to all topics covered in a course via the Handbook.
The following best practices should be followed when using video to create handbook first learning material.
Other best practices for recording new learning video include:
.vttfiles with video content added to Rise courses using Articulate360 to include closed captions within the course.
When creating learning content, the Learning & Develpment team may work with other teams on creating videos.
Guidelines for recording a video for a course:
Recordbutton, then click
Record on this Computer- This will make the file save to your computer and then you can drag and drop into the designated Google Drive folder
share screenbutton as your normally would if sharing your screen in a meeting. Select the one browser that has your slides when selecting which screen to share - do not share your full Desktop as slack or other notifications could pop up in the Full Desktop mode (we don’t want to see any other applications or tabs you have open). Also, please ensure your slides are in
Presentmode and are taking up your full screen .
Stoprecording or just end the meeting. (Note: We can snip pieces of the video so if you start recording and then not start talking for 30+ seconds, we can snip that from the recording (same for any blank time at the end).
The following best practices should be followed when building learning content that includes private or internal only video.
Use the following resources when building handbook first learning. Review the tech stack to find the current application owner at GitLab.
Avoiding these examples can help ensure that the content you're producing follows a handbook first approach.
|Example||Suggested handbook first improvement|
|Introducing new content within a course or Pathway||Add new content to an existing handbook page, or open a new page to document|
|Directly uploading a public video to the LXP||Upload the video first to GitLab Unfiltered, emebed on the correct handbook page, and either display in an Articulate course via iframe in Level Up|