Right now, categories can only be nested one level, either in root, or nested under one parent. For a new forum we’re planning, it would be really nice if we could nest three levels. Is that something that might be “easily” enabled and/or is planned for the new future?
ie, I’d like (made up example):
Brands > Apple > iPhone
Brands > Apple > Mac
Brands > Google > Pixel
Other Root Category > Other > Other
thanx!
marc
Just to relate my own experience, we started our forum with lots of categories and subcategories, but after a year, we’re actually moving in the opposite direction – eliminating subcategories in many cases and using tags instead. I’ve found tags to be far more flexible, and their use surfaces content that users might otherwise miss by not looking in the “proper” category or subcategory.
Just something to consider!
Have you considered using tags to structure things beyond the subcategory? It’s something that works today as-is.
AFAIK there are no plans to go beyond subcategories, it has been discussed many times and the benefits just aren’t there.
It is a long story but we will be adding three levels as it comes up too often for enterprisey clients.
To me it is a clear case of “be careful what you ask for” but then some people willingly eat blood sausages, so… 
Those are delicious 
Jeff,
that is excellent news. we have thought long and hard about using tags, but I believe three levels of nesting are the right solution for what we wanna do (especially since categories do up-merge, i.e. the parent shows all posts from all its sub categories).
Do yo have a (guesstimated) time line? I know you cant make any guarantees, but are you thinking in terms of next week, next month, or next year?
thanx!
marc
Somewhere between next month and next year, but you can certainly make it happen faster by signing up to a enterprise plan with us 
Is there something comparable to that for self-hosting? we’re not really in there market for stopping to self-host, but that doesn’t mean we’d not be open to financially (or otherwise) contributing…
We occasionally take sponsorship for big features if we know we want to build them just can not justify cost at this second.
But fair warning, this would be expensive to sponsor, we are talking about 2-6 weeks of work at our current hourly rate. If you have budget to sponsor the whole thing, sure you can contact us at team@discourse.org
Gotcha. that’ll probably be a. bit out of the scope for the project we have this in mind for, but we’ll take the option under consideration… Thanx!
any idea on an ETA on this one ?
It is still on the same state:
Raising my hand for this feature, please.
We’re actively working on this at the moment. It will likely be available in the early new year.
哎呀，真没想到。我终于说服自己改用标签了。这真是一场情感过山车。
你最好使用标签。启用这个设置基本上就等于开启了“我喜欢打自己”的站点选项。
我该如何使用标签而不是嵌套子类别？
这个项目进展如何？我们从一开始就在使用标签，但我发现增加第三层级能帮我省去不少麻烦，并满足特定需求：
注意：在我们的网站上，类别被称为“频道”。
有两个频道服务于网站的核心功能，它们特意不设置子频道，而是广泛使用标签：
其他所有频道则用于实现辅助功能：反馈（网站和社区元沟通）、公告（所有对外沟通的历史和按时间排序的存档）、新闻动态（与我们目标相关的“外部”新闻）、资源、评测、HVAC（一个仅限订阅者访问的非 moderated 发泄区，其话题不对外显示）等。
实际上，这些顶级频道本可以设为标签，但我希望将它们的话题与其余内容隔离开来，因为它们具有特定功能，应归属于独立的“论坛版块”。遗憾的是，由于顶级层级用于为其所包含的相关频道组提供“版块标题”，目前无法设置子频道。
使用示例：
在“资源”频道中，我们有“书籍”、“培训”、“示例文件与代码片段”、“应用（免费向社区提供，按原样使用）”、“产品与应用（用于盈利）”、“插件”等。
插件在我们所使用的平台上非常重要，因此值得设立独立频道。特别是为了将它们与使用该平台开发的实际产品区分开来。
一些插件开发者积极推广自己的产品，我希望避免他们的几个插件主题帖子淹没在大量由这些积极推广者发布的“更新、公告、发布”等主题中。因此，我制定了一条规则：每个插件只能有一个主题帖子。除了需要不断提醒用户外，我还不得不持续清理该频道。
如果我能为每个插件创建子频道，我就可以让每位开发者/产品推广者自行管理其频道，发布促销、更新公告，同时将该特定插件频道的主题帖子数量限制为一个。
因此，我真的很期待能够再嵌套一层！
下一个超级实用的功能是支持“频道（类别）”级别的版主。能够仅对特定频道授予版主权限将会非常棒。
目前我的变通方法是创建一个名为 JohnDoe_curator 的群组，将 John Doe 设为该群组的所有者，并为 JDcollection 频道授予 JohnDoe_curator 群组的创建权限，同时授予 Everyone 群组的阅读和回复权限。
你好 Cécile——该项目已于几个月前完成，但在我们的托管计划中，仅面向企业客户开放。