Toast Notification Stack
A corner stack whose live region is mounted before any message exists, errors announce assertively, and the auto-dismiss timer pauses on hover and on focus.
Which channel carries which event, so the loud ones can be moved rather than muted entirely.
components/notification-channel-list.tsxnpx hoverlab add notification-channel-list
Or over MCP, from your editor's agent — no account needed.
Free to read, copy and install, for personal and non-commercial projects. Shipping it in client work or a paid product needs Pro ($79 once). The source lands in your repo and stops being ours — no attribution, nothing to upgrade.
Start a page with this section — add more, order them, and leave with the page source.
The all-or-nothing toggle is why people mute products. Routing by event lets the two that matter stay loud while the rest go somewhere quiet.
Rendered live in your current theme — this is the same component whose source is below, not a screenshot of it.
'use client'
/**
* <NotificationChannelList> — Which channel carries which event, so the loud ones can be moved rather than muted entirely.
*
* The all-or-nothing toggle is why people mute products, and the layout
* problem is that routing has more than two states while a switch has two.
* The obvious wrong answer is a longer column of switches — same failure,
* more rows.
*
* Routing by event lets the two things that matter stay loud while
* everything else goes somewhere quiet, and the badge names the destination
* rather than an on/off state. That is what makes the panel skimmable: four
* rows, four destinations, one glance.
*
* The incident row says it ignores quiet hours. That is the setting most
* likely to be wrong in either direction, and it is worth stating on the row
* rather than burying it in a preferences page — someone who does not want
* to be woken has to be able to see that they will be.
*
* The announcements row mentions that the unsubscribe link is not buried.
* Small, and the kind of thing a notification settings panel should say out
* loud, because it is the promise that makes the rest credible.
*
* Rows are buttons with `aria-pressed` — a real implementation opens the
* channel picker behind one — and `status` is separate from `tone` so
* "push" and "digest" are readable without relying on colour. The demo
* selects the first row, the loudest one, since it is the setting most
* people come here to change.
*/
import * as React from 'react'
type Tone = 'neutral' | 'positive' | 'warning' | 'critical'
export interface NotificationChannelListRow {
id: string
label: string
detail?: string
tone?: Tone
/** What the badge says. Falls back to the tone name when absent. */
status?: string
}
export interface NotificationChannelListProps {
heading?: string
intro?: string
rows?: NotificationChannelListRow[]
className?: string
}
/*
Tones as complete utility classes, never assembled from fragments.
Tailwind scans source text, so `text-${tone}-foreground` produces no
class at all — the same failure as an undefined token, and just as
invisible in review.
*/
const TONE_CLASS: Record<Tone, string> = {
neutral: 'bg-muted text-muted-foreground',
positive: 'bg-primary/10 text-primary',
warning: 'bg-accent text-accent-foreground',
critical: 'bg-destructive/10 text-destructive',
}
const ROWS: NotificationChannelListRow[] = [
{ id: "row-1", label: "Production incidents", detail: "Push and email, immediately, ignoring quiet hours.", tone: "critical", status: "push" },
{ id: "row-2", label: "Someone mentions you", detail: "Push during working hours, batched into the digest outside them.", tone: "warning", status: "push" },
{ id: "row-3", label: "Build results", detail: "Digest only. Failures are already in the incident row above.", tone: "neutral", status: "digest" },
{ id: "row-4", label: "Product announcements", detail: "Email, monthly, and the unsubscribe link is not buried.", tone: "neutral", status: "email" },
]
export function NotificationChannelList({
heading = "Where each thing goes",
intro = "The all-or-nothing toggle is why people mute products. Routing by event lets the two that matter stay loud while the rest go somewhere quiet.",
rows = ROWS,
className,
}: NotificationChannelListProps) {
// Per-instance ids. A literal id in a reusable component is a
// collision waiting for the second copy on the page — and a <label>
// then resolves to whichever input rendered first.
const uid = React.useId()
const [selected, setSelected] = React.useState<string | null>(rows[0]?.id ?? null)
return (
<section
aria-labelledby={`${uid}-notification-channel-list-heading`}
className={`w-full bg-background px-6 py-16 ${className ?? ''}`}
>
<div className="mx-auto max-w-3xl">
<h2
id={`${uid}-notification-channel-list-heading`}
className="text-2xl font-semibold tracking-tight text-foreground"
>
{heading}
</h2>
<p className="mt-2 text-sm text-muted-foreground">{intro}</p>
<ul className="mt-8 divide-y divide-border overflow-hidden rounded-xl border border-border bg-card">
{rows.map((row) => {
const isSelected = row.id === selected
return (
<li key={row.id}>
{/*
A button, not a div with onClick. The row is operable, so
it has to be reachable by keyboard and announce its
selected state — aria-pressed is what carries that.
*/}
<button
type="button"
aria-pressed={isSelected}
onClick={() => setSelected(row.id)}
className={`flex w-full items-center justify-between gap-4 px-5 py-4 text-start transition-colors hover:bg-muted/60 focus-visible:outline-none focus-visible:ring-2 focus-visible:ring-ring focus-visible:ring-inset ${
isSelected ? 'bg-muted/40' : ''
}`}
>
<span className="min-w-0 flex-1">
<span className="block truncate text-sm font-medium text-foreground">
{row.label}
</span>
{row.detail ? (
<span className="mt-0.5 block text-sm text-muted-foreground">
{row.detail}
</span>
) : null}
</span>
<span
className={`shrink-0 rounded-full px-2.5 py-1 text-xs font-medium ${
TONE_CLASS[row.tone ?? 'neutral']
}`}
>
{row.status ?? row.tone ?? 'neutral'}
</span>
</button>
</li>
)
})}
</ul>
</div>
</section>
)
}
bg-card, text-muted-foreground) — it inherits your theme instead of overriding it.Drop it at components/notification-channel-list.tsx and import it where you need the section:
import { NotificationChannelList } from '@/components/notification-channel-list'1 of this block’s props are simple enough to drive from here. Change them and the block below re-renders — it is the same component whose source is above, not a mock of it. Everything else it accepts is in the table underneath.
Read out of the component’s own type and signature, so this cannot drift from the source below. Every prop has a default — the component renders standalone before you pass it anything.
| Prop | Type | Default |
|---|---|---|
heading | string | "Where each thing goes" |
intro | string | — |
rows | NotificationChannelListRow[] | ROWS |
className | string | — |
The same block rendered once to markup, wrapped as a file your framework compiles. Tailwind classes are framework-agnostic, so the design transfers intact — the behaviour does not.
This block is interactive. The markup below is its initial state with the event handlers stripped — you will need to re-wire the behaviour in your framework.
<!--
Notification Channel List — markup from the Hoverlab catalog.
This is the block rendered once to HTML and wrapped as a component
file. It is not a port of the React source: the Tailwind classes carry
the design, which is the part that took the work, and they are the same
in every framework.
This block is interactive in React and the handlers are NOT here.
Buttons, toggles and menus render in their initial state and do
nothing until you wire them up.
-->
<section aria-labelledby="_R_0_-notification-channel-list-heading" class="w-full bg-background px-6 py-16 ">
<div class="mx-auto max-w-3xl">
<h2 id="_R_0_-notification-channel-list-heading" class="text-2xl font-semibold tracking-tight text-foreground">Where each thing goes</h2>
<p class="mt-2 text-sm text-muted-foreground">The all-or-nothing toggle is why people mute products. Routing by event lets the two that matter stay loud while the rest go somewhere quiet.</p>
<ul class="mt-8 divide-y divide-border overflow-hidden rounded-xl border border-border bg-card">
<li>
<button type="button" aria-pressed="true" class="flex w-full items-center justify-between gap-4 px-5 py-4 text-start transition-colors hover:bg-muted/60 focus-visible:outline-none focus-visible:ring-2 focus-visible:ring-ring focus-visible:ring-inset bg-muted/40">
<span class="min-w-0 flex-1">
<span class="block truncate text-sm font-medium text-foreground">Production incidents</span>
<span class="mt-0.5 block text-sm text-muted-foreground">Push and email, immediately, ignoring quiet hours.</span>
</span>
<span class="shrink-0 rounded-full px-2.5 py-1 text-xs font-medium bg-destructive/10 text-destructive">push</span>
</button>
</li>
<li>
<button type="button" aria-pressed="false" class="flex w-full items-center justify-between gap-4 px-5 py-4 text-start transition-colors hover:bg-muted/60 focus-visible:outline-none focus-visible:ring-2 focus-visible:ring-ring focus-visible:ring-inset ">
<span class="min-w-0 flex-1">
<span class="block truncate text-sm font-medium text-foreground">Someone mentions you</span>
<span class="mt-0.5 block text-sm text-muted-foreground">Push during working hours, batched into the digest outside them.</span>
</span>
<span class="shrink-0 rounded-full px-2.5 py-1 text-xs font-medium bg-accent text-accent-foreground">push</span>
</button>
</li>
<li>
<button type="button" aria-pressed="false" class="flex w-full items-center justify-between gap-4 px-5 py-4 text-start transition-colors hover:bg-muted/60 focus-visible:outline-none focus-visible:ring-2 focus-visible:ring-ring focus-visible:ring-inset ">
<span class="min-w-0 flex-1">
<span class="block truncate text-sm font-medium text-foreground">Build results</span>
<span class="mt-0.5 block text-sm text-muted-foreground">Digest only. Failures are already in the incident row above.</span>
</span>
<span class="shrink-0 rounded-full px-2.5 py-1 text-xs font-medium bg-muted text-muted-foreground">digest</span>
</button>
</li>
<li>
<button type="button" aria-pressed="false" class="flex w-full items-center justify-between gap-4 px-5 py-4 text-start transition-colors hover:bg-muted/60 focus-visible:outline-none focus-visible:ring-2 focus-visible:ring-ring focus-visible:ring-inset ">
<span class="min-w-0 flex-1">
<span class="block truncate text-sm font-medium text-foreground">Product announcements</span>
<span class="mt-0.5 block text-sm text-muted-foreground">Email, monthly, and the unsubscribe link is not buried.</span>
</span>
<span class="shrink-0 rounded-full px-2.5 py-1 text-xs font-medium bg-muted text-muted-foreground">email</span>
</button>
</li>
</ul>
</div>
</section>
What each framework gets across the whole catalog — effects convert properly; this rung is markup.
The component, its props, the design tokens it expects and the command that installs it — as one prompt. Paste it into Claude, Cursor, v0 or ChatGPT and what they build around it will match the rest of the catalog instead of inventing its own system.
Want the whole screen instead of this one section? Open a page and copy it entire.
All of them free to read, copy and install — no account, no locked tiles, no watermarked preview. The whole catalog is open, and so are the API and the CLI.
Browse NotificationsCopying the code is free. Putting it in client work or a paid product is what Pro is for — the licence, not the access.
A corner stack whose live region is mounted before any message exists, errors announce assertively, and the auto-dismiss timer pauses on hover and on focus.
The bell panel: filterable list with read state, the unread count in the accessible name rather than only in a badge, and machine-readable timestamps beside the human ones.
Per-event, per-channel switches as a real table, with required notifications locked and explained, and column headers that toggle a whole channel and report a mixed state honestly.
The soft ask before the browser dialog you only get one shot at — what will be sent, what will not, and a decline of the same weight as the yes.
A day's notifications collapsed into one digest, grouped by what they are rather than when they arrived.
The control that turns notification volume down instead of off, which is the choice most people actually want.