I’m building essentially a directory of podcasts and I want to build the system so that each podcast has its own forum (or set of forums) – but linked with a single account that I’ll integrate to the directory with SSO.
I’m thinking that I can make each podcast its own category, and then each category page would show the subcategories it has posts in. However, this means I’ll likely have thousands of categories and I’m worried this is misusing how categories work (and that I might run in to performance issues having thousands). I’d obviously need to limit or even delete the ‘base’ view so that I’m not loading in every single category, but I imagine there may be other considerations I’m missing.
Does anyone have thoughts on this?
I’d additionally want to allow podcast owners to moderate their own podcast’s forums, but I believe this is doable (mods on per-category basis).
Thousands of categories gets really unwieldy, yes.
Are the subcategories going to be the same for every podcasts?
If so, you could combine tags here, with one category per podcast and tags replacing the subcategories, or have one set of categories with podcasts as the tags?
I would be super careful here, 1000 ghost towns and no real community is not a great recipe.
When it comes to sites for podcast fans really you want to be connected with the actual podcasters, interacting with them and providing ideas.
My recommendation would be to roll out slowly, make dedicated sites for your 3 top podcasts where the community interact with the podcasters and grow from there. Use SSO to provide delegated auth.
I’m not trying to build communities, strictly, and the purpose of the site is well off the scope of a forum. I’m wondering if the category system is what I should be using for this use case, not a validation of my business plans.