Glossary of terms Follow
The following is a glossary of key terminology:
| Term | Definition |
|---|---|
| Actions | An action is a behavior that is triggered when interacting with an asset, e.g. an action on a button asset might be to go to another screen within the project or show a sub-screen. |
| Assets | An asset is a content item that can be added to a screen within a project (e.g. text, graphic, video, question, comic strip). |
| Branching | A method of navigating content within a project in a non-linear fashion, e.g. within a topic you may wish to display content based on employee type and would therefore use branching to create different content journeys for the different employee types. |
| Columns | Content added to a screen is mapped to content blocks that support 1-4 columns. When viewed on smartphone devices, the content columns will collapse down into a single column layout in a vertical sequence to ensure the content is in the correct order. |
| Content Block | A content block is a container in which content columns are configured. A screen can support multiple content blocks if required. |
| Editor | The authoring interface is used to create the content screens available in a project. |
| Extras | Extras are additional elements available within a project to provide enhanced functionality (e.g. a help section or glossary). |
| HTML5 | HTML5 is the markup language used to build a published project. |
| Locked for editing | When a topic is being edited by another user in an account, it will be locked so that other users cannot edit it at the same time. When the user closes the editor for that topic, the lock will be removed. Administrators have the capability to remove a lock if needed by right-clicking on the topic and selecting the ‘remove lock’ option. |
| LMS | LMS, or Learning Management System, is an online system used to deploy and track e-learning for end users. When a project is published in Gomo, the zip file that is produced can be uploaded to an LMS. |
| Multi-device | Gomo allows you to create content that will work on desktops, tablets, and smartphones which we commonly refer to as ‘multi-device’. |
| Portal | The online portal is used to access all features and functionality available within Gomo. |
| Player | When you create a project in Gomo and publish it, the published content combined with the selected (or customized) theme is referred to as the player. |
| Publish | The process of taking the project content, settings, and theme and publishing it as an HTML5-based output. |
| Resources | Media files that you want to include in your project (e.g. images, audio, video and PDFs). |
| SCORM 1.2 | The LMS tracking method is available within Gomo. |
| Screen lock | The option to restrict end-users from progressing to the next screen until they have interacted with all appropriate elements on the current screen. |
| Screens | Screens are the individual pages a learner would see when navigating through content created in Gomo. When creating content in Gomo, the screens within a topic are created using the content editor. |
| Sub-screens | Within a screen, you can also create sub-screens to show content that you might only want to display when a user carries out a specific action (e.g. clicks on a button). |
| Topic lock | The option to restrict end-users from progressing to the next topic until the current topic has been completed. |
| Topics | Projects created in Gomo are built on content topics as a way of segmenting your content into meaningful sections (you can think of them as chapters). |
| User role |
When accessing Gomo, a user-type role will have been assigned to your user account. The user roles available are: Administrator Has complete access to all the features and functionality available within the Gomo portal. If the administrator is also flagged as the account owner, they will have additional access to the account setting to allow them to manage and maintain their Gomo subscription settings. Editor Has the ability to add and edit content to projects they have access to. Reviewer Has the ability to review projects they have access to. |
| Variables | Variables can be created at an account or project level and can be used within text assets in a course. When a course is previewed or published, the variable within a text asset will be replaced with the value that was originally assigned. |
Comments
0 comments
Article is closed for comments.