Clearly identify which plugins we support in-house

[davemart-in]

Description

We've received feedback from Happiness Engineers (HE'S) on multiple occasions that it would be great if we could do a better job of clearly identifying the plugins which we support within the plugin directory.

Expected

When HE's chat with Business and eCommerce plan customers it would help if there were an easier way to point out which plugins are maintained and supported by Automattic and which plugins Customers will have to turn to third-party plugin developers to for support.

Actual

We've actually got three different plugin directories:

1) Calypso Plugin Directory

2) Calypsoified Plugin Directory

3) WP-Admin Plugin Directory

We'll need to come up with a design that works.

[davemart-in]

Related #43231

[Aurorum]

What about something like this?

I'm not sure how challenging it would be to get working in the other plugin directories, but in Calypso, it wouldn't be too tricky. I think it's also quite clear.

						{ this.props.plugin.author_name === 'Automattic' && (
							<InfoPopover
								className="plugins-browser-item__house-gridicon"
								position="top left"
								icon="house"
							>
								{ this.props.translate(
									'This plugin is supported in-house, so we can help provide support with it.'
								) }
							</InfoPopover>
						) }

[github-actions]

This issue is stale because it has been 180 days with no activity. You can keep the issue open by adding a comment. If you do, please provide additional context and explain why you’d like it to remain open. You can also close the issue yourself — if you do, please add a brief explanation and apply one of relevant issue close labels.

[cpapazoglou]

This is still relevant for the Marketplace efforts

[allilevine]

This seems like a high priority now that we're featuring premium plugins. We also want to feature our free plugins, and indicate support and ownership. See: p1645042945001419/1645042800.545619-slack-C029JEQRVRT

Do we have this data (support, ownership) for each plugin?

[lsl]

Do our customers know who Automattic is? A good first step might be to .replace("Automattic", "WordPress.com").

(Though I really like the extra badge up in the corner idea too)

Do we have this data (support, ownership) for each plugin?

@allilevine it looks like we're loading this info straight out of .org's plugin endpoints so we have what you can see on wordpress.org.

[cpapazoglou]

Do our customers know who Automattic is?

That's an interesting perspective. And I would agree. I would tend though to keep some source of truth like wordpress.org uses Automattic. The badge though can certainly reference WordPress.com like WordPress.com Pick or Curated by WordPress.com

[cpapazoglou]

@SaxonF , @vinimotaa after doing a Marketplace walkthrough I noticed that we can do a better job in marketing our paid search results. Searching for subscriptions (our top selling product) I get the following results

there isn't any incentive for the user to pick the WooCommerce Subscriptions over Paid Memberships Pro. Is there something we can do to alleviate that?

[gcsecsey]

@SaxonF could you help with how could we clearly identify our curated search results?

[gcsecsey]

Backlog grooming:
Apart from the design updates on the search results, we'd like to display WooCommerce or WordPress.com as an author name instead of Automattic on first-party plugins, so that users unfamiliar with the company name can be more confident about the plugin.

[cpapazoglou]

@SaxonF and @vinimotaa have we also considered this in marketplace mockups?

[vinimotaa]

@cpapazoglou

Apart from the design updates on the search results, we'd like to display WooCommerce or WordPress.com as an author name instead of Automattic on first-party plugins, so that users unfamiliar with the company name can be more confident about the plugin.

Are you talking about this?

[cpapazoglou]

@cpapazoglou

Apart from the design updates on the search results, we'd like to display WooCommerce or WordPress.com as an author name instead of Automattic on first-party plugins, so that users unfamiliar with the company name can be more confident about the plugin.

Are you talking about this?

@vinimotaa both this and

could you help with how could we clearly identify our curated search results?

[cpapazoglou]

👋 @vinimotaa can you take a look at this again?

I think that clearly showing which plugins come from Automattic would have better results in users selecting them.