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?
“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.
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
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.
