-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Validate the action bar #96202
Comments
Support References This comment is automatically generated. Please do not edit it.
|
We should fix these issues. |
For logged in users this widget has a lot of conceptual overlap with the admin bar. There are even duplicative actions "Edit Site", "Edit", etc. We could streamline things by migrating valuable actions to the admin bar, and otherwise removing the action bar. I acknowledge we also need to consider the logged-out state, but I also question the value there. Anecdotally I really dislike that I'm forced to display this element to visitors on my sites, and always add custom css to ensure it doesn't appear on the frontend. Unless it's a big driver of signups/engagement I'd consider removing it, or at least providing an option for site owners to hide it. |
@jameskoster just noting that there is some deduplication already happening here: 169373-ghe-Automattic/wpcom Repeating what I shared in another related issue:
I plan to queue up a micro project for one of the Loop squads to add an option (probably under Settings -> General) to toggle the entire action bar off for folks who prefer not to have it on their site. Also related: @annezazu shared a helpful recap issue. |
Some more convos in P2, internal ref:
|
Thanks for mocking that up. I'd say discoverability would be the primary reason. I suspect moving everything under the admin bar menu would significantly reduce visibility and therefore clicks. |
Without wanting to be flippant, isn't there also a chance it might lead to more clicks? On that train of thought could there be a middle-ground where action bar items are added to the admin bar, as a precursor to retiring the action bar down the road? |
Mind sharing more? Specifically, I'm trying to figure out why a random person reading a post would click into that dropdown? To me, I'd never expect to find engagement links (comment, reblog, subscribe) hidden behind that menu. |
Since the action bar hides on scroll, it's actually hard to spot in casual regular browsing. Site owners don't always even realise it's on their site. Because it's force-enabled on so many millions of sites (i.e. every WP.com site that doesn't hide it with custom CSS), it gets a lot of clicks by its sheer scale. @jameskoster The top-level masterbar and links within it are "more visible", but unlike the Action bar, the master bar stays hidden when you're not logged in to WP.com. Even if you're logged on to WP.com, sites with custom domains won't "see" that you are. Most folks don't see the masterbar when randomly browsing WP.com sites. That's why we shipped the floating subscribe button as a more visible replacement: Since it's just the regular Jetpack Subscription button, it blends with the site's styles, is customizable in Gutenberg, doesn't have a WP.com account signup wall, and works with paid newsletters. If it were enabled by default on every new blog (and just blogs, not on all regular sites), you'd likely get more free and paid subscribers to sites due to more visibility, and less friction. You wouldn't need to re-architect the Action bar to work the same way, and continuing maintaining two things for the same action. No matter how you change the Action bar's appearance to look like Gutenberg, it will never look like the site and theme, and visitors will have no idea about Gutenberg. It's just another site to them. Because it doesn't blend in at all, you're inclined to keep "hiding" it like the current Action bar, getting much less engagement compared to if it were just much bigger and more visible. Since Action bar is enabled by default on every site, you'll get folks subscribing to sites who's owners have no intention to gain subscribers or even publish posts. Even worse are sites where publishers use competing products to gain subscribers. It's common to find sites with thousands of subscribers, who then actually used MailerLite, MailChimp or other products instead, so we were just basically stealing subscribers from them and confusing their visitors. |
@simison That reads like an argument for removing the action bar altogether, in favor of blocks (like the Jetpack Subscription button). Is that a fair summary? Details users provide during onboarding can dictate whether or not those blocks are included. Hopefully this is trivial to do thanks to block hooks. This approach also provides the flexibility that users need to make these features feel like an actual part of their site, or to pick and choose exactly which ones to include (maybe I want a 'Subscribe' button but not a 'Reblog' one). |
Yeah, the Subscribe blocks are already using block hooks all over (navigation, after posts, etc) and I listed what to enable by default on which WP.com goal here; pfYzsZ-rr-p2 Likes/reblog/sharing/related posts aren't using hooks though, which is a gap since now they won't appear on site editor at all and just appear on the site's frontend. Issue: |
Are customers using the logged in action controls on the action bar? I'd like some validation on if this is used or not.
Logged in
Logged out
Action bar - whether it should be removed entirely
❓ Does the action bar offer so much value as to be undeletable?
❓ If not, should there be an alternative UX to offer the same functionality/links?
Only the "Edit site" is duplicated in the top admin bar.
The following action items are unique to the floating action bar:
The text was updated successfully, but these errors were encountered: