On October 29, a new design proposal for WordPress Feature Notifications outlined a shared way to show site activity across WordPress, replacing today’s patchwork of plugin notices, banners and inbox cards with a common system.
In short: the proposal is a second prototype, not a change scheduled to ship in WordPress core. It sketches one notification tray for admin screens, the editor and the front of a site, with rules for how plugins submit messages. Existing plugins, notices, APIs and hooks would keep working while the project gathers feedback.
What the WordPress Feature Notifications proposal changes
The October 29 Core post starts with a familiar admin problem: plugins deliver information in different places and formats. A failed payment or security update can sit alongside promotions and routine reminders, while notices may push the page down.
The proposed answer is a common notification tray, available from every admin screen, within the editor and on the site’s front end. Each item would open to show what it concerns, who sent it and a clear next step. The design aims to keep unresolved problems visible while placing less urgent items out of the way.
This is a design direction, not a core feature announcement. The post says the work is not finished and will not ship soon. A feature plugin version 0.3.0 comes first; any later move into core would follow that step. Plugins would also adopt the system at their own pace.
Plugins would send information, not custom layouts
The second prototype responds to feedback on an earlier version, which left questions about how much of the interface each plugin could control. In the new proposal, plugins send notification data and choose from four layouts: Standard, Object, Conversation and Group. Core would define the system’s values, while plugins fill in the fields.
The proposal describes five dimensions that can affect a notification, including its type, severity, intent, read state and sender status. For example, a payment dispute could be marked critical and operational, remain unread, and show a status such as “Needs response” before later changing to “Won.”
Critical items would stay at the top until resolved and turn the bell’s count red. An Alerts tab would collect critical notifications and warnings. The design also proposes limits on repeated messages: repeats could replace earlier entries, similar items could be grouped, and users could switch off tips and offers.
These rules are intended to make notifications more consistent across plugins. They do not remove the existing admin-notice system. The post explicitly says current notices and custom notices will continue to work, and no APIs or hooks are being removed.
Important design questions remain open
The post asks developers and site users to weigh in on several parts of the prototype. One question is whether notifications should use a distinct badge for each type, such as orders or comments, or a smaller set of generic badges that would not grow as plugins add new categories.
Severity is another open point. The prototype has three levels: critical, warning and informational. Critical items stay pinned, warnings appear in Alerts and informational messages make up the rest. The post asks whether three levels are enough and who should be allowed to label a message critical. It proposes that promotional messages can never receive critical status.
There are also questions about message details and delivery. The design could use existing metadata to store who performed an action and what object it concerns, but those values would remain optional and loosely defined. The proposal asks whether core should instead add shared fields that every plugin fills in the same way.
For delivery, the same event might reach a person through the notification bell, an admin-menu count, email or a mobile push. The post says the project needs to review events across those channels so a user gets each message in the right place, without receiving it repeatedly.
Accessibility and notification controls need testing
The prototype follows the WordPress.com panel’s keyboard model: arrow keys move through the list, Enter opens a notification, and Escape returns to the list or closes the tray. The post asks whether that interaction works well with screen readers and other assistive technology. Accessibility feedback is part of the request, not a claim that the design has passed testing.
Settings also need more work. The concept lets people mute notifications by channel, such as WooCommerce orders, and turn off a plugin’s tips with one switch. The author notes that these controls could become difficult to manage when many plugins send several notification types.
What developers and site owners can do now
There is no immediate migration to plan: current notices keep working, and the proposal does not announce a release date for core. For now, the practical step for plugin developers is to review the proposed rules and identify where their messages would fit, especially around severity, repeated notifications and the data attached to an event.
The project plans to test the system against more plugins. WooCommerce was the first deep test; Jetpack is named as the next place to try the shared catalog and see where its rules need adjustment. Feedback is welcome in the post’s comments, in GitHub issue #655 and in the #feature-notifications Slack channel.
FAQ
Is the notification tray included in a WordPress release?
No. The October 29 post presents a design prototype, not a feature shipping in a named WordPress release. The feature plugin’s 0.3.0 version comes first, and a later move into core would follow.
Will existing WordPress admin notices stop working?
No. The proposal says existing notices, including custom ones, will continue to work. It does not remove APIs or hooks.
How can developers give feedback on the design?
Developers can comment on the Core post, contribute to GitHub issue #655 or join the #feature-notifications Slack channel. The post specifically invites feedback on the open design and accessibility questions.
Next step: plugin developers who send admin notices should review the prototype and comment on how its shared layouts and severity rules would fit their messages.