Feedback
Alert
Severity semantics, inline layout, optional actions, and explicit dismissal — never a toast.Scheduled maintenance
Sync pauses on Sunday from 02:00 to 04:00 UTC.
Choose it deliberately
Use the component when its interaction contract matches the user task.
Use when
A message must stay visible next to the form, section, or content it explains.
Avoid overloading
Do not use it as a toast, a dialog, or a notification queue, and keep retry state in the application.
Composition
Sizing, labels, and neighboring elements should preserve visual hierarchy.
One primary meaning
Title states the problem, body explains recovery; long labels wrap instead of overflowing.
Few actions
Many actions signal that MBanner or another content surface fits better.