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.
Why this can grow a startup
Many forums assume users will infer the difference between support, feature requests, announcements, and general discussion from a category name alone. They usually do not. Discourse Category Banners gives the operator a much plainer move: use the category description that already lives in the About topic and surface it as a visible banner on the category page. That reduces wrong-way posting, makes the first screen feel intentional, and gives each part of the forum a clearer job instead of one generic layout everywhere.
Source-backed example
Discourse's Category Banners theme component reads category descriptions from the automatically created About category topic and can show banners even when the operator disables the default hide-without-description setting.
Source-reported evidence
Source: Discourse Meta: Category Banners
The component uses the existing category description and can be configured not to hide banners when a category description is missing.
Attributed to the cited source; GrowthDex has not independently verified it. Use this as context, not as a forecast, benchmark, or recommended target.
Evidence scope: claims and metrics are attributed to the linked source; GrowthDex has not independently replicated the reported result. Check the original context and validate fit before applying it. Read the evidence methodology.
Source discovered: May 30, 2026
When to use it
Use this when Community, Website, Support is relevant to first-visit clarity, community onboarding, route hygiene and you can run a bounded test with a free budget.
When not to use it
Do not use it as a substitute for customer evidence, a clear owner, or a measurable stop condition. Local platform rules and market behavior still need checking.
How to do it
- Choose one target segment and define the exact next action this tactic should prompt.
- Adapt the tactic to Community and Website, using evidence from Discourse Meta: Category Banners as context—not as a promised result.
- Record a baseline for: Share of target users completing the product's first-value action. Set a guardrail that would make you pause the test.
- Run a narrow pilot and choose a test window that fits the normal decision or use cycle; do not scale before you have observed the full cycle.
- Compare the signal with its baseline. Scale only if the intended action improves without crossing the guardrail; otherwise revise one variable or stop and record what you learned.
Compare a stack for your situation
Compare source-backed tactics against your product, stage, budget and channel strengths, then choose one experiment to test.
Explore the context
Did you launch this experiment?
Report a launch to help us understand which growth ideas founders put into practice.
Apply this with an operator
Build creator and community systems around real incentives, trust, and repeat participation.