Discourse doc category index sidebar for evergreen answers
Promote the best recurring answers into indexed documentation categories so the forum keeps its community energy without burying durable guidance.
Why this can grow a startup
A support community gets stronger when its best answers stop expiring inside old threads. Discourse Doc Categories gives teams a way to reserve categories for documentation, build an index topic, power a native sidebar, and run reports for missing or extraneous entries. That is useful because the archive can stay conversational while the durable answers become browsable. The docs also remain inside the same domain and search surface, which makes the transition from thread to reference much less jarring for users.
Source-backed example
Discourse's Doc Categories plugin uses an index topic to power a documentation sidebar, adds reports for topics not indexed or extraneous items, and supports the `in:docs` search qualifier across documentation categories.
Source-reported evidence
Source: Discourse Meta: Discourse Doc Categories
The plugin adds missing-topic and extraneous-item reports and lets `in:docs` search across categories that have an index topic assigned.
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 29, 2026
When to use it
Use this when Community, Documentation, SEO is relevant to evergreen answers, docs architecture, searchable knowledge base and you can run a bounded test with a medium 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 Documentation, using evidence from Discourse Meta: Discourse Doc Categories as context—not as a promised result.
- Record a baseline for: Qualified search visitors who complete the intended next 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
Turn isolated search tactics into a crawlable visibility system tied to demand and proof.