Engage 360: Publishing and Sharing Content
Article Last Updated
This article applies to:
If you view an Engage 360 interaction on your local hard drive (or send it to others to view on their local hard drives), you'll encounter security restrictions from the computer, web browser, and network that can cause various features of the interaction to fail. To test your published content and share it with others, upload it to the environment for which it was published. See each of the publishing options below for details.
Publish to Review 360
Publish your interaction to Review 360 to collect feedback from stakeholders and track version history. It’s a great way to collaborate on a project before distributing the finalized interaction to learners.
If your stakeholders are new to Review 360, you can share this user guide with them.
Publish for Web Distribution
If you don't need to track learners' progress or results, then web publishing is a good option.
- First, publish your interaction for web distribution.
- Then, do any of the following to get your interaction onto a web server:
- Use the FTP option on the Publish Successful dialog to upload the published files to a web server.
- Use your own FTP client to upload the published files to a web server.
- Give the published files to your server administrator to upload to a web server.
- Finally, give learners the URL for the
interaction.htmlfile, which is the file that launches your interaction.
If you don't have access to a web server, here are some free options:
- Amazon S3 offers free hosting with generous usage limits. If you go over your limit, you'll be charged a small fee. See this video tutorial by Tom Kuhlmann to learn more about Amazon S3.
- Google Cloud also has a free hosting service. You'll be charged a small fee if you go over the free limit. See this video tutorial by Tom Kuhlmann to learn more about Google Cloud.
Publish for LMS Distribution
If you need to track learners' progress and results, another great option is to use your own learning management system (LMS). Engage 360 supports Tin Can API (xAPI), SCORM 2004, SCORM 1.2, and AICC LMSs.
- First, publish your interaction for LMS distribution.
- Then, click the Zip option on the Publish Successful dialog and upload the zip file to your LMS.
- Finally, invite learners to your LMS to view the interaction.
If you're not sure how to upload content to your LMS or invite learners, check with your LMS provider for instructions.