WordPress.org

Making WordPress.org

Opened 3 years ago

Last modified 3 months ago

#527 new enhancement

Profiles: Badges should link to the corresponding team

Reported by: SergeyBiryukov Owned by:
Milestone: Priority: normal
Component: Profiles Keywords:
Cc:

Description

Core Team or Plugin Developer badges might be self-descriptive, but when you see a Community Team badge on someone's profile, you have to go to make.wordpress.org and look for the team description there to get more details.

I think the badges should link either to the team blog, or to the description on make.wordpress.org (with an anchor).

Change History (13)

#1 @marktimemedia
3 years ago

#722 was marked as a duplicate.

#2 follow-up: @marktimemedia
3 years ago

Agreed, and as a followup the following suggestions:

a) add a tooltip or something to just say what the icon means (plugins, meta, speaking/organizing, etc)

b) would be good to have them link to their respective make.wordpress.org pages for now, but in the future a central page with all the badges and a summary of what they mean similar to the materials handed out at WCSF (since I know some of the badges for speaking, community, etc are not on the main make.wordpress.org page)

#3 @NikV
3 years ago

+1 to the tooltip. Though I believe there could be potential accessibility issues with the tooltip, so we need to make sure that's all checked over if we are to add that.

#4 @iandunn
3 years ago

Adding text to them is being discussed in #420.

#5 in reply to: ↑ 2 @kpdesign
3 years ago

Replying to marktimemedia:

Agreed, and as a followup the following suggestions:

a) add a tooltip or something to just say what the icon means (plugins, meta, speaking/organizing, etc)

Each badge already has a tooltip - I can hover over each one in Chrome, and it shows me what it is.

The markup for the Plugin Developer div is:

<div class="badge item dashicons badge-plugins dashicons-admin-plugins" title="Plugin Developer"></div>
  ::before
</div>

As @iandunn indicated, there are some accessibility concerns with the current implementation being discussed in #420.

I definitely agree that the team badges should link to their respective Make blogs, or to the plugin/theme tabs in a developer's profile (such as mine). Not sure what the organizing/speaking badges would point to yet.

#6 @iandunn
3 years ago

WordCamp organizers don't have a separate badge, they're just considered part of the Community team, so those badges should link to the Community team.

WordCamp speakers are less clear, though. Should they link to the Community team? WordCamp Central? WPTV?

What about Plugin/Theme developers? Should they link to the "about" page for the respective repositories? The home page for the respective repositories?The plugins/themes tab on their profile?

Maybe it'd help to identify the reasons why a user would click on a badge. Do they want to know what the badge means? How they can get it? Something else?

Personally, I'm leaning towards speaker badges linking to the Community team and plugin/theme badges linking to the "about" page for the respective repositories, but I can see good arguments for other conclusions, too. What does everyone else think?

This ticket was mentioned in Slack in #meta by ocean90. View the logs.


23 months ago

#8 follow-up: @coffee2code
16 months ago

One consideration is to have each badge link to a badges page in the respective team's contributor handbook.

Badges are intended as a reflection of participation in a WordPress.org team, so it seems natural to point users to information within a team's contributor's handbook (which live within the team's make site). Such pages should list the badges they provide and the criteria used to earn a badge. Then they could take that opportunity to point these interested users to other parts of their handbook to encourage them to get involved with the team.

This also provides a consistent experience for users since the badges would link to similar explanatory pages instead of to potentially disparate targets (a profile tab for one, a make site for another, an about page of sort for another) which may not be immediately clear how it relates to a badge or how one earned/earns it.

Having a centralized page (which we do already in the meta team's handbook, though it could use sprucing up to show each of the badges and a bit more info) has its merits as well.

#9 in reply to: ↑ 8 ; follow-ups: @SergeyBiryukov
16 months ago

Replying to coffee2code:

One consideration is to have each badge link to a badges page in the respective team's contributor handbook.

I like that, makes a lot of sense.

This ticket was mentioned in Slack in #community-events by bph. View the logs.


5 months ago

#11 in reply to: ↑ 9 @melchoyce
5 months ago

Replying to SergeyBiryukov:

Replying to coffee2code:

One consideration is to have each badge link to a badges page in the respective team's contributor handbook.

I like that, makes a lot of sense.

+1

#12 in reply to: ↑ 9 @danieltj
3 months ago

Replying to SergeyBiryukov:

Replying to coffee2code:

One consideration is to have each badge link to a badges page in the respective team's contributor handbook.

I like that, makes a lot of sense.

Good idea, but requires all teams to get their handbook updated.

Who can update a handbook for a team? Is it just the team members or anyone? I'd like to see the badges link to the team directly with more info on getting involved etc. As of right now there is a brief summary in the general handbook but it's not very clear for some badges and others are completely missing.

#13 @SergeyBiryukov
3 months ago

  • Type changed from defect to enhancement
Note: See TracTickets for help on using tickets.