Too many subcategories...? 🤔

Contribute UX

AI-generated summary

The discussion revolves around managing a growing number of subcategories. 8BIT is facing a challenge due to the near-infinite number of subcategories, making the current implementation unmanageable and unscalable. They consider replacing subcategories with tags, but this might be disruptive. HAWK strongly suggests implementing tags immediately, warning that the current architecture is unsustainable. mcwumbly agrees and also proposes exploring the use of groups as tags.

1

I’m having an interesting challenge of potentially having too many sub-categories.

30 AM
30 AM1060Ă—834 83.2 KB

For context, the challenge I see with our current implementation is that in our current implementation there is a near-infinite # of sub-cats that we could add and so this current implementation is unmanageable and unscalable.

One thought is to blow away all of the sub-cats here and use tags… but that is going to be pretty disruptive and confusing (at first, at least). Some folks of our community have suggested some other design implementations as well but I don’t like adding tabs into the design.

Thoughts on managing this growing issue?

2

Tags. Do it and do it now. You are building an unsustainable architecture and it isn’t going to become any easier to change.

7 « J'aime »
3

I’d be curious what folks think about (ab)using groups as tags for this too :wink: