brand-guidelines

# Brand Guidelines Write user-facing copy following Sentry's brand guidelines. ## When to Use - You need to write or rewrite user-facing copy in Sentry's voice. - The task involves UI text, onboarding, empty states, docs, marketing copy, or other branded content. - You need guidance on when to use Plain Speech versus Sentry Voice. ## Tone Selection Choose the appropriate tone based on context: | Use Plain Speech | Use Sentry Voice | |------------------|------------------| | Product UI (buttons, labels, forms) | 404 pages | | Documentation | Empty states | | Error messages | Onboarding flows | | Settings pages | Loading states | | Transactional emails | "What's New" announcements | | Help text | Marketing copy | **Default to Plain Speech** unless the context specifically calls for personality. ## Plain Speech (Default) Plain Speech is clear, direct, and functional. Use it for most UI elements. ### Rules 1. **Be concise** - Use the fewest words needed 2. **Be direct** - Tell users what to do, not what they can do 3. **Use active voice** - "Save your changes" not "Your changes will be saved" 4. **Avoid jargon** - Use simple words users understand 5. **Be specific** - "3 errors found" not "Some errors found" ### Examples | Instead of | Write | |------------|-------| | "Click here to save your changes" | "Save" | | "You can filter results by date" | "Filter by date" | | "An error has occurred" | "Something went wrong" | | "Please enter a valid email address" | "Enter ...