A lot of forums ask the user to understand the whole operating model before the first click.
Support goes in one place. Feature requests go somewhere else. Rules live in a pinned thread. The real experts are mixed into the crowd. None of that is obvious to a new visitor who just wants to ask one question without looking foolish.
When that route is unclear, the forum starts generating cleanup work instead of useful discussion.
The first screen should explain what this category is for
Category banners from About-topic copy is such a good fix because it uses content the team should already have. The About topic holds the category description anyway. Surfacing it as a banner means the visitor sees the purpose, the norms, and the likely next move before posting into the wrong lane.
I would pair that with Discourse topic template before support post submit. One tells the user where they are. The other tells them what a useful post looks like once they get there.
The evergreen instructions should stay visible beside the live queue
Topic list sidebars from a closed guidance topic fixes a common forum mistake. Good instructions are often trapped in a pinned topic that disappears into the scroll. A sidebar keeps the checklist, links, and caveats in view while the list of live threads keeps moving.
That sits naturally next to Discourse doc category index sidebar for evergreen answers. One helps before the post. The other helps after the answer becomes durable.
Ideas should not fight with support for the same air
Ideas category type with topic voting defaults is really a routing move disguised as a feature request tool. Once product requests live in their own category, support threads stop carrying roadmap arguments they were never built to resolve.
It also works well beside Discourse solved schema and search priority. Support needs finished answers. Idea categories need ranked demand. Treating both as the same thread type is how communities become noisy.
A vote should create a follow-up path, not just a score
Vote-to-watch prompt after idea upvote is the detail I like most in this batch. It closes the gap between passive agreement and actual follow-through. If someone cares enough to vote, asking them to watch the topic is a clean way to keep the right audience attached when the request changes shape.
The Hot sorting change matters too. Communities often confuse old cumulative demand with current momentum. Those are not the same signal.
Ownership should expand category by category
Category group moderation before global mod promotion is a better growth move than it first sounds. A healthy forum needs more than official staff. It needs trusted operators who can keep one area clean, fair, and useful without taking over the entire site.
I would use that alongside Discourse category experts for ask-an-expert routing. One creates visible authority in the discussion. The other gives some of that authority real operating power where it is earned.
This cluster is strongest for SaaS, AI products, developer tools, open-source software, and any support-heavy product where the community doubles as onboarding, self-serve help, and roadmap intake. The standard is simple. A newcomer should be able to tell where to go, what belongs there, and who is in charge before they write the first post.
If you want help turning a support forum, docs surface, or product-feedback queue into a cleaner growth system, the advisory CTA is here: work with Ian Goh.