Foundations · Content

Messages

Messages explain what happened, what it means, and what someone can do next. Use these patterns for empty states, inline flags, and lightweight education in Nexus People OS agents and dashboards.

Message types

Match the component to the moment. Keep titles short, put the most important detail first, and offer one clear action when possible.

Shared rules

  • Lead with the outcome (“Couldn’t sync calendar”), not the error code.
  • Use sentence case for titles; skip ending punctuation on titles.
  • Pair every problem message with a next step when you can.
  • Don’t stack more than one flag for the same event.