WordPress Feature Notifications Return: 7 Proven Benefits for Site Owners
After three years on the shelf, WordPress Feature Notifications are back. The Repository reported on October 19, 2026 that WordPress’s long-stalled Feature Notifications project has been revived, with a first working version planned for December. The revival was set in motion by Automattic developer advocate Jonathan Bossenger — who led the project when it launched as WP Notify back in 2019 — through a status update and release plan published on the Make WordPress Core blog on October 10. Bossenger set a December 1 release date for version 0.3.0, deliberately lining it up with the final release candidate for WordPress 7.2, which is due December 8. He described 0.3.0 as always having been intended as the project’s first live preview: “a working system that creates, stores, displays, and dismisses notifications.” For site owners buried under dashboard notices, the return of WordPress Feature Notifications could be the most meaningful wp-admin improvement in years.
What Happened: WordPress Feature Notifications Get a December Ship Date
Bossenger’s October 10 status update lays out a concrete plan: version 0.3.0 of the Feature Notifications canonical plugin will ship on December 1, timed to ride the momentum of the WordPress 7.2 release candidate. The goal is a unified notification center for wp-admin that replaces the admin_notices hook — the long-criticized mechanism that lets any plugin inject arbitrary HTML at the top of the dashboard. Bossenger is openly recruiting: he hopes contributors will join “as we work toward getting this merged into core,” and he will post regular updates in the #feature-notifications channel on WordPress Slack.
The return of WordPress Feature Notifications also comes with unusual honesty about the project’s state. An audit in the update explains why the project needs this push: the data models and database schema were well designed and tested, but the system does not work end to end. “The persistence layer is still a set of stubs, the REST API returns empty responses, dismissing a notification doesn’t save anything, and the REST controller tests are skipped.” Bossenger’s hope is that “with a little time, and some AI support, we can get the canonical plugin released to let everyone install it, test it out, and share their feedback.”
The revival is more remarkable given how long WordPress Feature Notifications sat idle. The project last shipped version 0.2.0 in April 2023 — and that same month, Bossenger stepped down as its lead. By June, contributors had paused work on database storage and REST API endpoints to run a community survey, a moment reported by WP Tavern at the time. After that, activity tapered off, and the project effectively froze for three years.
Bossenger told The Repository exactly why it stalled: his sponsored Automattic work with the Training team, building developer learning pathways for learn.wordpress.org, consumed all of his time and left no scope to lead both efforts. Then, at the start of 2025, his Automattic role shifted toward WordPress core AI projects — documentation, testing, talks, workshops, and tutorials. That AI detour turned out to be the making of the revival. WordPress 6.9 laid the AI groundwork with the Abilities API in December 2025; WordPress 7.0 built on it in May 2026 with the AI Client and a new Connectors screen; the MCP Adapter became a canonical plugin; and the AI plugin settled into a steady stream of new features and updates.
“Now that Abilities and the AI Client are available in Core, the MCP Adapter is a canonical plugin, and the AI plugin has a steady stream of new features and updates, I found myself in a position to look for my next ‘big project’.” Then, within a single week, two people asked about Feature Notifications independently. Automattic-sponsored contributor Anne McCarthy raised it in an internal conversation about WordPress 7.2, keen to see it picked back up as momentum built around collaborative workflows and AI — including “how do we handle shared notifications for folks using AI to interact with their site?” That convergence of AI infrastructure and renewed contributor interest is what pulled WordPress Feature Notifications off the shelf.
Who Is Affected: Who Should Care About WordPress Feature Notifications
Anyone who has ever opened wp-admin to a wall of dismissible banners already knows the pain this project targets. Site owners running plugin-heavy websites — especially WooCommerce stores juggling extensions — live with the worst of it: every plugin shouts for attention, and important notices drown in marketing noise. For these users, WordPress Feature Notifications promise a single, sane place where notices live, persist, and can actually be dismissed for good.
Agencies and freelancers managing client sites are affected too. A unified notification center means fewer “is this warning important?” support tickets and cleaner handoffs, which is exactly the kind of quality-of-life win that belongs in a professional website maintenance routine. And plugin developers currently relying on admin_notices should pay attention now: WordPress Feature Notifications are being designed as the eventual replacement, so the sooner you understand the new patterns, the smoother your future migrations will be.
Why WordPress Feature Notifications Matter: 7 Proven Benefits
The admin_notices hook is one of the oldest and most abused extension points in WordPress. Any plugin can drop any HTML at the top of any dashboard screen, with no structure, no priority system, and no memory of what you dismissed. The Feature Notifications project exists to replace that chaos with a real system. Here are seven proven benefits the revived project promises.
1. One Notification Center Replaces Notice Chaos
Instead of a dozen plugins each rendering their own banners, WordPress Feature Notifications centralize everything into a single notification center. Site owners get one predictable place to check, instead of scanning every admin screen for something they might have missed. For busy store owners and publishers, that consolidation alone is worth the wait.
2. Notifications That Are Created, Stored, Displayed — and Dismissed
The 0.3.0 goal is explicit: “a working system that creates, stores, displays, and dismisses notifications.” Storage is the quiet revolution here. Today’s admin notices are amnesiac — dismiss one and it often returns after an update or on another screen. WordPress Feature Notifications are being built with persistence from the start, so a dismissed notification stays dismissed.
3. A Calmer wp-admin for Site Owners
Fewer competing banners means less visual noise and less anxiety for non-technical site owners. When notices follow consistent design patterns and live in one place, owners can actually distinguish “update your payment gateway” from “rate our plugin five stars.” This is the everyday payoff WordPress Feature Notifications are designed to deliver — and agencies should expect the calmer dashboard to reduce the support tickets that start with “there’s a red warning on my site.”
4. Safer Patterns for Developers
Replacing arbitrary HTML injection with a structured notification API is a security and stability win. Constrained, reviewable notification patterns are harder to abuse than raw admin_notices output, and they render consistently across the dashboard. Developers building on WordPress Feature Notifications get guardrails instead of a blank HTML canvas — fewer ways to accidentally break the admin, and fewer surprises during WordPress development sprints.
5. A Stable API Plugin Authors Can Build On
A canonical notification system gives plugin authors a predictable target: one API, one rendering pipeline, one set of behaviors across every site. That stability compounds over time — extensions can rely on notification delivery instead of reimplementing their own banner stacks, and the whole ecosystem gets more consistent. WordPress Feature Notifications give early adopters a real advantage: those who learn the API during the canonical-plugin phase will be ahead when a core merge eventually lands.
6. Ready for the AI Era
The timing of this revival is deliberate. WordPress 6.9 laid the AI groundwork with the Abilities API in December 2025; WordPress 7.0 built on it in May 2026 with the AI Client and a new Connectors screen. Bossenger’s Automattic role shifted at the start of 2025 toward WordPress core AI projects — documentation, testing, talks, workshops, tutorials — and the MCP Adapter is now a canonical plugin with the AI plugin shipping a steady stream of new features. Anne McCarthy raised Feature Notifications specifically in the context of collaborative workflows and AI, asking how WordPress handles “shared notifications for folks using AI to interact with their site.” WordPress Feature Notifications are being revived into a core that finally has the AI primitives to make smart, contextual notifications possible.
7. WooCommerce-Scale Backing
This is not a solo effort. Woo Artistic Director Beau Lebens reached out to Bossenger offering support, noting that “notifications are a pretty significant issue in the Woo world as well.” In the Make post comments, Lebens was blunt: “‘Notifications’ in wp-admin are a notoriously bad part of the overall experience, and the more plugins you use, the worse it gets” — adding that WooCommerce would get some folks involved. When the team behind the web’s biggest e-commerce plugin commits contributors, WordPress Feature Notifications stop being an experiment and start being infrastructure.
What to Do Now: Prepare for WordPress Feature Notifications
The December 1 release of version 0.3.0 is six weeks away. Here is how to get ready:
- Join the #feature-notifications channel on WordPress Slack, where Bossenger will post regular updates as the release approaches.
- When 0.3.0 lands, install the canonical plugin on a staging site and put it through its paces — create, display, and dismiss notifications across your plugin stack.
- Audit how your own themes and plugins use admin_notices today, so you know what will eventually need migrating.
- If you build products for clients, start planning notification copy and priority levels around a persistent, dismissible model.
- Agencies: add notification-center testing to your website maintenance checklists now, so December updates do not surprise you.
- Share feedback with the project — Bossenger explicitly wants testers, and early feedback shapes the API before it hardens.
Getting involved early with WordPress Feature Notifications is the cheapest way to influence a system your sites will eventually depend on.
Frequently Asked Questions
What exactly are WordPress Feature Notifications?
WordPress Feature Notifications are a revived core project building a unified notification center for wp-admin. The goal is to replace the admin_notices hook — which lets plugins inject arbitrary HTML at the top of dashboard screens — with a structured system that creates, stores, displays, and dismisses notifications. The project actually dates back to 2019, when it launched as WP Notify under Bossenger’s leadership, and it is being developed as a canonical plugin first: that means site owners and developers can install it, test it, and give feedback long before any core merge is proposed.
When will WordPress Feature Notifications ship?
Version 0.3.0 of the canonical plugin is scheduled for December 1, 2026, timed with the WordPress 7.2 release candidate (final release due December 8). That date is deliberate: it lets the notification project ride the testing momentum of the last major WordPress release of the year. A merge into WordPress core itself has no date yet; Bossenger hopes contributors will join “as we work toward getting this merged into core.” Until then, the #feature-notifications channel on WordPress Slack is where release updates will land first.
Will WordPress Feature Notifications replace the admin_notices hook?
That is the stated goal. The project aims to give wp-admin a unified notification center instead of the current free-for-all, where every plugin renders its own banners with no shared structure or dismissal memory. Expect a long transition — admin_notices is deeply embedded in thousands of plugins — but the direction is clear, and auditing your own admin_notices usage now beats scrambling later.
How can I get involved with WordPress Feature Notifications?
Join the #feature-notifications channel on WordPress Slack for regular updates from Bossenger, install the 0.3.0 canonical plugin on a staging site when it ships December 1, and share your testing feedback on the Make WordPress Core blog. Contributors of all skill levels are welcome — and because the persistence layer, REST API, and dismissal behavior are all being rebuilt right now, feedback given in the next few weeks will have the most influence on the final API.
Conclusion
The Feature Notifications story is a comeback three years in the making. After shipping 0.2.0 in April 2023, losing its lead that same month, and pausing that June for a community survey, the project went quiet — until Bossenger, fresh from AI groundwork on the Abilities API and AI Client, decided it was time for his next big project. With a December 1 target for version 0.3.0, backing from WooCommerce’s Beau Lebens, and a clear mission to tame the admin_notices chaos, WordPress Feature Notifications have their best shot yet at reaching core. Site owners should watch this space closely, and developers should start preparing now. And if keeping up with releases like this feels like a second job, our WordPress care plan handles updates, testing, and maintenance for you — or start with a free website SEO audit to see where your site stands.
Sources
- The Repository, “Feature Notifications Project Returns After Three-Year Pause, With Plans to Ship a Functional MVP in December,” October 19, 2026: https://www.therepository.email/feature-notifications-project-returns-after-three-year-pause-with-plans-to-ship-a-functional-mvp-in-december (Disclosure: Automattic-owned Pressable sponsors The Repository.)
