The following tips will help you avoid unexpected results when creating, sharing, and publishing Articulate Presenter 360 projects.
- Create, Edit, and Publish Projects on Your Local Hard Drive
- Save, Version, and Backup Projects Frequently
- Send Projects to Other Developers When You Need to Collaborate
- Host Published Content Online
- Optimize File Paths and Naming Conventions
Always save and publish on your local hard drive (typically your C: drive). Working on a network drive or an external (USB) drive can cause erratic behavior, such as file corruption, an inability to save changes, and loss of project resources due to latency.
If you need to place a copy of your project on a network drive or an external drive for backup purposes, create an Articulate Package first (see below), then move the package to your network or external drive. If you need to edit or publish the project again later, move the Articulate Package back to your local hard drive and fully extract it before opening the presentation.
An Articulate Package is a zip file that contains a copy of your entire project, including the PowerPoint file, the Articulate Presenter file with audio/video resources, quiz files, and interaction files. Here's how to create an Articulate Package:
- Do one of the following, depending on your version of PowerPoint:
- PowerPoint 2013 or 2016: Go to the File tab on the PowerPoint ribbon, click Share, and choose Articulate Package.
- PowerPoint 2010: Go to the File tab on the PowerPoint ribbon, click Save & Send, and choose Articulate Package.
- When the Articulate Presenter Package window appears, choose a Package Location. By default, the zip file will be created in the same location where your PowerPoint file is stored, but you can change it. Just click the ellipsis (...) button and browse to a different folder.
- Modify any of the optional Package Notes and click Create Package.
- When the Publish Successful window appears, you'll have an option to open the folder where the zip file was created. Click Close when you're done.
Save your work often. The keyboard shortcut Ctrl+S is the fastest way to save. Do it so often it becomes muscle memory. You’ll be glad you did.
Create versions of your project during its development cycle so you can go back to earlier versions when necessary. Just create a new Articulate Package of your project as described above and give the resulting zip file a slightly different file name. For example, you might make a new version at the end of each work day and add the date to the file name so you can easily identify it.
Versioning is also a good way to backup your work. Just save earlier versions to the cloud, a network drive, or an external hard drive for safekeeping. (But always save the current version on your local hard drive.)
If you need to share a Presenter project with another developer, create an Articulate Package as described above.
Then send the resulting zip file via email, external drive, network drive, etc.
Recipients should save it to their local hard drives and fully extract it before opening the project.
Viewing published content on your local hard drive or a network drive isn't supported. Security restrictions in these environments can cause various features in your content to fail.
To avoid unexpected behavior during playback, host your content in the location for which it was published. For example, if you published for web, upload your content to a web server; if you published for a learning management system (LMS), upload it to an LMS.
The published output for a course includes multiple files and folders. For your course to work properly, these files and folders must remain in the same organizational structure when you upload them to a server.
Be sure the file paths to your projects and published output are well under the 260-character limit imposed by Microsoft Windows. (Publishing adds characters to the file path you selected. If it exceeds 260 characters, your published output will be incomplete.)
Avoid using special characters, accents, or symbols in your file paths and file names. Learn more about naming conventions in this Microsoft article.