# 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.

- Canonical HTML: https://growth.iangoh.com/growth-ideas/discourse-doc-category-index-sidebar-for-evergreen-answers/
- Source: [meta.discourse.org](https://meta.discourse.org/t/discourse-doc-categories/322376?tl=en)
- GrowthDex source hub: [Discourse Meta: Discourse Doc Categories](/sources/discourse-meta-discourse-doc-categories-meta-discourse-org/)
- Last checked: 2026-05-29
- Rarity: rare
- Budget: medium
- Channels: Community, Documentation, SEO
- Stages: evergreen answers, docs architecture, searchable knowledge base, internal linking


## Why this can grow

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.

## Ian's take

From scaling consumer platforms across MENA and Southeast Asia, my default is to distrust growth work that only looks good in a slide. For SEO and AI search, I care less about clever keyword tricks and more about clarity. A buyer, crawler, or answer engine should quickly understand who this is for, why it works, what proof backs it, and what page deserves to be cited. I would run it small enough to learn quickly, then only scale the parts that real users repeat, save, reply to, or buy from. For this tactic, I would watch one clear growth signal before putting more time or budget behind it.

## Action plan

1. Define one narrow startup segment where discourse doc category index sidebar for evergreen answers can create a measurable lift.
2. Turn the tactic into one offer, page, campaign, or workflow for the Community and Documentation channel.
3. Use the evidence from meta.discourse.org to set the first version of the message, format, and audience.
4. Launch a small test for 7 to 14 days with one success metric: one measurable growth signal.
5. Review the result, keep the winning message, remove weak variants, and turn the learning into a repeatable growth playbook.

## 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.

## Adjacent tactics in the same lane

- [Doc category index for community knowledge base](/growth-ideas/doc-category-index-for-community-knowledge-base/) - same source, 2 shared channels
- [Topic list sidebars from closed guidance topic](/growth-ideas/topic-list-sidebars-from-closed-guidance-topic/) - 2 shared channels, 1 shared stage
- [Markdown file links for version-safe docs navigation](/growth-ideas/markdown-file-links-for-version-safe-docs-navigation/) - 2 shared channels, 1 shared stage
- [High-traffic help articles linking to low-traffic answers](/growth-ideas/high-traffic-help-articles-linking-to-low-traffic-answers/) - 2 shared channels, 1 shared stage

## Read GrowthDex essays

Browse the plain-English essay index at [GrowthDex Blog](/blog/).

## Related GrowthDex essays

- [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

## Advisory

If you want help turning this into a working growth system, Ian Goh offers advisory at https://iangoh.com/advisory.