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

# Community Discourse Overview

> Track developer-community threads on Reddit, Hacker News, GitHub, Dev.to, and Stack Overflow, with citation overlaps and brand presence in one project view.

Community Discourse helps you understand how your product, competitors, and tracked topics show up in developer communities. It turns raw threads and replies into a project-level view of where the conversation is happening and which discussions overlap with your visibility opportunities.

## What Community Discourse Tracks

Community Discourse focuses on relevant conversations across supported sources:

* Dev.to
* Stack Overflow / Stack Exchange
* Hacker News
* GitHub
* Reddit threads
* Reddit comments on plans that include comment expansion

The system uses your configured brands and tracked URLs to find threads worth paying attention to, then summarizes how those threads connect back to your product and AI Search footprint.

## What You See on the Page

The page is organized around a shared source/date filter bar and a set of summary views:

### KPI cards

At the top of the page, DevTune summarizes the current slice with metrics such as:

* **Threads** - Relevant threads captured in the selected range
* **Relevant replies** - Replies/comments that materially contribute to the discussion
* **Source overlaps** - Threads that exactly overlap with tracked or AI-cited URLs
* **Clusters** - Threads where your primary brand and competitors appear together

### Top Communities

Shows which communities are producing the most relevant discussion volume for the selected filters.

### Brand Share

Shows how often your primary brand and tracked competitors appear across the captured community conversations.

### Intent Mix

Breaks the discussion into practical buckets such as recommendation, comparison, problem, tutorial, and other conversation types.

### Community Threads

The main thread table supports two views:

* **Latest** - Recently indexed discussions
* **Top** - Highest-scoring discussions

You can also toggle **Clusters only** to focus on threads where your brand and competitors are showing up together.

### Source-Linked Threads

This section isolates threads that contain exact overlaps with your tracked URLs or URLs already being cited in AI Search.

### Citations from Community Threads

This table shows the top community-thread citations for the current filter state. It follows the same page filters and highlights the strongest overlaps rather than showing a long paginated tail.

## Filters

Community Discourse uses shared page filters:

* **Source**
* **Date range**

These filters apply consistently across the KPI cards, charts, thread tables, and community citation table.

## Plan Differences

Community Discourse is available on paid plans, but the source mix differs by tier:

* **Starter / Plus** - Dev.to, Stack Overflow, Hacker News, GitHub, and Reddit threads
* **Enterprise** - Everything above, plus Reddit comments

This means lower-tier plans still see the thread layer across all core sources, while Enterprise plans get deeper Reddit discussion coverage.

## How to Use It

Community Discourse is most useful when you treat it as the bridge between raw community conversation and the rest of the DevTune workspace:

1. Use **Top Communities** and **Brand Share** to see where the conversation is strongest
2. Review **Latest** and **Top** threads for concrete discussion examples
3. Check **Source-Linked Threads** to find community conversations that directly overlap with your tracked URLs
4. Use **Actions** to turn the strongest patterns into content, docs, or competitive response work

## Best Practices

* Keep your **Brands** and **tracked URLs** up to date in Project Settings so community matching stays relevant
* Use **Clusters only** when you want to focus on discussions where competitors are actively present
* Pair Community Discourse with **AI Search** and **Owned Content** to see whether relevant discussion is also turning into citations and traffic

## Next Steps

* **[Project Navigation](/projects/project-navigation)** - See where Community Discourse fits in the workspace
* **[Actions Workspace](/insights-actions/actions-hub)** - Turn discussion signals into prioritized work
* **[AI Search Overview](/search-tracking/overview)** - Compare community signals with AI Search visibility