--- title: Exploring a design for Feature Notifications | daily.dev description: WordPress Core is prototyping a unified Feature Notifications system to replace scattered admin notices, inbox cards and banners. One shared notification tray... canonical: https://daily.dev/posts/exploring-a-design-for-feature-notifications-gqtaj8ryc twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: Exploring a design for Feature Notifications | daily.dev og:description: WordPress Core is prototyping a unified Feature Notifications system to replace scattered admin notices, inbox cards and banners. One shared notification tray... og:url: https://daily.dev/posts/exploring-a-design-for-feature-notifications-gqtaj8ryc og:image: https://api.daily.dev/og/posts/GQtAj8rYC.png og:image:alt: Exploring a design for Feature Notifications og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # Exploring a design for Feature Notifications **[Make WordPress Core](https://daily.dev/sources/wordpresscore)** · 7 min read · 0 upvotes · 0 comments ## Summary WordPress Core is prototyping a unified Feature Notifications system to replace scattered admin notices, inbox cards and banners. One shared notification tray would appear across every admin screen, the editor and the front end, with plugins sending structured data rather than custom layouts. Notifications use five dimensions, such as type, severity and read state, and four layouts (Standard, Object, Conversation, Group). Critical items stay pinned and turn the bell count red until resolved. The design was tested against every message WooCommerce and WooPayments show today, with Jetpack next, and targets a first step in version 0.3.0 as a feature plugin before any core merge. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### What is the WordPress Feature Notifications project trying to replace? It aims to replace today's scattered admin notices, inbox cards, banners and badges with one shared notification tray available everywhere in WordPress, including every admin screen, the editor and the front of the site. Plugins would send structured data instead of custom layouts, using one of four layouts (Standard, Object, Conversation, Group) and five dimensions like type, severity, intent and read state, so critical issues like failed payments or security updates stand out instead of getting lost among promotions. _Developers building WordPress plugin notifications can follow this redesign's progress on daily.dev before adopting it._ ### How does severity work in the proposed WordPress notifications system? Severity has three levels: critical, warning and info. Critical notifications are pinned at the top and turn the bell's count red until resolved, not just read; warnings wait in a dedicated Alerts tab until dealt with; info covers everything else. There is no 'success' level, since good news already shows through status changes, like a payment dispute marked 'Won'. _Plugin authors weighing notification severity models can track how this spec evolves on daily.dev._ ### Which WordPress plugin was used to stress-test the new notifications design? WooCommerce and WooPayments were the first plugins tested, with every message they currently show run through the new notification catalog to validate the design's rules. Jetpack is the next plugin planned to go through the same stress test, to see how its existing notices fit the new system and where the rules still need to change. _Teams planning WooCommerce notification migrations can keep up with this rollout via daily.dev._ ## Similar posts on daily.dev - [Feature Notifications: status update and plan for 0.3.0](https://daily.dev/posts/feature-notifications-status-update-and-plan-for-0-3-0-tvbqwlt4f) · Make WordPress Core · 1 upvotes · 0 comments - [WP Feature Notifications weekly update: 2026-10-16](https://daily.dev/posts/wp-feature-notifications-weekly-update-2026-10-16-fzljfvpsz) · Make WordPress Core · 2 upvotes · 0 comments - [440: Hey\! Hi\! Right here\! In-App Notifications That Like You](https://daily.dev/posts/440-hey-hi-right-here-in-app-notifications-that-like-you-auwqjna7t) · CodePen · 0 upvotes · 0 comments - [Slack Rebuilds Notification System, Reports 5X Increase in Settings Engagement](https://daily.dev/posts/slack-rebuilds-notification-system-reports-5x-increase-in-settings-engagement-lkcnrib6j) · InfoQ · 0 upvotes · 0 comments --- Tags: [#wordpress](https://daily.dev/tags/wordpress), [#ui-design](https://daily.dev/tags/ui-design), [#accessibility](https://daily.dev/tags/accessibility), [#woocommerce](https://daily.dev/tags/woocommerce) [View this post on daily.dev](https://daily.dev/posts/exploring-a-design-for-feature-notifications-gqtaj8ryc) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"Exploring a design for Feature Notifications","url":"https://daily.dev/posts/exploring-a-design-for-feature-notifications-gqtaj8ryc","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/exploring-a-design-for-feature-notifications-gqtaj8ryc"},"datePublished":"2026-10-29T13:27:54.254Z","dateModified":"2026-10-29T13:28:24.607Z","description":"WordPress Core is prototyping a unified Feature Notifications system to replace scattered admin notices, inbox cards and banners. One shared notification tray...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/68d9eb3c937ad39d1a3118fd169e9654?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/68d9eb3c937ad39d1a3118fd169e9654?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"Make WordPress Core","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Make WordPress Core","logo":"https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/892d1a79e30e4e8a911b5726c6fb1a06","url":"https://daily.dev/sources/wordpresscore"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/exploring-a-design-for-feature-notifications-gqtaj8ryc","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"wordpress,ui-design,accessibility,woocommerce","timeRequired":"PT7M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Make WordPress Core","item":"https://daily.dev/sources/wordpresscore"},{"@type":"ListItem","position":3,"name":"Exploring a design for Feature Notifications"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/exploring-a-design-for-feature-notifications-gqtaj8ryc#faq","mainEntity":[{"@type":"Question","name":"What is the WordPress Feature Notifications project trying to replace?","acceptedAnswer":{"@type":"Answer","text":"It aims to replace today's scattered admin notices, inbox cards, banners and badges with one shared notification tray available everywhere in WordPress, including every admin screen, the editor and the front of the site. Plugins would send structured data instead of custom layouts, using one of four layouts (Standard, Object, Conversation, Group) and five dimensions like type, severity, intent and read state, so critical issues like failed payments or security updates stand out instead of getting lost among promotions. Developers building WordPress plugin notifications can follow this redesign's progress on daily.dev before adopting it."}},{"@type":"Question","name":"How does severity work in the proposed WordPress notifications system?","acceptedAnswer":{"@type":"Answer","text":"Severity has three levels: critical, warning and info. Critical notifications are pinned at the top and turn the bell's count red until resolved, not just read; warnings wait in a dedicated Alerts tab until dealt with; info covers everything else. There is no 'success' level, since good news already shows through status changes, like a payment dispute marked 'Won'. Plugin authors weighing notification severity models can track how this spec evolves on daily.dev."}},{"@type":"Question","name":"Which WordPress plugin was used to stress-test the new notifications design?","acceptedAnswer":{"@type":"Answer","text":"WooCommerce and WooPayments were the first plugins tested, with every message they currently show run through the new notification catalog to validate the design's rules. Jetpack is the next plugin planned to go through the same stress test, to see how its existing notices fit the new system and where the rules still need to change. Teams planning WooCommerce notification migrations can keep up with this rollout via daily.dev."}}]} ```