Alerts (web)

Summary

The nine toasts and ten browser confirms the website raises, with the strings it ships.

Raw wireframe

• .context/designs/web/patterns/alerts.html

Copy

The wireframe is the list. It was written from apps/website/src on 2026-10-02 and sits beside patterns/toasts.html, which is the visual rule for a toast; this page is the wording.

• Toasts come from two places only: categorising a transaction (ExpenseTransactions, CategoriseModal) and the profile form (ProfileSection). An error toast's second line is a fallback — presentError(err, "Try again.") — and the server's sentence replaces it when there is one.
• Confirms are window.confirm, so the browser draws the box: one message, Cancel and OK, no title and no way to colour the destructive button. Seven of the ten delete, replace, remove or revoke something.
• Three toasts and five confirms interpolate — a category, a merchant, an email, a count, a week. They are drawn with a real value in place, and Categorised is drawn twice because its second line has two forms.

Flows that touch this surface

• None. A toast and a confirm are raised over the page that owns them.

Entities referenced

• copy-strings
• voice

Sources

• apps/website/src — every toast( and window.confirm( call
• .context/designs/web/patterns/alerts.html
• scripts/check-designs.py — the copy check, which reads these two raisers for a web surface