Makes sense to me!
Overall, we’ve been heading in a direction where more things are configured per category rather than just site wide. We think allowing sites to treat categories as “building blocks” for their community will help sites evolve over time.
Given that, and what you’ve described, I think this suggestion makes a lot of sense.
A few things I think we need to be mindful of as we continue moving things in that direction in the product:
-
complexity of category setup / number of settings
we have tons of site settings. as more of these move into category configuration, how do we still keep the category setup process simple? perhaps the category types do enough by limiting the number of settings we expose for any given type of category… perhaps “advanced settings” is another way out. -
do we keep site settings and category settings?
i can imagine using the site setting as a way to set the “default” for new categories. but is that the approach we want to take? or do we get rid of the site setting when we move things over? -
ability to change things globally
if people want to change something across all or multiple categories, how do we make that easy? perhaps the new category management page is a way to approach this part of things.
all that said, we don’t need to figure everything out before we consider this.
I’ll share the idea with folks who’ve been working in this space recently.