Notifications
In-app notification surfaces — a stacked feed panel, a single content card, and a corner count badge.
Preview
4 New Notifications
Recent notifications
-
Scheduled Downtime 5 min agoServers will be offline tonight at 11 PM.
-
System Update 20 min agoYour app was updated to v2.3.1.
-
New Invite 1 hour agoYou've been added to the Design Team.
-
Security Alert 6 hours agoUnrecognized login attempt detected.
Controls
Device view renders in an isolated frame so real responsive breakpoints apply. Switch to Full for overflowing popovers.
Installation
php artisan ui:add notification-panel
Behavior layer (Alpine)
This component installs a self-registering Alpine module to
resources/js/ui/notification-panel.js. Import the behavior layer once
from your bundle so it loads (it hooks alpine:init):
import './notification-panel.js';
Registry contract
Install confidence
php artisan ui:add notification-panel
writes only the generated targets below. The CLI validates each file hash before writing and
prompts before replacing local changes unless --force is used.
- Version
- 1.0.0
- License
- open
- Stability
- stable
- Contract
- v2
- Foundation
- ≥ 1.0.0
| Type | Generated target |
|---|---|
| blade | resources/views/components/ui/notification-panel.blade.php |
| js | resources/js/ui/notification-panel.js |
Registry dependencies
None.
Package dependencies
composer: jml/brok:^1.0
npm: alpinejs
Guidance
Persistent message and notificationKeep an important message visible near its context.
Use when
- Use for important messages that should stay visible long enough to read and act on. Do not downgrade important guidance into transient messaging users can miss.
Avoid when
- Avoid using notification-panel as a default simply because it is available in the library. Choose it only when its interaction cost, visibility, and behavior match the job to be done.
- Task length
- micro
- Interaction cost
- low
- Interruptiveness
- medium
- Input precision
- none
- Mobile / touch risk
- low
- Accessibility risk
- high
- Needs background context
- Yes
- Comparison needed
- No
Preferred alternatives
- Toast for low-priority confirmation
Anti-patterns
- Downgrading important outcomes to transient feedback
API
manifest knowledge + registry-derived coverageProps
| Prop | Type / values | Default | Description |
|---|---|---|---|
| notifications | array | [ | Declared by @props in the registry Blade source. |
| open | bool | false | Declared by @props in the registry Blade source. |
Slots
Components use the default Blade slot unless a documented subcomponent is installed by the registry item.
Data slots
notification-panel
Capabilities
Behavior
- Uses server-rendered Blade and semantic HTML.
- Installs a JavaScript behavior module when the registry item includes resources/js/ui files.
- Declares registry capability flags: a11y, interactive, responsive, rtl, darkMode, localized.
Usage
<div class="p-6">
<x-ui.notification-panel />
</div>
Accessibility & localization
data-slot
Keyboard focus-visible
Localized labels
- Accessibility target: wcag-2.2-aa-target.
- Uses semantic HTML and a stable
data-slotattribute for styling/scripting hooks. - Focus-visible rings use the
ringtoken so keyboard focus is always visible. - Disabled and invalid states are conveyed to assistive tech, not by color alone.
- Targets WCAG 2.2 AA; verify contrast in light, dark, admin and customer surfaces above.
- Labels go through
__()and the component uses logical properties (ms-*,text-start,start-*) so it mirrors correctly — flip the preview to RTL to confirm.
Source
The exact, editable file ui:add writes
into your app — copy it or own the whole thing. Previews
render this same code; there are no preview-only components.
Changelog
Current version: v1.0.0. See the site changelog for the full release history.