WordPress Theme Review Team seeks to curb obtrusive admin notices with new requirement to follow core design patterns – a comment


Note: Content might be outdated!

From the perspective of someone who has seen a shit ton of the admin notices mess in WordPress, it seems to me the Theme Review Team might be ahead of its time here. The UX issues it tries to tackle by enforcing core-style admin notices partly go beyond its responsibilities; trying to solve them on the theme level, in my humble opinion, could end up doing more harm than good for users.

WordPress Theme Review Team Seeks to Curb Obtrusive Admin Notices with New Requirement to Follow Core Design Patterns

The one example for an obtrusive notice provided in the team’s meeting was the onboarding notice of the Storefront theme, and the Tavern article provided two more examples of the same type of notice.

Trying to force the implementation of onboarding dialogues for more sophisticated themes into core-style admin notices seems like trying to put out a dumpster fire by, pardon my language, peeing on it – an initiative based on good intentions but incredibly short-sighted.

There is a clear responsibility of WordPress core to provide a more granular API for notices – one that enables visual prioritisation of system-relevant notices over advertising/marketing/upselling. The case for moving notices from their current slot in wp-admin to a dedicated Dashboard Widget and Toolbar item (thus making them less intrusive and more user-centric by default) seems pretty self-explanatory as well.

At the same time, the way of how the WordPress product ecosystem has implemented plugin and theme user onboarding via notices up to today sounds like a deafening cry for a dedicated onboarding API in core.

WordPress has benefited from the incredible diversity in its ecosystem but if that diversity still translates into everybody rolling their own UI within wp-admin in 2019, we’re offloading a key design responsibility of WordPress core to the people who rely on it – both, users and product providers.

I believe this is the underlying concern of the TRT, and I’m all for unifying UX in wp-admin, but as far as I’ve read their meeting notes, the TRT hasn’t provided any compelling argument for effectively banning user onboarding via admin notices aside from the arbitrary notion that bigger notices are undesirable somehow.

I’d like to counter-argue that limitations on how to use an existing notices API won’t solve the problem of a missing API for product onboarding.

One reaction on “WordPress Theme Review Team seeks to curb obtrusive admin notices with new requirement to follow core design patterns – a comment

  1. TRT, sure, go right ahead and fix the shortcomings by providing a uniform admin notice API that we can all benefit from, you get my vote, but ditch being the totalitarian enforcers of how themes should be built, stifling creativity and limiting functionality and ultimately sowing division within the community.

    If upon activation of a new theme the site doesn’t break and there is no nefarious intent, it’s valid enough for me even if it does diddly squat. Have you looked at the repo in the last decade? You clearly are not running a tight ship, except only when it suits you or someone points out your glaring hypocrisy.

    It’s my prerogative to know what’s best for me and my needs for a theme, not you.

    Otherwise…I see colorful language coming your way in the near future if things keep going this direction. I’m literally asking myself “what new enforcements are next with this group?”

Reactions are closed.