Alerts are written by hand in about twenty variants, and the design system has no part for a notice #167

New Issue

2026-10-06T07:58:02Z

cgalo5758 commented

2026-10-06 07:58:02 +00:00

The question

The console writes every alert by hand: about twenty combinations of Bootstrap's alert classes appear across 45 templates and in Go strings, each with its own padding, size and margins. Dismissing one is built three ways: alert-dismissible on the organization types page, an htmx × on the operator setup banner, and the same × reused for the FedWiki sites list's notices. Two alerts in one card can differ in height. Forms have one library and a lint; alerts have neither. What is the notice part: which meanings it carries, which sizes, how it is dismissed, and what stops a hand-written alert from coming back?

What depends on the answer

Every page that tells a person something happened, went wrong or is about to happen. #22 asks the same question for previews. Notices that integrations declare, which the console will render, need the same part.

Options known so far

One part with tones named by meaning (problem, warning, done, information, preview), two sizes (page and inside a card), a dismissible variant that either posts the dismissal or only closes, and a lint that refuses alert markup outside it, as the anatomy lint does for badges.
Bootstrap's alerts as they are, with a written rule per meaning and size and no lint.

Decided when

The design system names the part, every alert renders through it, and the lint refuses one written by hand.

## The question The console writes every alert by hand: about twenty combinations of Bootstrap's `alert` classes appear across 45 templates and in Go strings, each with its own padding, size and margins. Dismissing one is built three ways: `alert-dismissible` on the organization types page, an htmx × on the operator setup banner, and the same × reused for the FedWiki sites list's notices. Two alerts in one card can differ in height. Forms have one library and a lint; alerts have neither. What is the notice part: which meanings it carries, which sizes, how it is dismissed, and what stops a hand-written alert from coming back? ## What depends on the answer Every page that tells a person something happened, went wrong or is about to happen. #22 asks the same question for previews. Notices that integrations declare, which the console will render, need the same part. ## Options known so far - One part with tones named by meaning (problem, warning, done, information, preview), two sizes (page and inside a card), a dismissible variant that either posts the dismissal or only closes, and a lint that refuses `alert` markup outside it, as the anatomy lint does for badges. - Bootstrap's alerts as they are, with a written rule per meaning and size and no lint. ## Decided when The design system names the part, every alert renders through it, and the lint refuses one written by hand.

cgalo5758 added the

kind

design

area/operator-ui area/member-ui labels 2026-10-06 07:58:02 +00:00

cgalo5758 referenced this issue

2026-10-06 08:12:35 +00:00

The console has no notifications #168

cgalo5758 commented

2026-10-06 08:12:40 +00:00