# The forum should route the newcomer before they post > Why category banners, sidebars, scoped idea voting, vote-follow prompts, and category-level moderation keep a community useful before the reply count explodes. - Canonical HTML: https://growth.iangoh.com/blog/the-forum-should-route-the-newcomer-before-they-post/ - Published: 2026-05-30 - Updated: 2026-05-30T01:35:00Z - Categories: community-led growth, support-led growth, product feedback - Niches: SaaS, AI products, developer tools, open-source software, customer support software ## On this page - The first screen should explain what this category is for - The evergreen instructions should stay visible beside the live queue - Ideas should not fight with support for the same air - A vote should create a follow-up path, not just a score - Ownership should expand category by category ## Start with these related tactics - [Category banners from About-topic copy](/growth-ideas/category-banners-from-about-topic-copy/): Turn each category's About topic into a persistent banner so newcomers see the purpose, rules, and next click before they post. - [Topic list sidebars from closed guidance topic](/growth-ideas/topic-list-sidebars-from-closed-guidance-topic/): Attach a closed guidance topic as a category or tag sidebar so recurring instructions stay visible beside the live thread list. - [Ideas category type with topic voting defaults](/growth-ideas/ideas-category-type-with-topic-voting-defaults/): Create a dedicated ideas category that turns feature requests into a ranked backlog instead of a flat complaint list. 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](/growth-ideas/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](/growth-ideas/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](/growth-ideas/topic-list-sidebars-from-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](/growth-ideas/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](/growth-ideas/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](/growth-ideas/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](/growth-ideas/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](/growth-ideas/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](/growth-ideas/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](https://iangoh.com/advisory). ## Related GrowthDex tactics - [Category banners from About-topic copy](/growth-ideas/category-banners-from-about-topic-copy/) - Community, Website, Support - [Topic list sidebars from closed guidance topic](/growth-ideas/topic-list-sidebars-from-closed-guidance-topic/) - Community, Documentation, Website - [Ideas category type with topic voting defaults](/growth-ideas/ideas-category-type-with-topic-voting-defaults/) - Community, Product Feedback, Support - [Vote-to-watch prompt after idea upvote](/growth-ideas/vote-to-watch-prompt-after-idea-upvote/) - Community, Product Feedback, Lifecycle Messaging - [Category group moderation before global mod promotion](/growth-ideas/category-group-moderation-before-global-mod-promotion/) - Community, Support, Operations ## Essay chronology - [Newer essay: The admin listing should not hide the real setup](/blog/the-admin-listing-should-not-hide-the-real-setup/) - SEO, brand trust, marketplaces - [Older essay: A launch should teach before it interrupts](/blog/a-launch-should-teach-before-it-interrupts/) - launches, brand trust, customer support ## Keep reading - [The support forum should stop acting like a chat room](/blog/the-support-forum-should-stop-acting-like-a-chat-room/) - community-led growth, support-led growth, documentation - [The support queue should know what kind of thread it is](/blog/the-support-queue-should-know-what-kind-of-thread-it-is/) - support-led growth, community-led growth, brand trust - [The docs page should show signs of life before support does](/blog/the-docs-page-should-show-signs-of-life-before-support-does/) - documentation, proof surfaces, support-led growth ## Continue through the blog - [SaaS](/blog/#path-saas) - 3 essays in this path - [AI products](/blog/#path-ai-products) - 3 essays in this path - [developer tools](/blog/#path-developer-tools) - 3 essays in this path ## Sources - [Discourse Meta: Category Banners](https://meta.discourse.org/t/category-banners/86241?tl=en) · [GrowthDex source hub](/sources/discourse-meta-category-banners-meta-discourse-org/) - [Discourse Meta: Topic List Sidebars](https://meta.discourse.org/t/topic-list-sidebars/107561?tl=en) · [GrowthDex source hub](/sources/discourse-meta-topic-list-sidebars-meta-discourse-org/) - [Discourse Meta: Easily create Ideas categories using the Topic Voting plugin](https://meta.discourse.org/t/easily-create-ideas-categories-using-the-topic-voting-plugin/399365) · [GrowthDex source hub](/sources/discourse-meta-easily-create-ideas-categories-using-the-topic-voting-plu/) - [Discourse Meta: Improvements to Topic Voting](https://meta.discourse.org/t/improvements-to-topic-voting-voting-access-notification-prompts-and-hot-sorting/401156) · [GrowthDex source hub](/sources/discourse-meta-improvements-to-topic-voting-meta-discourse-org/) - [Discourse Meta: Category Group Review/Moderation](https://meta.discourse.org/t/category-group-review-moderation/116478?tl=en) · [GrowthDex source hub](/sources/discourse-meta-category-group-review-moderation-meta-discourse-org/) ## Editing notes - Kept the essay on one grounded claim: routing confusion creates cleanup work long before it creates community value. - Used plain forum scenes like pinned threads vanishing, support and ideas mixing together, and newcomers posting in the wrong lane. - Let the Discourse mechanics do the heavy lifting instead of inflating the piece with big community rhetoric. - Ended with an operating standard and the advisory CTA rather than a generic community conclusion. ## Advisory If you want help turning this into a growth system, Ian Goh offers advisory at https://iangoh.com/advisory.