[wp-trac] [WordPress Trac] #65116: Feature request: On This Day dashboard widget

[WordPress Trac]

#65116: Feature request: On This Day dashboard widget
-------------------------+-------------------------------------------------
 Reporter:  alshakero    |       Owner:  (none)
     Type:  feature      |      Status:  new
  request                |
 Priority:  normal       |   Milestone:  Awaiting Review
Component:  Widgets      |     Version:  trunk
 Severity:  minor        |  Resolution:
 Keywords:  has-patch    |     Focuses:  ui, administration, sustainability
-------------------------+-------------------------------------------------

Comment (by eclev91):

 I just don't think "how cool would it be" (Matt's words regarding changes
 to the dashboard) is a good criteria for what should go into core.

 "There was a lot of excitement...it didn't get picked up."

 So not ''that'' much excitement.

 Matt goes on to talk about the low complexity of doing it, which is
 certainly true. But many things are easy without being worthy of doing.

 Maybe I'm missing context. The core committer minutes simply say "Are
 there new widgets that can be added..." with a couple of examples, which
 says to me "We think the dashboard could be more useful. There should be
 discussion around what makes it not useful. What would make it more
 useful?" The minutes don't suggest that conversation happened, but Matt,
 in the video meeting, mentions people "making the dashboard their own",
 which is an actionable goal and maybe even an important one.

 But this widget creates an additional query on the dashboard and loads yet
 another stylesheet, which is far from the experience I want on the
 dashboard if I'm making it my own. If you disable the widget with Screen
 Options, it just hides it with CSS. It doesn't remove the box and improve
 performance related to its inclusion. It's relevant to one subset of users
 and contributing to a noise problem for the rest. Does its default
 inclusion help people "make the dashboard their own", or does this serve
 only a subset of users rather than create a user experience pattern that
 actually serves the stated goal?

 I'm far from well plugged into core development, and the code is already
 written, but can this at least be something you opt into rather than have
 to disable on sites where it's irrelevant?

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/65116#comment:7>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform