Writing guidelines
Practical rules and standards for writing consistent, clear, and user-centered content across the Tendoo platform.
Writing guidelines
These guidelines help you write content that’s clear, consistent, and easy to use. They apply to all interface text, documentation, and user-facing content in the Tendoo system.
Follow these rules to align with our voice, support accessibility, and keep every message helpful and human.
✅ Use Sentence Case
Use sentence case for most UI text — labels, headings, buttons, and notifications.
✅ “Create new project”
🚫 “Create New Project”
📣 Write in Active Voice
Tell users who’s doing what, and keep things direct.
✅ “You can reset your password.”
🚫 “Passwords can be reset.”
🧠 Use Present Tense
Present tense keeps content simple and immediate.
✅ “Your changes are saved.”
🚫 “Your changes have been saved.”
🔁 Be Consistent
Use the same terms for the same things — throughout the product and documentation.
✅ Always use “Sign in”
🚫 Don’t switch between “Sign in” / “Log in” / “Login”
📝 Use Clear and Direct Language
Avoid buzzwords, slang, or overly technical jargon (unless writing for a developer audience).
✅ “We couldn’t find your file.”
🚫 “The requested resource could not be located.”
❌ Avoid Redundant Words
Write only what the user needs. If it doesn’t help, cut it.
✅ “Upload file”
🚫 “Please kindly upload your file to continue”
📎 Link Text Should Be Descriptive
Make link text meaningful without needing surrounding context.
✅ “Download the Tendoo app”
🚫 “Click here”
🧩 Use Placeholders Correctly
Keep variables like {name} or {count} intact and unaltered.
✅ “Hi, {name}”
🚫 “Hello { name }!”
📐 Use Consistent UI Terms
| Action | Label |
|---|---|
| Sign in | “Sign in” |
| Submit form | “Submit” |
| Next step | “Continue” |
| Remove | “Delete” |
Related
These guidelines keep Tendoo’s content unified, clear, and helpful — so users can focus on their goals, not the interface.