Finding subcategories via the category dropdown in the topic list

AI-generated summary

The discussion addresses inconsistencies in how subcategories are accessed via the category dropdown in the topic list compared to the composer. Currently, a search field allowing direct subcategory access only appears if there are 10 or more options, a logic Moin notes is based on PR #36062. mcwumbly highlights that this search field does not appear unconditionally, showing different behaviors for different users. Moin suggests that subcategories should be counted toward the 10-option threshold to ensure the search field appears, a proposal mcwumbly supports as a good initial step. awesomerobot raises the broader question of merging category and subcategory dropdowns to match the composer’s single dropdown, though Moin points out the complexity of supporting options like “parent only” versus “parent and subcategories” within a unified menu. Finally, mcwumbly cross-posts stephtara’s concern that the lack of direct subcategory access is problematic for community organization, suggesting UI patterns that either drill down into subcategories or display them prominently depending on posting permissions.

Continuing the discussion from Updating how categories are organized on Meta:

Currently, in the topic list, we only show top level categories in the category dropdown:

In some conditions, a search field appears, where you can directly access subcategories:

But that doesn’t show up unconditionally (I think it depends on how many categories one can see perhaps?)

In the composer and other areas of the app, on the other hand, people can always navigate directly to a subcategory.

A couple thoughts:

  • (a) Should we update the logic that determines whether the search field appears?
    In particular, it’d be helpful for it to show up for everyone on meta now while we’re experimenting with a more nested category structure
  • (b) Should we consider making it more like the rest of the category dropdowns, like the one in the composer?
    This would be a bigger change than (a), but perhaps it’s worth considering making it more consistent with other category choosers?
2 Likes

Based on the PR that added hiding the search, FIX: category page improvements by yuriyaran · Pull Request #36062 · discourse/discourse · GitHub, “some conditions” are 10 options.

“hide search input in filters dropdown if list is less than 10 options”

To me, it feels like while they aren’t shown by default, the subcategories that search would return should be counted to determine if there are more than 9 options.

2 Likes

I think that is a good, targeted, first move here.

2 Likes

Might be worth thinking about if we should merge category + subcategory dropdowns too — we have a single dropdown in the composer so showing subcategories there is necessary.

In the nav, the dropdowns are kind of also breadcrumbs so we deconstruct and have separate category + subcategory + tags menus

2 Likes

How do you want to support the “no subcategories” option in one dropdown?

The concept of selecting if you want to see

  • posts from the parent and all subcategories
  • only posts from the parent
  • posts from one of the subcategories

makes sense to me. You need the “no subcategories” option to get what used to be Support, now that it has lots of subcategories. So I am not sure how that would work within one menu.

3 Likes

xposting for context here

1 Like