Copywriting is a design element. The words used in buttons, headings, descriptions, error messages, and tooltips shape the user’s understanding of the platform just as much as visual design does.

Voice and Tone

The Alius voice is:

  • Clear — say what you mean, directly and simply
  • Restrained — do not exaggerate, boast, or over-promise
  • Engineering-driven — respect the user’s technical intelligence
  • Friendly — warm and approachable, not cold or corporate
  • Not exaggerated — no superlatives, no hype, no marketing language

Alius speaks to developers, engineers, researchers, and students as capable professionals. The copy should feel like a knowledgeable colleague explaining something clearly, not a salesperson pitching a product.

Use clear, action-oriented language:

  • “Start configuring” — not “Begin your journey”
  • “Download resources” — not “Get everything you need”
  • “View examples” — not “Explore endless possibilities”
  • “Copy command” — not “Harness the power”
  • “Check connection” — not “Verify your destiny”
  • “Reset to defaults” — not “Start fresh”
  • “Install the CLI” — not “Unlock the full potential”
  • “Read the docs” — not “Dive into knowledge”
  • “Report an issue” — not “Tell us your pain points”
  • “View source on GitHub” — not “Join the revolution”

Copy to Avoid

Avoid marketing-driven, exaggerated, or vague language:

  • “Empower the future”
  • “Disrupt everything”
  • “One click to change the world”
  • “Unleash the power of AI”
  • “Next-generation intelligent experience”
  • “Seamlessly integrated”
  • “Revolutionary platform”
  • “Industry-leading”
  • “Game-changing”
  • “Cutting-edge”

Context-Specific Guidelines

Buttons and Actions

  • Use verbs: “Download”, “Create”, “Delete”, “Save”, “Cancel”
  • Be specific: “Export as CSV” instead of “Export”
  • Show consequences for dangerous actions: “Delete project” instead of “Delete”

Error Messages

  • Explain what happened: “Connection timed out after 30 seconds”
  • Explain why: “The device may be offline or the network may be unstable”
  • Suggest a fix: “Check your network connection and try again”

Empty States

  • Explain the situation: “No devices have been added yet”
  • Provide a next step: “Add your first device to get started”

Tooltips and Helper Text

  • Be concise: explain only what is not obvious from the UI
  • Provide examples: “Enter the device IP address (e.g., 192.168.1.100)“

Headings and Titles

  • Use descriptive, scannable headings
  • Prefer noun phrases for reference pages: “Configuration Parameters”
  • Prefer verb phrases for guides: “Setting Up Your First Robot”

Documentation

  • Write in present tense and active voice
  • Address the reader directly with “you” (not “the user”)
  • Use short paragraphs and bullet lists for readability
  • Include code examples alongside explanations