# GitHub Discussions sections for announcements questions and ideas

> Separate announcements, Q&A, and idea threads into clear sections so visitors know whether they are reading a broadcast, a solved answer, or an open-ended product debate.

- Canonical HTML: https://growth.iangoh.com/growth-ideas/github-discussions-sections-for-announcements-questions-and-ideas/
- Source: [docs.github.com](https://docs.github.com/en/discussions/managing-discussions-for-your-community/managing-categories-for-discussions)
- GrowthDex source hub: [GitHub Docs: Managing categories for discussions](/sources/github-docs-managing-categories-for-discussions-docs-github-com/)
- Last checked: 2026-06-05T13:35:00Z
- Rarity: uncommon
- Budget: free
- Channels: GitHub, Community, Product Marketing
- Stages: information architecture, community segmentation, launch communication, product feedback
- Key metric: GitHub supports up to 25 discussion categories, each with a format and optional section assignment.

## Why this can grow

Most community spaces feel messy for a boring reason: every kind of conversation is thrown into one scrolling list. GitHub Discussions lets maintainers choose category formats, add descriptions, and nest categories inside sections. That means release updates do not have to fight support questions for attention, and ideas do not need to look like bug reports. Once the archive has lanes, readers can self-sort faster and maintainers can build habits around each lane instead of moderating one giant mixed queue.

## 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. My bias is to treat this as a small market test first. Make the audience narrow, make the promise concrete, and let the first real response decide whether it deserves more work. 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 github discussions sections for announcements questions and ideas can create a measurable lift.
2. Turn the tactic into one offer, page, campaign, or workflow for the GitHub and Community channel.
3. Use the evidence from docs.github.com 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

GitHub Docs says each discussion category has a format such as announcement, question and answer, or open-ended discussion, and each repository or organization can create up to 25 categories that can be grouped into sections.

## Adjacent tactics in the same lane

- [GitHub profile README as operator proof surface](/growth-ideas/github-profile-readme-as-operator-proof-surface/) - 2 shared channels
- [GitHub community profile checklist as trust audit](/growth-ideas/github-community-profile-checklist-as-trust-audit/) - 2 shared channels
- [GitHub contributing tab before first PR](/growth-ideas/github-contributing-tab-before-first-pr/) - 2 shared channels
- [GitHub saved replies for triage and duplicate routing](/growth-ideas/github-saved-replies-for-triage-and-duplicate-routing/) - 2 shared channels

## Read GrowthDex essays

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

## Related GrowthDex essays

- [The community archive should answer the next visitor](/blog/the-community-archive-should-answer-the-next-visitor/) - community-led growth, SEO, documentation

## Advisory

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