Info messages
Something worth knowing, said without interrupting what the crew is doing.
On this page
High water 16:42 UTC. The current turns north in 2 hr 5 min and will set you toward the shore.
An info message gives the crew something useful to know: a change coming, a reason behind something they see, a fact that helps them plan. It never asks for an action, and it never interrupts. If it needs an action, it is an attention message.
Anatomy
- Title (optional): the subject in a few words.
- Body: the fact and why it matters. One or two sentences.
- Action (optional): one link to learn more or open the related page. Never a required step.
Voice and tone
Where info messages go
- Inline, beside the value or control they explain.
- On the situation board as an info-level item, without a severity shape, for conditions that matter to everyone on watch.
- Spoken only when the crew asked a question, or when the fact changes what they are about to do.
Match the message to its scope
Use InlineMessage for one field's context, SectionMessage for a panel, and Banner for a condition affecting the whole view. A persistent note belongs near the content it explains. Avoid repeating the same notice in every row or turning routine updates into assertive announcements.
For a report, name the assumption or limitation and its effect on the conclusion. “Illustrative data” belongs beside the example; a source caveat belongs beside the affected measurement or figure. An informational note does not change the evidence or grant approval.