Title: Feature Project Proposal: WP Notify
Author: Jonathan Bossenger
Published: August 5, 2019

---

 [  ](https://profiles.wordpress.org/psykro/) [Jonathan Bossenger](https://profiles.wordpress.org/psykro/)
8:30 pm _on_ August 5, 2019     
Tags: [feature-notifications ( 54 )](https://make.wordpress.org/core/tag/feature-notifications/)

# Feature Project Proposal: WP Notify

_This detailed proposal was [originally drafted](https://www.notion.so/Feature-Project-Proposal-WP-Notify-d6a2116f37bb4f48a9b6ad9e83bcdfca)
by [@schlessera](https://profiles.wordpress.org/schlessera/), who unfortunately 
[does not have the resources to commit](https://twitter.com/schlessera/status/1155428522892169216)
to executing the project. I am however thankful that he has agreed to assist, in
an advisory role._

# Introduction

WordPress is currently lacking a fundamental mechanism: sending notifications to
users to give them feedback about state changes in the system. Traditionally, pluginPlugin
A plugin is a piece of software containing a group of functions that can be added
to a WordPress website. They can extend functionality or add new features to your
WordPress websites. WordPress plugins are written in the PHP programming language
and integrate seamlessly with WordPress. These can be free in the WordPress.org 
Plugin Directory [https://wordpress.org/plugins/](https://wordpress.org/plugins/)
or can be cost-based plugin from a third-party. developers and CoreCore Core is 
the set of software required to run WordPress. The Core Development Team builds 
WordPress. have been using adminadmin (and super admin) notices for this purpose,
but this solution is lackluster at best and comes with a lot of disadvantages:

 * They are rendered into the normal working area in the dashboard and can even 
   push the actual page content below the fold.
 * The user has no control over how or when they want to deal with them, therefore
   they see them in a mostly negative fashion.
 * They are nothing more than printed HTMLHTML HyperText Markup Language. The semantic
   scripting language primarily used for outputting content in web browsers.. Because
   they lack any kind of structure, it is not possible to manipulate them in an 
   automated fashion.
 * Their persistence is not regulated, which leads to many different implementations
   as well as cruft in the database.

For the above reasons, there’s a general consensus that admin notice are not up 
to the task and need a more robust replacement that can deal with current and future
notification needs.

I hereby want to officially kickstart a **Feature Project** called “**WP Notify**“.

# Project Scope

The initial project will cover an **extensibleExtensible This is the ability to 
add additional functionality to the code. Plugins extend the WordPress core software.
backend implementation** as well as a **single frontend use case**.

## A. Backend implementation

The backend implementation will cover the following elements:

 * An **object model** that is extensible as well as serializable (to JSONJSON JSON,
   or JavaScript Object Notation, is a minimal, readable format for structuring 
   data. It is used primarily to transmit data between a server and web application,
   as an alternative to XML.).
 * A **persistence abstraction** that comes with an initial WPDB implementation.
 * A **background queue** that processes notifications to distribute them across
   channels, for use cases where this is a costly operation, like sending them through
   email.
 * A **simplified procedural APIAPI An API or Application Programming Interface 
   is a software intermediary that allows programs to interact with each other and
   share data in limited, clearly defined ways.** that allows for easy manipulations
   the way plugin developers are accustomed to.
 * **REST APIREST API The REST API is an acronym for the RESTful Application Program
   Interface (API) that uses HTTP requests to GET, PUT, POST and DELETE data. It
   is how the front end of an application (think “phone app” or “website”) can communicate
   with the data store (think “database” or “file system”) [https://developer.wordpress.org/rest-api/](https://developer.wordpress.org/rest-api/)
   controllers** that provide endpoints to manage the notification from the frontend.

## B. Frontend use case

The frontend use case will cover the following elements:

 * An **admin bar integration** that shows notification state and opens a panel 
   to read and dismiss current notifications.
 * An **settings page** that lets the user control which notifications to show/hide
   in the admin bar and which notifications to forward through email.

# Technical Requirements

 * Objects must be serializable to JSON in such a way that it can be sent to the
   client, either as a localized JavaScriptJavaScript JavaScript or JS is an object-
   oriented computer programming language commonly used to create interactive effects
   within web browsers. WordPress makes extensive use of JS for a better user experience.
   While PHP is executed on the server, JS executes within a user’s browser. [https://www.javascript.com](https://www.javascript.com/)
   snippet or as a REST API response.
 * A notification can have one or more recipients, which can be users, roles or 
   a mixture of both.
 * A recipient can configure the channel(s) they want to receive the notifications
   in, on a “per-group” basis.
 * Distribution across channels is not directly coupled to the frontend request,
   but works as a background queue.
 * The admin bar integration needs to build on top of the work done with GutenbergGutenberg
   The Gutenberg project is the new Editor Interface for WordPress. The editor improves
   the process and experience of creating new content, making writing rich content
   much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom
   HTML etc. [https://wordpress.org/gutenberg/](https://wordpress.org/gutenberg/)
   and use a reactive interface powered by the REST API.

# Some Clarifications

## Did this just come out of the blue?

No, the need for a notification subsystem has been identified a long time ago. Current
discussions have been centralized in the [Trac ticket #43484](https://core.trac.wordpress.org/ticket/43484).

## Why does this document talk about a “single frontend use case”? Does the proposal not already cover everything anyway?

No, having a sort of “admin bar hub” to manage your notifications is indeed only
one potential use of the the notifications subsystem. The way it is currently planned,
it could easily have other use cases, like the following examples:

 * Forwarding notifications to a webhook, for integrations into third-party services
   like SlackSlack Slack is a Collaborative Group Chat Platform [https://slack.com/](https://slack.com/).
   The WordPress community has its own Slack Channel at [https://make.wordpress.org/chat/](https://make.wordpress.org/chat/)
 * Providing a webhook to feed notifications from third-party services like GitHubGitHub
   GitHub is a website that offers online implementation of git repositories that
   can easily be shared, copied and modified by other developers. Public repositories
   are free to host, private repositories require a paid subscription. GitHub introduced
   the concept of the ‘pull request’ where code changes done in branches by contributors
   can be reviewed and discussed before being merged by the repository owner. [https://github.com/](https://github.com/)
   into WordPress
 * Showing notifications in a management system like cPanel or ManageWP
 * Integrating notifications contextually into other parts of the admin experience
   in a targeted way
 * Providing a “feed” view/endpoint
 * Letting other servers or tools send notifications to WordPress users/roles over
   the REST API, like a cron job completing a shell maintenance task
 * Attaching server notification systems like `notify-send` or `growl` to your WordPress
   dashboard
 * …

## Why have so many complex moving pieces? Isn’t this called over-engineering?

Complex solutions can easily be adapted to fit simpler needs, while the opposite
is not true. As you can see with the current admin notices, a simplistic solution
that tries to solve a complex problem causes more harm than good, as you cannot 
just get rid of inherent complexity. On the contrary, a solution that is not properly
adapted will cause additional complexity just because of the amount of side-effects
it will generate.

I am certain that building a notifications mechanism for an entire platform like
WordPress that fits the entire spectrum of scenarios from simple blogs to enterprise-
grade custom solutions is inherently complex. An abstraction allows us to put the
main extensibility points in place to stay future-proof and then concentrate on 
the few basic implementations we need for 80% use cases… without having locked out
developers with more exotic needs and while at the same time leaving the solution
open to creative improvements in the future.

## What is this “simplified procedural API” all about?

While building an extensible object model will allow us to extend the implementations
in a safe way in the future, it also comes with more complex usage when interacted
with directly.

That is why we should include a simplified procedural wrapper around the object 
model that mimics the way plugin & theme developers are used to work with WordPress.

As an example, instead of creating an instance of a factory first, to then retrieve
a base notification with a simple message and a single recipient to it, we could
have a simplified wrapper that looks like this:

    ```notranslate
    // Create a new notification for the current user.
    wp_notify( 'MyBackupPlugin', get_current_user_id(), 'Backup completed!' );

    // Mark a specific notification as read.
    get_notification( $notification_id )->mark_as_read();
    ```

These procedural functions come with a default setup that can be controlled via 
actions & filters.

Such a simplified layer allows us to have the best of both worlds: robust and extensible
behind the scenes, and simple and intuitive facing the user.

## So we’re building a complex object model and then wrap it with simplified functions. This is not how WordPress code is usually done…

Indeed. Given that this project is mostly isolated and can be approached in an unencumbered
way, it offers the perfect opportunity to improve the general way WordPress Core
code is done. It should demonstrate that it is possible to get the combined benefits
of both an extensible object model that is robust to work with as well as an intuitive
public-facing API that provides a low barrier of entry.

There is a lot of momentum right now on the WordPress Core developer front. But 
general coding conventions are still based in large parts on what we inherited from
the project’s roots. This project can help define a new set of WordPress-specific
coding patterns that are not tied to the compromised patterns we inherited from 
the PHPPHP The web scripting language in which WordPress is primarily architected.
WordPress requires PHP 7.4 or higher 4 era.

Yes, this is not how WordPress code is usually done … yet! But we can change that!

## Wasn’t there a similar Feature Project already?

You’re referring to the [post by John Blackbourn that he wrote in 2016](https://make.wordpress.org/core/2016/10/03/feature-project-proposal-notifications-api/).
That project proposal never really got off the ground, and I got confirmation from
John that it is abandoned and should hopefully be replaced, as the need for it is
still there.

# Call for Volunteers

If the above sounds like something you would like to contribute to, please either
write a brief comment below this post, with the area you are interested in and the
skills you can offer.

Alternatively, you can join the discussions on [Slack in the #feature-notifications channel](https://wordpress.slack.com/messages/C2K1C71FE)
or on [Trac ticket #43484](https://core.trac.wordpress.org/ticket/43484).

This project covers a lot of different areas, like advanced backend code, scalable
database gymnastics, reactive JavaScript code and dynamic UIUI User interface/UXUX
User experience design.

All help is welcome, but please be aware that different topics will be in focus 
at different stages of the project.

## Next Steps

There have already been a number of interested parties on the TracTrac An open source
project by Edgewall Software that serves as a bug tracker and project management
tool for WordPress. ticketticket Created for both bug reports and feature development
on the bug tracker. or in the [#feature-notifications](https://make.wordpress.org/core/tag/feature-notifications/)
channel and I look forward to your feedback, comments and suggestions. By the 19th
of August I plan to have an initial project kick off meeting scheduled, so that 
we can set up a plan of how best to move forward.

### Share this:

 * [  Threads ](https://make.wordpress.org/core/2019/08/05/feature-project-proposal-wp-notify/?share=threads)
 * [  Mastodon ](https://make.wordpress.org/core/2019/08/05/feature-project-proposal-wp-notify/?share=mastodon)
 * [  Bluesky ](https://make.wordpress.org/core/2019/08/05/feature-project-proposal-wp-notify/?share=bluesky)
 * [  X ](https://make.wordpress.org/core/2019/08/05/feature-project-proposal-wp-notify/?share=x)
 * [  Facebook ](https://make.wordpress.org/core/2019/08/05/feature-project-proposal-wp-notify/?share=facebook)
 * [  LinkedIn ](https://make.wordpress.org/core/2019/08/05/feature-project-proposal-wp-notify/?share=linkedin)

 1.   ![](https://secure.gravatar.com/avatar/6f505c6be9a951929a99becb6b413dcfa583a5ca3dd0f7320766fee1481f0f82?
      s=32&d=mm&r=g)
 2.    [Jb Audras](https://profiles.wordpress.org/audrasjb/)  8:51 pm _on_ August 5,
      2019
 3.   Great news!
       Thanks [@psykro](https://profiles.wordpress.org/psykro/) for taking
      ownership on [@schlessera](https://profiles.wordpress.org/schlessera/)’s project!
      I just joined [#feature-notifications](https://make.wordpress.org/core/tag/feature-notifications/)
      channel. Happy to help where I can!
 4.   Cheers,
       Jb
 5.    * ![](https://secure.gravatar.com/avatar/a8a3c44a68937ee1996ba1bd3325126c4fd962f20b60acc16988dea6b527d14c?
         s=32&d=mm&r=g)
       *  [Jonathan Bossenger](https://profiles.wordpress.org/psykro/)  6:21 am _on_
         August 7, 2019
       * Thanks [@audrasjb](https://profiles.wordpress.org/audrasjb/)
 6.   ![](https://secure.gravatar.com/avatar/3c47f25cb051a0ae3c8929aeb4af45f1c2ccbdb62b42115569424b3924bd989d?
      s=32&d=mm&r=g)
 7.    [Rachel Cherry](https://profiles.wordpress.org/bamadesigner/)  9:05 pm _on_ 
      August 5, 2019
 8.   Thanks Johnathan! The notifications in the adminadmin (and super admin) dashboard
      need some serious consideration so it’s awesome to hear things are moving forward.
 9.   For me, outside of the obvious design issues, the majority of the problem is 
      that a lot of developers and pluginPlugin A plugin is a piece of software containing
      a group of functions that can be added to a WordPress website. They can extend
      functionality or add new features to your WordPress websites. WordPress plugins
      are written in the PHP programming language and integrate seamlessly with WordPress.
      These can be free in the WordPress.org Plugin Directory [https://wordpress.org/plugins/](https://wordpress.org/plugins/)
      or can be cost-based plugin from a third-party./themes shops use the notices 
      as a way to nag or advertise.
 10.  I am often inundated with plugin notices that aren’t vital to my use and aren’t
      showing a change of state. Most of the time they want me to donate or give them
      a review or check out their other products.
 11.  It’s tolerable when they only display these notices on their settings/tools page,
      but then you get the obnoxious plugins that display them on every page of the
      admin. And then that’s the last time I use that plugin or any plugins from that
      developer or shop.
 12.  But most are not so lucky. I can build my own plugins, most cannot. They have
      to grin and bear the madness.
 13.  With all that said, I read this proposal and how you want to be able to export
      these notifications to other services and my instant reaction was “great. now
      we’re gonna give developers a way to spam us OUTSIDE WordPress too”.
 14.  I see you and Alain have given lots of thought to the technical and design issues
      with notifications, but I feel that’s only half the battle. You can fix all of
      that but people will still take advantage.
 15.  Have you given any thought to the (lack of) governance issues with notifications?
 16.  I would love to see this project include work on defining boundaries and establishing
      policies for what the notification system can be used for.
 17.  Thanks for all of your work!
 18.   * ![](https://secure.gravatar.com/avatar/b089b139f7aa516c9e2793572939d7f0de5a877566b1bb08123322e877ea5eca?
         s=32&d=mm&r=g)
       *  [donmhico](https://profiles.wordpress.org/donmhico/)  12:38 am _on_ August
         6, 2019
       * +1 to the concern of pluginPlugin A plugin is a piece of software containing
         a group of functions that can be added to a WordPress website. They can extend
         functionality or add new features to your WordPress websites. WordPress plugins
         are written in the PHP programming language and integrate seamlessly with 
         WordPress. These can be free in the WordPress.org Plugin Directory [https://wordpress.org/plugins/](https://wordpress.org/plugins/)
         or can be cost-based plugin from a third-party. / theme developers may abuse
         this upcoming WP Notify. But unfortunately that’s something we have little
         control to. At most, what we can do is be more strict in screening the plugins/
         themes submitted in WP.org’s repo and make sure that they are not abusing 
         the notification APIAPI An API or Application Programming Interface is a software
         intermediary that allows programs to interact with each other and share data
         in limited, clearly defined ways..
          - ![](https://secure.gravatar.com/avatar/2705ec72762002e78c7aded24c0f5342a977a679a86abd8b1b3b2e09d5f6d715?
            s=32&d=mm&r=g)
          -  [Michael Nelson](https://profiles.wordpress.org/mnelson4/)  1:01 am _on_
            August 6, 2019
          - Ya I think someone from the pluginPlugin A plugin is a piece of software
            containing a group of functions that can be added to a WordPress website.
            They can extend functionality or add new features to your WordPress websites.
            WordPress plugins are written in the PHP programming language and integrate
            seamlessly with WordPress. These can be free in the WordPress.org Plugin
            Directory [https://wordpress.org/plugins/](https://wordpress.org/plugins/)
            or can be cost-based plugin from a third-party. review team will need to
            be involved in deciding what the new rules will be, seeing how they’re 
            the ones who will ultimately be enforcing them.
          - ![](https://secure.gravatar.com/avatar/4dca3cf784f40c6c15f9a8094460a0ed8033c68e0e929d78a5a45f5ba3135958?
            s=32&d=mm&r=g)
          -  [mikehealy](https://profiles.wordpress.org/mikehealy/)  1:57 am _on_ August
            6, 2019
          - Perhaps it could be controlled like notification permissions on your phone?
            
            The site owner could explicitly enable certain types of notifications to
            be sent to them outside of WordPress, and the option would be off by default.
             * ![](https://secure.gravatar.com/avatar/2705ec72762002e78c7aded24c0f5342a977a679a86abd8b1b3b2e09d5f6d715?
               s=32&d=mm&r=g)
             *  [Michael Nelson](https://profiles.wordpress.org/mnelson4/)  4:22 am
               _on_ August 6, 2019
             * Ya giving the site adminadmin (and super admin)/owner that level of 
               control would probably be good.
       * ![](https://secure.gravatar.com/avatar/19064ed4f839086c8fd557e5d00c62cdb52cdba868e6bf100a64d8a4f0974aed?
         s=32&d=mm&r=g)
       *  [Mike Schinkel [WPLib Box project lead]](https://profiles.wordpress.org/mikeschinkel/)
         1:08 am _on_ August 6, 2019
       * > For me, outside of the obvious design issues, the majority of the problem
         > is that a lot of developers and pluginPlugin A plugin is a piece of software
         > containing a group of functions that can be added to a WordPress website.
         > They can extend functionality or add new features to your WordPress websites.
         > WordPress plugins are written in the PHP programming language and integrate
         > seamlessly with WordPress. These can be free in the WordPress.org Plugin
         > Directory [https://wordpress.org/plugins/](https://wordpress.org/plugins/)
         > or can be cost-based plugin from a third-party./themes shops use the notices
         > as a way to nag or advertise.
       * This. 1000% this.
       * ![](https://secure.gravatar.com/avatar/27180c82524020e7339e2b30818b6d8ab004c54f730f12b1434b1e365be0e175?
         s=32&d=mm&r=g)
       *  [Ipstenu (Mika Epstein)](https://profiles.wordpress.org/ipstenu/)  10:36 
         pm _on_ August 6, 2019
       * The reality there is plugins and themes will abuse the lack of system as much
         as the system.
       * Already, many plugins have built their own systems, which are far worse and
         not controllable. But if we have a single hub system for notifications, we
         can then via-coreCore Core is the set of software required to run WordPress.
         The Core Development Team builds WordPress. (and … plugins …) give site owners
         some control back. Say you put in a pluginPlugin A plugin is a piece of software
         containing a group of functions that can be added to a WordPress website. 
         They can extend functionality or add new features to your WordPress websites.
         WordPress plugins are written in the PHP programming language and integrate
         seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory
         [https://wordpress.org/plugins/](https://wordpress.org/plugins/) or can be
         cost-based plugin from a third-party. to suppress all notifications. Then 
         no matter how much a plugin or theme abuses the system, it’s all silence for
         you.
       * Won’t stop people from going outside the system, but it will stop the rookies
         from writing some gorram awful code to invent a wheel, and it’ll give a control-
         plugin a chance to wrangle in notifications, similar to how your phone does,
         perhaps.
 19.  ![](https://secure.gravatar.com/avatar/19064ed4f839086c8fd557e5d00c62cdb52cdba868e6bf100a64d8a4f0974aed?
      s=32&d=mm&r=g)
 20.   [Mike Schinkel [WPLib Box project lead]](https://profiles.wordpress.org/mikeschinkel/)
      10:21 pm _on_ August 5, 2019
 21.  Great to see forward movement on this.
 22.  Is there a GitGit Git is a free and open source distributed version control system
      designed to handle everything from small to very large projects with speed and
      efficiency. Git is easy to learn and has a tiny footprint with lightning fast
      performance. Most modern plugin and theme development is being done with this
      version control system.
       [https://git-scm.com/](https://git-scm.com/) repo where
      work is being done? If it was in the tracTrac An open source project by Edgewall
      Software that serves as a bug tracker and project management tool for WordPress.
      ticketticket Created for both bug reports and feature development on the bug 
      tracker. or this point, I obviously missed it.
 23.  ![](https://secure.gravatar.com/avatar/2705ec72762002e78c7aded24c0f5342a977a679a86abd8b1b3b2e09d5f6d715?
      s=32&d=mm&r=g)
 24.   [Michael Nelson](https://profiles.wordpress.org/mnelson4/)  11:49 pm _on_ August
      5, 2019
 25.  +100 this!
       I’m interested in contributing. I’ve contributed to the REST APIREST
      API The REST API is an acronym for the RESTful Application Program Interface (
      API) that uses HTTP requests to GET, PUT, POST and DELETE data. It is how the
      front end of an application (think “phone app” or “website”) can communicate 
      with the data store (think “database” or “file system”) [https://developer.wordpress.org/rest-api/](https://developer.wordpress.org/rest-api/),
      Multisitemultisite Used to describe a WordPress installation with a network of
      multiple blogs, grouped by sites. This installation type has shared users tables,
      and creates separate database tables for each blog (wp_posts becomes wp_0_posts).
      See also **network**, **blog**, **site**, and am a plug-in developer. I love 
      the technical plan so far. It sounds like it has the potential to bring some 
      sanity to the state of notifications in WordPress for both site owners and developers.
      It would be great to develop a plan that allows for this to be introduced to 
      coreCore Core is the set of software required to run WordPress. The Core Development
      Team builds WordPress. in incrementally (otherwise I’m afraid it might suffer
      the fate of other great initiatives like the fields APIAPI An API or Application
      Programming Interface is a software intermediary that allows programs to interact
      with each other and share data in limited, clearly defined ways., which were 
      great but hard to adopt all-at-once). I’m a bit afraid the politics of notifications(
      like Rachel brought up, where site creators detest spammy notifications, but 
      pluginPlugin A plugin is a piece of software containing a group of functions 
      that can be added to a WordPress website. They can extend functionality or add
      new features to your WordPress websites. WordPress plugins are written in the
      PHP programming language and integrate seamlessly with WordPress. These can be
      free in the WordPress.org Plugin Directory [https://wordpress.org/plugins/](https://wordpress.org/plugins/)
      or can be cost-based plugin from a third-party. owners see a huge increase in
      support from them) is another pitfall to navigate. But I really hope this progresses
      and hope to contribute to it.
 26.   * ![](https://secure.gravatar.com/avatar/f684d395d41f087441413624b6af3309fe38bad2206cf41556cb03f0be1f67df?
         s=32&d=mm&r=g)
       *  [Kyle Maurer](https://profiles.wordpress.org/brashrebel/)  12:22 am _on_ 
         August 7, 2019
       * You’re awesome dude!
 27.  ![](https://secure.gravatar.com/avatar/b089b139f7aa516c9e2793572939d7f0de5a877566b1bb08123322e877ea5eca?
      s=32&d=mm&r=g)
 28.   [donmhico](https://profiles.wordpress.org/donmhico/)  12:48 am _on_ August 6,
      2019
 29.  I love the idea of a better mechanism for notifications. But like Rachel mentioned
      above we need to somehow find a way to minimize the “noise” from plugins / themes.
 30.  > An settings page that lets the user control which notifications to show/hide
      > in the adminadmin (and super admin) bar and which notifications to forward 
      > through email.
 31.  This is vital. The current `admin_notice` hook doesn’t have this mechanism which
      results to a “noisy” admin dashboard.
 32.  ![](https://secure.gravatar.com/avatar/e1ebdc8c85b7d6484f5ad4984c6dc2a20f329e5bcb41b7da78ad70612072b80f?
      s=32&d=mm&r=g)
 33.   Anonymous User  7:01 am _on_ August 6, 2019
 34.  I feel nothing short of _thrilled_ about this proposal, the abstract reads _great_!
 35.  Rachel brought up a key question I’d like to second, of course: **how is WordPress
      going to own the screen estate it makes accessible to third-party developers 
      and protect a powerful feature like notifications from being mis-/abused?**
 36.  To re-state some of the potential premises here:
 37.   * It is so powerful of a feature because it directly deals with and has the 
         potential to either attract, or consume, the most battled-for resource in 
         software design: human attention.
       * It is also a feature facing a major challenge: to transport any type of user-
         directed message, from system-critical to marketing, in a way that helps users
         prioritise those messages while the feature itself must avoid being too opinionated
         about their content.
       * Finally (and this may sound more like a premature assumption than a premise),
         it is a feature that, at some point in the future, may have to enable communication
         both ways – providing not only a gateway to user attention, but also a way
         for users to send feedback to a notifying agent (pluginPlugin A plugin is 
         a piece of software containing a group of functions that can be added to a
         WordPress website. They can extend functionality or add new features to your
         WordPress websites. WordPress plugins are written in the PHP programming language
         and integrate seamlessly with WordPress. These can be free in the WordPress.
         org Plugin Directory [https://wordpress.org/plugins/](https://wordpress.org/plugins/)
         or can be cost-based plugin from a third-party./theme provider, or WordPress
         coreCore Core is the set of software required to run WordPress. The Core Development
         Team builds WordPress.), e.g. by ‘flagging’ any inappropriate use of the feature.
 38.  Based on collective experience, I agree there have to be expectations and boundaries
      put in place. WordPress clearly not only has a technical mandate here, but one
      for design, and an educational one as well, all the while its mission must be‘
      people-first’ which means to empower both, users _and_ developers. Any bias towards
      either one of these groups could pose major obstacles in the reception of the
      work done.
 39.  Based on the outlook Jonathan has provided on software architecture, I believe
      these two aspects – code and the implications of how it should and should not
      be used – can progress asynchronously for a while, informing each other but not
      holding each other back, at least not before this project gets to a technical
      MVPMinimum Viable Product "A minimum viable product (MVP) is a product with just
      enough features to satisfy early customers, and to provide feedback for future
      product development." - [WikiPedia](https://en.wikipedia.org/wiki/Minimum_viable_product)
      in the Feature PluginFeature Plugin A plugin that was created with the intention
      of eventually being proposed for inclusion in WordPress Core. See [Features as Plugins](https://make.wordpress.org/core/handbook/about/release-cycle/features-as-plugins/).
 40.  I’d love to see discussion happen in an organised, time-boxed, and moderated 
      form across multiple channels (like here on Make, but also through other blogs,
      newsletters, talks, Contributor Days etc). Ideally, decisions regarding limitations
      and expected behaviour will be based on data from as many groups of stakeholders
      as possible. Perhaps that is something the WP Governance project could help to
      facilitate?
 41.  For the time being, I’m excited to see this initiative being kicked off for real
      and keen to follow its progress.
 42.  ![](https://secure.gravatar.com/avatar/2bbf5d68008a40dd09df7de61b7f06de29163885ca93e8b9706574aadc07ff12?
      s=32&d=mm&r=g)
 43.   [dingo-d](https://profiles.wordpress.org/dingo_d/)  7:26 am _on_ August 6, 2019
 44.  Rachel brought valid points, but ultimately I don’t think it has much to do with
      the _development_ of the notifications APIAPI An API or Application Programming
      Interface is a software intermediary that allows programs to interact with each
      other and share data in limited, clearly defined ways. (or WP Notify), but how
      pluginPlugin A plugin is a piece of software containing a group of functions 
      that can be added to a WordPress website. They can extend functionality or add
      new features to your WordPress websites. WordPress plugins are written in the
      PHP programming language and integrate seamlessly with WordPress. These can be
      free in the WordPress.org Plugin Directory [https://wordpress.org/plugins/](https://wordpress.org/plugins/)
      or can be cost-based plugin from a third-party. and theme review teams are going
      to handle the use cases.
 45.  In this regard the community discussion is vital so that we can prevent abuse,
      but I don’t think that we should limit the potential power of the new project,
      just out of fear that somebody will misuse it (and there are people who will 
      definitely do that no matter what).
 46.   * ![](https://secure.gravatar.com/avatar/e1ebdc8c85b7d6484f5ad4984c6dc2a20f329e5bcb41b7da78ad70612072b80f?
         s=32&d=mm&r=g)
       *  Anonymous User  7:38 am _on_ August 6, 2019
       * So, people will definitely misuse a feature as powerful as this one and we
         should just stand by and watch it happen and not try to mitigate misuse through
         dedicated user research, applied design thinking, and ownership of the powers
         we set lose… is that what you’re saying?
          - ![](https://secure.gravatar.com/avatar/2bbf5d68008a40dd09df7de61b7f06de29163885ca93e8b9706574aadc07ff12?
            s=32&d=mm&r=g)
          -  [dingo-d](https://profiles.wordpress.org/dingo_d/)  7:55 am _on_ August
            6, 2019
          - No, I’m saying that we need a community discussion on how to mitigate the
            potential misuse, but that it **shouldn’t hinder the development** side
            of the new feature.
             People will always find ways to misuse a certain thing,
            no matter how hard we try to mitigate it. That’s just the reality of things.
          - Often times, at WordPress, the features are discussed until no development
            is being done and things just die away (just take a peek into the autoloading
            and the usage of composer in tracTrac An open source project by Edgewall
            Software that serves as a bug tracker and project management tool for WordPress.).
            Discussion should happen in parallel, but shouldn’t hinder the development.
            That’s my opinion 😉
             * ![](https://secure.gravatar.com/avatar/e1ebdc8c85b7d6484f5ad4984c6dc2a20f329e5bcb41b7da78ad70612072b80f?
               s=32&d=mm&r=g)
             *  Anonymous User  8:02 am _on_ August 6, 2019
             * 👍
 47.  ![](https://secure.gravatar.com/avatar/1e617206bef965b930d9d23eabfeecf8bc37c6bf500a26cc3ef55ec380131eb2?
      s=32&d=mm&r=g)
 48.   [Archie22is](https://profiles.wordpress.org/archie22is/)  8:24 am _on_ August
      6, 2019
 49.  This one gets +1000 from me. Definitely a great proposal. The usage cases that
      come to my mind are definitely unlimited.
 50.  ![](https://secure.gravatar.com/avatar/6dde7f578e5530884238e7173f768ae3a890b6d66eb99262a82f2c494a1b67d4?
      s=32&d=mm&r=g)
 51.   [Alain Schlesser](https://profiles.wordpress.org/schlessera/)  9:31 am _on_ 
      August 6, 2019
 52.  A quick note about governance and abuse:
 53.  The original intent of the proposal was to let the plugins/themes decide WHAT
      to show, and let the users decide IF and HOW/WHERE to show it.
 54.  This would mean that there is some form of categorisation/prioritisation that
      plugins/themes can choose from. Users can then flexibly configure what they want
      to be bothered with, and through which channel(s).
 55.  The governance part would then basically be that the pluginPlugin A plugin is
      a piece of software containing a group of functions that can be added to a WordPress
      website. They can extend functionality or add new features to your WordPress 
      websites. WordPress plugins are written in the PHP programming language and integrate
      seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory
      [https://wordpress.org/plugins/](https://wordpress.org/plugins/) or can be cost-
      based plugin from a third-party./theme review teams ensure that plugins/themes
      don’t use deceiving categorisation/prioritisation. But even if they do, users
      would still be able to just switch off the offenders.
 56.  This is only a preliminary plan, of course, and all discussion is fruitful and
      welcome. But I think a general approach of splitting up the responsibilities 
      between providers and consumers (instead of letting the providers do what they
      want and leaving the consumers powerless as is now) is a solid way of improving
      on the situation.
 57.   * ![](https://secure.gravatar.com/avatar/e1ebdc8c85b7d6484f5ad4984c6dc2a20f329e5bcb41b7da78ad70612072b80f?
         s=32&d=mm&r=g)
       *  Anonymous User  9:40 am _on_ August 6, 2019
       * 👍
       * ![](https://secure.gravatar.com/avatar/4dca3cf784f40c6c15f9a8094460a0ed8033c68e0e929d78a5a45f5ba3135958?
         s=32&d=mm&r=g)
       *  [mikehealy](https://profiles.wordpress.org/mikehealy/)  9:51 pm _on_ August
         6, 2019
       * Sounds good.
          Would having categories similar to error logging (info, notice,
         error, critical etc) work? Users could then have the choice of how they receive
         each class of notification, and plugins could be reprimanded or punished for
         abusing the categories (for example putting ads in the critical group).
       * ![](https://secure.gravatar.com/avatar/27180c82524020e7339e2b30818b6d8ab004c54f730f12b1434b1e365be0e175?
         s=32&d=mm&r=g)
       *  [Ipstenu (Mika Epstein)](https://profiles.wordpress.org/ipstenu/)  10:39 
         pm _on_ August 6, 2019
       * Speaking for the pluginPlugin A plugin is a piece of software containing a
         group of functions that can be added to a WordPress website. They can extend
         functionality or add new features to your WordPress websites. WordPress plugins
         are written in the PHP programming language and integrate seamlessly with 
         WordPress. These can be free in the WordPress.org Plugin Directory [https://wordpress.org/plugins/](https://wordpress.org/plugins/)
         or can be cost-based plugin from a third-party. team, it’d be easier to grep
         someone for using that system and smack ’em for abuse than it is today with
         a bajillion home-grown systems, half of which don’t work.
       * PLUS someone could easily make a plugin that limits the abuse by other plugins
         🙂 Notification managers would have a standard!
 58.  ![](https://secure.gravatar.com/avatar/27180c82524020e7339e2b30818b6d8ab004c54f730f12b1434b1e365be0e175?
      s=32&d=mm&r=g)
 59.   [Ipstenu (Mika Epstein)](https://profiles.wordpress.org/ipstenu/)  10:40 pm 
      _on_ August 6, 2019
 60.  +make.wordpress.org/plugins
 61.  ![](https://secure.gravatar.com/avatar/9d98caff333af226f3562c13222afa97589830eddbce220eee3ece3f16890a80?
      s=32&d=mm&r=g)
 62.   [Andrei Igna](https://profiles.wordpress.org/andreiigna/)  7:37 am _on_ August
      7, 2019
 63.  This is great! As a pluginPlugin A plugin is a piece of software containing a
      group of functions that can be added to a WordPress website. They can extend 
      functionality or add new features to your WordPress websites. WordPress plugins
      are written in the PHP programming language and integrate seamlessly with WordPress.
      These can be free in the WordPress.org Plugin Directory [https://wordpress.org/plugins/](https://wordpress.org/plugins/)
      or can be cost-based plugin from a third-party./theme developer I noticed there’s
      no easy way to handle this part in WordPress, and was thinking to propose something
      similar too. I’ve put some time time and thoughts into this, and it’s great to
      see most of the things are found in this feature plan.
 64.  There’s one idea which I wanna mention here, and I think it will be helpful for
      end users and will help with preventing abuse. The idea is **Notification groups**.
 65.  
      ## A. Backend implementation
      
 66.   * The object model for notifications should have a required **group** field,
         and all notifications sent must be grouped based on the user’s interest or
         notification source (something to be discussed more).
 67.      ```notranslate
          // Let the admins know there's an action needed for a plugin
          wp_notify( $group = 'plugin/my-plugin', $usersOrRoleOrCapability = 'admin', $message = 'My Plugin requires attention or it will stop working soon.' );
      
          // Let the editors know a plugin finished a scheduled job
          wp_notify( $group = 'plugin/another-plugin', $usersOrRoleOrCapability = 'editor', $message = 'Another plugin finished that job you set up' );
      
          // Notify site owners about theme
          wp_notify( $group = 'theme', $usersOrRoleOrCapability = 'manage_options', $message = 'Theme X needs this setting to show this section' );
          ```
      
 68.  
      ## B. Frontend use case
      
 69.  Having notification groups will enable a few extra options for end users on frontend:
 70.   * On settings page allow muting by notification groups. Example based on the
         3 notifications sent above: show the groups “Plugin”, “Plugin – My Plugin”,“
         Plugin – Another plugin”, “Theme” and allow to mute/unmute each one.
       * Each notification should display the groups & subgroups, and allow muting 
         for each. Example for first notification: “Mute all plugin notifications” 
         and “Mute My Plugin notifications”
 71.  I mention this mainly to start the discussion, and hope it will lead to a good
      implementation in WordPress. Will also follow the thread and contribute when 
      this starts to be built
 72.  ![](https://secure.gravatar.com/avatar/1718b7c2f2afc31b4e94805b6f1f6ae2b802cc4c696f99b11fde2186006c82c9?
      s=32&d=mm&r=g)
 73.   [Pascal Birchler](https://profiles.wordpress.org/swissspidy/)  7:37 am _on_ 
      August 7, 2019
 74.  Are there any examples of what kind of notifications this would be useful for?
 75.  I am a bit worried that this has a strong focus on backend implementation, and
      the frontend part gets just two sentences, suggesting a notification panel in
      the adminadmin (and super admin) toolbar. I feel like more thought should be 
      put into the UXUX User experience of this.
 76.  There have also been learnings about notifications in GutenbergGutenberg The 
      Gutenberg project is the new Editor Interface for WordPress. The editor improves
      the process and experience of creating new content, making writing rich content
      much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom
      HTML etc.
       [https://wordpress.org/gutenberg/](https://wordpress.org/gutenberg/),
      BuddyPress and other projects. It would be good to chat and collaborate with 
      these teams.
 77.  ![](https://secure.gravatar.com/avatar/cd18da60d54f0a7374dc62b122ff5050f33fad8c43ce013594f7703a37b9d906?
      s=32&d=mm&r=g)
 78.   [Andrea Fercia](https://profiles.wordpress.org/afercia/)  9:21 am _on_ August
      7, 2019
 79.  > I feel like more thought should be put into the UXUX User experience of this.
 80.  I’d second Pascal’s opinion. For example, I’m not sure the adminadmin (and super
      admin) bar is the best place for notifications:
 81.   * on the front end, the admin bar can be dismissed via user’s preferences
       * on small screens, the admin bar is already very crowded (see all the recent
         problems to find a spot for the “recovery mode” notice
       * in terms of accessibilityAccessibility Accessibility (commonly shortened to
         a11y) refers to the design of products, devices, services, or environments
         for people with disabilities. The concept of accessible design ensures both“
         direct access” (i.e. unassisted) and “indirect access” meaning compatibility
         with a person’s assistive technology (for example, computer screen readers).(
         https://en.wikipedia.org/wiki/Accessibility), the DOM order is important and
         the admin bar has a lot of content before it
 82.  Side note: I’d like to give credit to Tim Hengeveld as co-author of this proposal
      as he created the [Trac ticket](https://core.trac.wordpress.org/ticket/43484)
      that started this project (which in turn, elaborates on the original proposal
      from John Blackbourn)
 83.   * ![](https://secure.gravatar.com/avatar/d90c229271bfd77e2082d964e37cef60b935fa3ab6682883a8407a6c086e6e4c?
         s=32&d=mm&r=g)
       *  [Erin 'Folletto' Casali](https://profiles.wordpress.org/folletto/)  12:04
         pm _on_ September 2, 2019
       * Thanks for these notes. I’d add that I suggested in the linked ticketticket
         Created for both bug reports and feature development on the bug tracker. to
         look up the design that has been worked on and agreed already by many regarding
         an adminadmin (and super admin) bar redesign, [here](https://core.trac.wordpress.org/ticket/32678).
         That should solve at least the “small screens” issue, and possibly the bar
         having “lot of content” issue (but that’s something we can see once we get
         to prototype it).
 84.  ![](https://secure.gravatar.com/avatar/a8a3c44a68937ee1996ba1bd3325126c4fd962f20b60acc16988dea6b527d14c?
      s=32&d=mm&r=g)
 85.   [Jonathan Bossenger](https://profiles.wordpress.org/psykro/)  9:45 am _on_ August
      7, 2019
 86.  Personally, I have no plans to focus only on the technical implementation without
      already having a solid plan on what the user experience should be.
 87.  This is not a project to be taken lightly, nor one that I expect to be ready 
      to ship any time soon. I have already been advised that it would be a good idea
      to have a co-lead on this, and from my perspective having someone who has a strong
      focus on the user experience, and who is dedicated to seeing this through to 
      the end, would be the perfect co-lead. Volunteers for that position welcome!
 88.  [@afercia](https://profiles.wordpress.org/afercia/) thank you also for highlighting
      [@hedgefield](https://profiles.wordpress.org/hedgefield/)‘s initial work on this.
      I plan to confer with and take advice from the folks who have laid the groundwork
      before me, as well as other key members of the WordPress project, as we move 
      forward.
 89.  ![](https://secure.gravatar.com/avatar/3c47f25cb051a0ae3c8929aeb4af45f1c2ccbdb62b42115569424b3924bd989d?
      s=32&d=mm&r=g)
 90.   [Rachel Cherry](https://profiles.wordpress.org/bamadesigner/)  12:57 pm _on_
      August 7, 2019
 91.  Thanks everyone for the conversation and follow up!
 92.  I don’t think anyone expects/believes the tech itself is going to eradicate notification
      spam but that doesn’t mean that we, as a community, cannot make rules/boundaries/
      expectations so that when devs ultimately break them, we have the power to remove
      them from the repo.
 93.  And, yes, devs will do their own thing outside the new notification system but
      that’s also where governance can make a difference.
 94.  We can’t always control how people use WordPress software, but we can control
      who gets hosted in the repo. We can control guidelines, boundaries, and expected
      use for our software. We can tell developers they have to use our notification
      system, and play by the rules, if they want to be hosted in the repo.
 95.  As Caspar pointed out, new, fancy tech is great and all (and it does sound awesome)
      but we have to be responsible for the power and experience it creates. The current
      notification system, even with its minimum functionality, is already being exploited
      and you’re basically talking about giving the system an unlimited playground.
      We have to discuss and research its implications. It has to be a part of the 
      tech design process.
 96.  No one wants to hinder tech development but the whole point of the notification
      system is to help the user be more informed about their site. We have to be thinking
      about the user experience. It is one and the same with the code.
 97.  For example, here’s some user research for you.
 98.  I, as a user, don’t want the solution to be “well just remove all notifications”
      because some of them are actually important. Yes, being able to group them according
      to type will help because I can disable certain types. But that’s not enough.
      If there’s no attempt at governance of what constitutes a valid notification,
      I will just turn them all off rather than deal with the noise. And then what’s
      the point of the system?
 99.  ![](https://secure.gravatar.com/avatar/a8a3c44a68937ee1996ba1bd3325126c4fd962f20b60acc16988dea6b527d14c?
      s=32&d=mm&r=g)
 100.  [Jonathan Bossenger](https://profiles.wordpress.org/psykro/)  1:52 pm _on_ August
      7, 2019
 101. Thanks Rachel, I do appreciate your input.
 102. I do plan on following an approach where we spend a goodly amount of time designing
      the new system before we even write a single line of code. This is a problem 
      that needs an informed approach, not just a quick fix.
 103. As such, I would appreciate any input and feedback you have on the project, as
      it takes shape. Right now I’m focusing on welcoming interested parties, and then
      planning next steps.
 104.  * ![](https://secure.gravatar.com/avatar/3c47f25cb051a0ae3c8929aeb4af45f1c2ccbdb62b42115569424b3924bd989d?
         s=32&d=mm&r=g)
       *  [Rachel Cherry](https://profiles.wordpress.org/bamadesigner/)  1:57 pm _on_
         August 7, 2019
       * Thanks Jonathan! I’m excited about the project and grateful for you and others
         involved. I know these things take a lot of dedication and time. I’ll be sure
         to follow along. Let me know if/how I can help.
          - ![](https://secure.gravatar.com/avatar/a8a3c44a68937ee1996ba1bd3325126c4fd962f20b60acc16988dea6b527d14c?
            s=32&d=mm&r=g)
          -  [Jonathan Bossenger](https://profiles.wordpress.org/psykro/)  2:05 pm 
            _on_ August 7, 2019
          - Thanks, I will.
 105. ![](https://secure.gravatar.com/avatar/b7a012092ab8958977998298ca9567475f87efbaf0ad57256943390ca05812c3?
      s=32&d=mm&r=g)
 106.  [Aurélien Denis](https://profiles.wordpress.org/maigret/)  2:16 pm _on_ August
      7, 2019
 107. I’ve been waiting this project for a while, that’s a nice!!
 108. ![](https://secure.gravatar.com/avatar/168e9c9d51f35eb9e61d14ccdc76fe23b36d30abb1cff7606a12302554b5b585?
      s=32&d=mm&r=g)
 109.  [Benjamin Denis](https://profiles.wordpress.org/rainbowgeek/)  2:18 pm _on_ 
      August 7, 2019
 110. Can’t wait!
 111. ![](https://secure.gravatar.com/avatar/c5debc287c39574307d9282c8b29a58caa8bc18884dd1a1161ff03dfcb437ae4?
      s=32&d=mm&r=g)
 112.  [Patrick Buntsma](https://profiles.wordpress.org/duisterdenhaag/)  2:39 pm _on_
      August 7, 2019
 113. +100
       As both a developer and user I have been reading along for some time now.
      I LOVE this project already. Reading all comments is extremely interesting. BRAVA
      to all!
 114. I feel that a notification bubble in the Adminadmin (and super admin) Bar is 
      already much less intrusive and annoying than all those Admin Notices now.
 115. I love the idea for sections.
       To avoid cluttering and spamming of WP Notify,
      I strongly vote for similar restrictions / layout as home screen notifications
      on your mobile phone. Short, sweet and straight to the point. Perhaps users could
      select the categoryCategory The 'category' taxonomy lets you group posts / content
      together that share a common bond. Categories are pre-defined and broad ranging.
      as well as per pluginPlugin A plugin is a piece of software containing a group
      of functions that can be added to a WordPress website. They can extend functionality
      or add new features to your WordPress websites. WordPress plugins are written
      in the PHP programming language and integrate seamlessly with WordPress. These
      can be free in the WordPress.org Plugin Directory [https://wordpress.org/plugins/](https://wordpress.org/plugins/)
      or can be cost-based plugin from a third-party.? Choose the type of notification
      in general, but also mute certain plugins/themes altogether. Yet, there should
      be an exception for high priority issues – that will always come through – by
      the WP CoreCore Core is the set of software required to run WordPress. The Core
      Development Team builds WordPress. Team for example.
 116. Spamming with a commercial banner when you delete a post, should be punishable
      in my opinion. I too tend to completely remove such plugins. So I do also vote
      for a possibility for users to report misuse by developers.
 117. Please correct me if I am wrong, I but I have not found a friendly way to notify“
      my” users other than through an “upgrade notice”. Yet, that is only shown in 
      the updates page and completely stripped to plain text, so users do not notice
      it.
       A push notification in WP Notify would certainly improve that. It will then
      also bypass the current (obvious) restrictions on update notices on MultiSitemultisite
      Used to describe a WordPress installation with a network of multiple blogs, grouped
      by sites. This installation type has shared users tables, and creates separate
      database tables for each blog (wp_posts becomes wp_0_posts). See also **network**,**
      blog**, **site**.
 118. ![](https://secure.gravatar.com/avatar/412521b833353b5e345699c38493ef10153265a35559d9015b15fb57defedd49?
      s=32&d=mm&r=g)
 119.  [Victor M Ramirez](https://profiles.wordpress.org/isvictorious/)  12:35 am _on_
      August 8, 2019
 120. I would love to be involved in fixing this issue. Notifications are currently
      the bane of my client dashboard existence.
 121. ![](https://secure.gravatar.com/avatar/c51a07d16b1608a83a35b1627ea48cf96d927f154fba90d556201ec3fc419272?
      s=32&d=mm&r=g)
 122.  [Kuba Mikita](https://profiles.wordpress.org/kubitomakita/)  7:10 am _on_ August
      9, 2019
 123. Sounds similar to my pluginPlugin A plugin is a piece of software containing 
      a group of functions that can be added to a WordPress website. They can extend
      functionality or add new features to your WordPress websites. WordPress plugins
      are written in the PHP programming language and integrate seamlessly with WordPress.
      These can be free in the WordPress.org Plugin Directory [https://wordpress.org/plugins/](https://wordpress.org/plugins/)
      or can be cost-based plugin from a third-party. which covers backend notifications:
      [https://wordpress.org/plugins/notification/](https://wordpress.org/plugins/notification/)
 124. I think you could take some ideas from it, as the developer APIAPI An API or 
      Application Programming Interface is a software intermediary that allows programs
      to interact with each other and share data in limited, clearly defined ways. 
      is pretty flexible.
 125. ![](https://secure.gravatar.com/avatar/791ebbe2ac92b4789fc4dce5bee3a6f256df13ab58d37e8d9a30db40a2b3f48b?
      s=32&d=mm&r=g)
 126.  [senki](https://profiles.wordpress.org/_senki/)  1:48 pm _on_ August 14, 2019
 127. I would love to be involved in this development. Maybe we can do something that
      lay out of the future of the modernisation of the WordPress
 128. ![](https://secure.gravatar.com/avatar/1894e91b32c9f80d8f30a42d360af6983a507f1cf2c621b7c9a0a0de14e011c5?
      s=32&d=mm&r=g)
 129.  [Xedin Unknown](https://profiles.wordpress.org/xedinunknown/)  6:07 pm _on_ 
      August 21, 2019
 130. I would be very happy to contribute to this, having had experience in building
      standards-compliant robust solutions in this area, including flash messages, 
      dismissable notifications, etc.
 131. ![](https://secure.gravatar.com/avatar/d90c229271bfd77e2082d964e37cef60b935fa3ab6682883a8407a6c086e6e4c?
      s=32&d=mm&r=g)
 132.  [Erin 'Folletto' Casali](https://profiles.wordpress.org/folletto/)  12:01 pm
      _on_ September 2, 2019
 133. As a designer that was involved in the earlier discussions, I can provide some
      design help depending on the needs of the project. I’d note for something like
      this that we should be striving to ship a small **modular MVPMinimum Viable Product"
      A minimum viable product (MVP) is a product with just enough features to satisfy
      early customers, and to provide feedback for future product development." - [WikiPedia](https://en.wikipedia.org/wiki/Minimum_viable_product)
      first, and extend it later**.
 134. I specifically note this as a counterpoint to “Why have so many complex moving
      pieces”. APIs can be built to start small and then evolved (this is usually the
      best approach). There’s no need to go full-blown from the start, it’s actually
      a problem as will make shipping delayed and would release something hard to grok
      for developers lowering the adoption. I agree there that abstractions help, the
      key is to **start with a small abstraction that can be extended** in future releases,
      and an excellent UXUX User experience, and work from there.
 135. I worry a lot about a project that starts with already a very narrow scope as
      this, I would stress to start with **two parallel explorations**, one APIAPI 
      An API or Application Programming Interface is a software intermediary that allows
      programs to interact with each other and share data in limited, clearly defined
      ways. side and one design side, and see where the balance strikes.
 136. ![](https://secure.gravatar.com/avatar/c574c55a53f66ba6812c477fb0502a9bc0270aeb82cecd71b213addbfd3d2bbd?
      s=32&d=mm&r=g)
 137.  [Mervin Hernandez](https://profiles.wordpress.org/hrmervin/)  4:26 pm _on_ November
      3, 2019
 138. Here is the requirements doc if anyone is interested in learning more / contributing.
      [https://docs.google.com/document/d/1SoIaFqXkXiVzq5mizbZQafMfL36bD0WKj8iwYM823MI/edit#heading=h.qpzqhl4y9i8b](https://docs.google.com/document/d/1SoIaFqXkXiVzq5mizbZQafMfL36bD0WKj8iwYM823MI/edit#heading=h.qpzqhl4y9i8b)

Comments are closed.

# Post navigation

[← WordPress Local Environment](https://make.wordpress.org/core/2019/08/05/wordpress-local-environment/)

[Editor Chat Agenda: August 7th →](https://make.wordpress.org/core/2019/08/06/editor-chat-agenda-august-7/)