Skip to content
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

Hide tags with less than X sites on the Browse page #244

Closed
ndiego opened this issue Oct 12, 2023 · 4 comments
Closed

Hide tags with less than X sites on the Browse page #244

ndiego opened this issue Oct 12, 2023 · 4 comments
Labels
[Status] Not Applicable This will not be worked on

Comments

@ndiego
Copy link
Member

ndiego commented Oct 12, 2023

Can we kill/hide all tags with fewer than 3(?) members? E.g., https://wordpress.org/showcase-v2/tag/space/ isn't useful 😆

I broke out this comment from #234.

On most laptops, the site grid will have 2 sites per row, so I would recommend that we hide tags from the Browse page if the term has less than 2 sites. Thoughts @jasmussen @marko-srb?

image

@renintw with the current tag implementation on Browse, how hard would this be to implement? If it's easy, it would be great to get this in ahead of launch, but this could be punted to post-launch if needed.

@ndiego ndiego added the [Status] Needs Design Feedback Feedback is needed on an existing or new component label Oct 12, 2023
@ndiego ndiego moved this from Todo to On hold/blocked in WordPress.org Redesign: Showcase Oct 12, 2023
@jasmussen
Copy link

For what it's worth, I'm reading this as more of an editorial effort than a technical one. That if you click a tag and you only get two results, that's not a good experience begging the question why even have that tag in the first place? I agree with this, and lean towards either finding a way to use that tag on more sites, or remove that tag entirely. Previously we had a lot of cases like these, including a tag called "Eyewear", which would have two sites I believe.

If I'm getting this feedback right, it may have been from a previous iteration, however, where we did have tags with very few sites, but I can't see that anymore. The fewest sites we have in a tag now is 4:

Screenshot 2023-10-12 at 08 28 57

You can still get to a place where you combine enough tags, categories and flavors that you get few or no sites. I think that's related to separate tag/category/flavor conversations, and is arguably fine.

@marko-srb
Copy link

Here are my 2cents:

  • If removing all tags from TAGS page with 2 sites as results — leaves us with 10 tags there, then this is bad to do.
  • In any manner, 101 entry simply cannot provide a joyful experience if you press on most of the tags in the TAG page. So its more of, do we kill the TAG page, at this moment in time, or not, for me.

Now personal thought: I think it should stay. And I think it is ok if users come back and say hey folks what do we need this for, to consider removing. Plus I think we hid the index (Tags page) well enough, so it will be rarely used. All in all, I wouldn't touch Tags page (other than hiding flavors) at the moment. Also keep in mind that this is more a subjective view.

CC: @ndiego , @jasmussen

@marko-srb
Copy link

marko-srb commented Oct 12, 2023

We also should match the URL to the name in the breadcrumbs.

Either 'filters' either 'browse'. But I was prefering simply calling them 'tags' or 'wayfinding'. Why?

  1. Filters we do have in the All sites, as taxonomy.
  2. Browse is kinda results to search

So this can be confusing.

I had this comment before, but didn't work because we have categories and flavors.

@ndiego ndiego added [Status] Not Applicable This will not be worked on and removed [Status] Needs Design Feedback Feedback is needed on an existing or new component labels Oct 12, 2023
@ndiego
Copy link
Member Author

ndiego commented Oct 12, 2023

For what it's worth, I'm reading this as more of an editorial effort than a technical one.
All in all, I wouldn't touch Tags page

Great feedback everyone. Let's leave the Browse page as is, and we will do a more thorough audit of the tags to try and ensure all tags have at least two sites. I'll take care of this.

Given this direction, I am going to close the issue.

@ndiego ndiego closed this as completed Oct 12, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
[Status] Not Applicable This will not be worked on
Projects
None yet
Development

No branches or pull requests

3 participants