That reminds me of one thing with Discourse as a project, that isn’t really ideal to me as a user. The fact that the project does not use a proper public issue tracker for bugs and planning.
E.g, when I read Hugh’s response, my internal project manager immediately raised the question: where, where was this logged?. I know, my internal PM is a nosy little creature, isn’t he? 
I suppose using meta.discourse.org as an issue tracker gives the project an opportunity for “dogfooding” Discourse. And all other issue trackers have their own faults, so it’s a pain having to choose one. But to me Discourse - while being excellent as a forum for questions and discussions - is very lacking as an issue tracker. For that purpose it lacks effective categorization, info about affected and target versions, issue numbers, prioritization, effective means to filter issues by status, age, priority, product or compoents, and a good way to present a roadmap for a feature or the product as a whole, among other things.
Well, I digress. And I haven’t contributed a single line of code, bug report, or feature request yet, so who am I to complain. 
So, again, thank you all for the awesomeness of Discourse. And pardon the semi-rant.
And on topic, great to hear that Discourse Doc Categories, while not polished yet, is considered architecturally stable. I’ll check if I can get it installed on my hosted Discourse instance, and if so try to return with feedback. Thanks!