Triage design system v0.13.1-experiment
Home / Components / Feedback & states

Feedback & states

Banners, toasts, empty states and in-flight treatments — the three-channel feedback standard.

Banners & callouts

Informational note (tint-acc).
Success banner — saved.
Warning banner — saved, but the index did not rebuild.
redirect → .msg flash (ok/warn/err only; info retired); in-place JS → toast(); one toast at a time
<div class="note">Informational callout (blue tint)</div>
<div class="msg ok">Result message lines</div>
<div class="msg warn">Partial outcome</div>
<div class="msg err">Failure with a specific reason</div>

Toasts — live

calls the real toast(msg, kind) from js/shell.js into #toasts
top-right on desktop, bottom on phones; black slab with a left colour rail; ~5s auto-dismiss
toast('Rule ‘News’ disabled.', 'ok');
toast('Saved, but the index did not rebuild.', 'warn');
toast('Delete failed — still queued.', 'err');

Empty state

Nothing here yet

What will fill this area and why it is empty right now.

optional icon slot (30px, 40% opacity) + h4 + one-line reason + at most one CTA; never a bare blank area or bare “failed”
<div class="empty">
  <h4>Nothing here yet</h4>
  <p>Why it is empty and what will fill it.</p>
  <a class="btn primary">One action</a>
</div>

In-flight and loading

trigger disabled while a long job runs; honest progress with counts
submit guard covers forms; long-running jobs additionally disable their trigger and show counts
<button class="btn primary" disabled>Queued…</button>
<div class="progress"><i style="width:64%"></i></div>
<div class="skeleton" style="height:14px"></div>

Full-page states

404

Nothing at this address

The page moved or never existed. Your mail and rules are untouched.

ref 7f3a · 2026-10-06T09:58Z
same anatomy for 404 / 500 / 403 / offline / maintenance: icon, code, plain-language title, one sentence, at most two actions, a reference line for support
<div class="page-state">
  <div class="ps-icon">…svg…</div>
  <div class="ps-code">404</div>            <!-- 500 · 403 · offline · maintenance -->
  <h2>Nothing at this address</h2>
  <p>What happened, in one sentence, plus reassurance.</p>
  <div class="ps-actions"><a class="btn primary">Recovery action</a><a class="btn">Secondary</a></div>
  <div class="ps-meta">ref {{request_id}} · {{timestamp}}</div>
</div>
State copy rules. The code is for support (mono, secondary); the title is human and blames no one; the paragraph says what is unaffected; the reference line exists so screenshots can be traced. Maintenance and permission variants reuse the same skeleton — never a bare “failed”. source
Three channels, no fourth. Server redirect → flash banner at the top of content. In-place JS/fetch → toast. Long job → disabled trigger + progress. No page-local toast markup, no query-param toasts.
Triage Design System v0.13.1-experiment — the central, app-agnostic UI design authority. Source of truth: /tokens/tokens.json. Showcase chrome only: site/.