Best practices for attaching PDFs

When you attach a PDF or other file, it gets saved as part of the project. Thus, if you transfer the .story file to someone else, they could publish it, and the attachment would be there. 

This also means that if you update the original file, the attachment in the .story file doesn't get updated. Instead, you have to replace it with the updated version. Thus, in addition to having a good version-control process for the .story file, you need a good version-control process for attachments.

More re: best practices: Storyline files should only be opened from your hard drive. If multiple people will be working on the same file, you need to have a good process in place for backing up the .story file, as well as the other source files needed for the project. For example, be sure to back up any special images or illustrations, videos, and the editable source files for any attachments. I also recommend backing up audio transcripts and/or other script materials. 

FYI: Articulate recently added a feature that saves a copy of the .story file when you publish to Review 360. Here's more info about that:

• https://community.articulate.com/discussions/articulate-storyline/new-in-storyline-360-cloud-backup-beta 

More FYI: Here's the User Guide info about attachments:

• https://community.articulate.com/series/articulate-storyline-360/articles/articulate-storyline-360-user-guide-how-to-attach-resources