If you’re planning to share snippet groups with your team, there are a few things to keep in mind.
Remove personal information.
If you are revamping already existing snippets into a shared group, remove any personal information, such as your own email address or name. A neat way to include personal information in shared snippets is through nested snippets.
Snippets have an “abbreviation,” the “content” that abbreviation expands, and a “label.” Fill in the label field with a summary of the snippet. This way everyone can understand what the snippet is for. Also, fill in any keywords / search terms to help everyone locate the snippet.
Apply consistent naming.
Choose a snippet abbreviation convention for naming consistency. Here are a few tips:
Encourage the use of official snippets over personal snippets for key content.
If your team is already using TextExpander they likely have their own versions of some of the snippets you’re making. Once you put out the new “official” versions they will likely have different abbreviations than the team had for themselves. This means re-learning abbreviations. To make this easier on the team, it is possible to alias snippets. This way they can expand “official” content and keep using personal abbreviations.
Add snippet group instructions.
In each group’s settings is a Note field. Use this field to explain how you want the team to use the group.
Group snippets into specific topics.
This makes it easier to share with just the people who need that group. For example, the Support team might have a group just for their answers about the iOS platform and the IT team might have a group just for SQL.