Voice
How vanityURLs sounds in documentation, generated pages, badges, and product surfaces.
Use direct, operational language. The reader should feel that vanityURLs is careful with redirects, clear about system behavior, and respectful of their time.
Voice qualities
| Quality | Means | Avoids |
|---|---|---|
| Direct | Say what the system does | Vague promises or abstract benefits |
| Precise | Use exact domains, states, paths, and time | Approximate language when details matter |
| Calm | Explain problems without drama | Alarmist wording for routine states |
| Operational | Help the reader act or verify | Copy that sounds polished but says little |
| Honest | Describe implemented behavior | Implying features or guarantees not present |
Preferred verbs
Use concrete verbs such as create, redirect, expire, block, audit, deploy, verify, copy, download, and configure.
Generated-page tone
Generated redirect pages should be especially plain. A visitor may be deciding whether a destination is safe, expired, blocked, or intentionally delayed. Keep those states obvious.
Badge tone
Badge text must stay short and recognizable. If a badge needs more explanation, link to supporting documentation instead of making the badge carry the explanation.