[buddypress-trac] [BuddyPress Trac] #9098: Rethink Site (Wide) notices

buddypress-trac noreply at wordpress.org
Sun Mar 10 08:15:28 UTC 2024


#9098: Rethink Site (Wide) notices
-------------------------+-----------------------
 Reporter:  imath        |       Owner:  imath
     Type:  enhancement  |      Status:  assigned
 Priority:  high         |   Milestone:  14.0.0
Component:  Messages     |     Version:  1.0
 Severity:  normal       |  Resolution:
 Keywords:  2nd-opinion  |
-------------------------+-----------------------

Comment (by imath):

 Thanks for your feedback @shawfactor

 Actually the first people needing it to be a Core feature is us the Core
 team :)

 The new direction I want to move Site Notices towards is like a BuddyPress
 "approaching" way of doing something that is taking way too long to happen
 in WordPress => https://wordpress.github.io/wp-feature-
 notifications/?path=/docs/feature-notifications-introduction--docs

 Although it seems to still be under development, it's been
 [https://github.com/WordPress/wp-feature-
 notifications/commit/21247d1a3e714f2181830ad4714944765f6ec433 6 years]
 since it started...

 We first need this to be a Core Feature to:
 - Inform about important changes happening in BuddyPress: the "Admin
 notifications" workaround we used for 11.4.0 is not satisfying to me as
 people expressed the need to be able to read again dismissed Admin
 notifications.
 - It could be used to inform about a getting started guide like it was
 suggested in Slack.
 - It could still be used by site Admins to inform users widely on the
 front-end and in the back-end.
 - It could be used by site Admins to warn specific roles like "author"
 about important thing to consider when contributing to content, etc..

 About using a "custom post type", this is not the reply to every need. I
 wonder why the WordPress feature as a plugin is not using the CPT feature
 😉
 https://wordpress.github.io/wp-feature-notifications/?path=/docs
 /documentation-database-schema--docs

 Finally, if it should be in its own component, then it needs to be outside
 of BuddyPress as a BP Addon like BP Attachments. The new direction we took
 is to shrink BuddyPress progressively to move optional components into BP
 Addons: **we won't add new BP Optional components anymore**.

-- 
Ticket URL: <https://buddypress.trac.wordpress.org/ticket/9098#comment:4>
BuddyPress Trac <http://buddypress.org/>
BuddyPress Trac


More information about the buddypress-trac mailing list