> ## Documentation Index
> Fetch the complete documentation index at: https://notes.kodekloud.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Different Options in Discussions

> Guidance on GitHub Discussions categories, their purposes, examples, and best practices for organizing community conversations and improving contributor engagement

GitHub Discussions gives projects a structured, searchable place for community engagement that complements issues and pull requests. Selecting the right discussion category keeps conversations organized, helps contributors find relevant threads, and enables maintainers to triage and act on community feedback faster.

Below is a concise overview of each common Discussion category, its purpose, and practical examples of when to use it.

| Category      | Purpose                                                                                         | Use cases / Examples                                                           |
| ------------- | ----------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------ |
| Announcements | One-way channel for official project communications. Typically locked so only maintainers post. | Release notes, changelogs, major policy changes, project-wide updates          |
| General       | Open, casual space for community interaction related to the project.                            | Introductions, community socializing, off-topic but project-adjacent chats     |
| Ideas         | Collect and evaluate feature proposals, improvements, or experimental concepts.                 | Proposing new features, sharing design proposals, soliciting early feedback    |
| Polls         | Quick way to get community preference using votes.                                              | Prioritizing features, choosing a logo or name, making non-technical decisions |
| Q\&A          | Focused technical support area where answers can be accepted and surfaced.                      | Troubleshooting errors, configuration help, how-to questions                   |
| Show and Tell | Showcase what people have built with the project and celebrate community work.                  | Demos, case studies, plugins, integrations, notable implementations            |

## Category details and examples

* Announcements\
  Use Announcements for official, one-way communication from maintainers. Threads are often locked to prevent replies and keep the feed focused.
  * Examples: release notes, major policy updates, security advisories.

* General\
  A flexible area for community conversation that doesn’t belong in other categories.
  * Examples: welcome messages, informal discussions, community coordination.

* Ideas\
  Use this category to propose changes or gather preliminary feedback on new directions.
  * Examples: feature requests, UI redesign concepts, experimental approaches.

* Polls\
  Create quick, vote-driven polls to gauge community preference or consensus.
  * Examples: choosing the next feature to prioritize, selecting branding elements.

* Q\&A\
  Dedicated to troubleshooting and technical help. Replies can be marked as the accepted solution to guide future readers.
  * Examples: configuration help, debugging steps, platform-specific guidance.

* Show and Tell\
  Celebrate and share creative uses of the project to inspire others.
  * Examples: side projects, integrations, real-world case studies.

<Callout icon="lightbulb" color="#1CB2FE">
  Use categories consistently and include clear, descriptive titles and tags. This improves discoverability, speeds up triage, and helps future contributors find answers faster.
</Callout>

## Best practices for maintainers and contributors

* Create clear category descriptions so users know where to post.
* Encourage good titles and tags—these improve search results and help maintainers prioritize.
* Lock the Announcements category to preserve authoritative updates.
* Use the Q\&A category’s accepted answer feature to surface verified solutions.
* Regularly review the Ideas and Polls categories to gather community input for roadmaps.

## Links and references

* [GitHub Discussions documentation](https://docs.github.com/en/discussions)
* [How to use Discussions effectively](https://docs.github.com/en/discussions/using-discussions-in-your-project)

In summary, using the correct Discussion categories keeps your community organized, surfaces useful ideas and solutions, and enables maintainers to prioritize and act on feedback efficiently.

<CardGroup>
  <Card title="Watch Video" icon="video" cta="Learn more" href="https://learn.kodekloud.com/user/courses/github-foundation-certification/module/f42f6458-b9ea-4ebb-8cbd-261b2393e622/lesson/6562f691-9a5e-4f19-a31c-ac185545d903" />
</CardGroup>