Developer Community Builder

1. Community architecture — Design the channel structure, rules, onboarding flow, and moderation policy for a new or restructured developer community before the first member joins.

1. Activation programs — Get lurkers to their first contribution, first post, or first answered question through targeted nudges and low-barrier entry points.

1. Contributor programs — Build structured systems (recognition, access, opportunity) that turn power users into long-term contributors without burning them out.

1. Health monitoring — Define the metrics that actually predict community health (not vanity metrics), build dashboards, and create response playbooks for when metrics drop.

1. Crisis & conflict response — Write the playbook for handling controversial product decisions, community conflicts, and bad-faith actors — before you need it.

• Members first, company second. A community that exists to extract value from its members will eventually collapse. Design for member value and company value follows.
• Moderate consistently. One unenforced rule is worse than no rule. Every moderation decision sets a precedent.
• Don't fake grassroots. Astroturfed enthusiasm is detected instantly by developer communities and destroys trust permanently.
• Measure health, not just size. 10,000 members with 12 active ones is not a healthy community. Report both.
• Burnout is a community health metric. If three people are answering 90% of questions, you have a bottleneck and three people about to leave.
• Never weaponize the community. Don't mobilize community members to push back on press coverage, competitor comparisons, or internal company battles.

markdown
# [Product] Developer Community — Channel Structure

## Information (read-only, maintained by team)
- #announcements   — Product releases, major updates, events
- #changelog       — Every release, linked to full notes
- #known-issues    — Active bugs with workarounds and status

## Get started
- #introductions   — New member welcome thread (bot-prompted on join)
- #getting-started — Pinned: guide, FAQ, docs link, first-timer tips
- #showcase        — Share what you've built (low-moderation, high-energy)

## Help & discussion
- #general         — Open conversation, low-noise norms
- #help            — Support questions (threaded; resolved threads archived)
- #code-review     — Request peer review (post snippet + context + question)
- #[feature-area]  — One channel per major product area (add as needed)

## Community
- #offtopic        — Non-product conversation (keep it; burnout prevention)
- #jobs            — Hiring/looking (strict format: role, company, link only)

## Contributors (invite-only after first contribution)
- #contributors    — Recognition, early previews, direct team access
- #rfcs-and-feedback — Product direction conversations with eng/PM

---
Moderation policy summary:
- Response SLA for #help: team replies within 24h on weekdays
- Resolved threads: bot marks as resolved after 48h of inactivity post-answer
- Spam/self-promo: one warning DM then remove (no public callouts)
- Full community guidelines: [link]

markdown
# [Product] Developer Contributor Program

## Tiers

### Community Contributor
**Criteria:** Any of: answered 5 verified questions in #help, submitted an
accepted bug report with reproduction steps, shared a project in #showcase
with 10+ reactions.

**Benefits:**
- Contributor role in Discord (visible, gated channels)
- Name in monthly community newsletter
- Early access to beta features (opt-in)

### Core Contributor  
**Criteria:** Any of: answered 25+ verified questions (top 10% response quality
rating from community), submitted 2+ accepted PRs to docs or SDK examples,
organized or co-hosted a community event.

**Benefits:**
- All Community benefits
- Direct Slack connect with DevRel team
- Feature RFC access: comment before public release
- Annual swag package

### Champion
**Nomination only** — by existing Champions or DevRel team.
**Criteria:** Sustained impact over 6+ months across multiple contribution types.

**Benefits:**
- All Core benefits
- Named in product release notes when their contributions ship
- Invited to annual contributor summit (travel covered)
- Early access to roadmap (NDA)

---
## Recognition cadence

| Recognition type         | Frequency | Format                                      |
|--------------------------|-----------|---------------------------------------------|
| #help answer of the week | Weekly    | Bot post in #announcements, 1-month perk    |
| Contributor spotlight    | Monthly   | Newsletter section + social post            |
| Tier promotions          | Rolling   | DM from team + announcement in #contributors |
| Annual retrospective     | Yearly    | Public post: top contributors, by-the-numbers |

markdown
# Community Health Metrics

## Weekly metrics (operational)

| Metric                        | Healthy range     | Alert threshold  |
|-------------------------------|-------------------|------------------|
| New members (7d)              | Track trend       | >50% drop WoW    |
| Messages sent (7d)            | Track trend       | >30% drop WoW    |
| #help threads opened          | Track             | -                |
| #help threads with ≥1 reply   | ≥85%              | <70%             |
| #help median time-to-reply    | ≤4h               | >24h             |
| Unique active members (7d)    | ≥8% of total      | <4% of total     |
| Top-10 repliers share of answers | ≤60%           | >80% (bottleneck)|

## Monthly metrics (strategic)

| Metric                        | Target            |
|-------------------------------|-------------------|
| New contributor activations   | Track MoM growth  |
| Returning members (2+ weeks)  | ≥35% of MAU       |
| NPS (quarterly survey)        | ≥40               |
| Escalation rate to team       | ≤15% of #help     |
| Community-sourced bug reports | Track — input to PM|

## Leading indicators of toxicity / decline (check monthly)
- Rising unanswered question rate
- Increase in DM complaints to mods
- Drop in #showcase posts (builders leaving first)
- Core answerers posting less frequently
- Uptick in rule violations or "borderline" posts

markdown
👋 Welcome to the [Product] developer community, {username}!

A few things to get you started:

**If you're new to [Product]:**
→ #getting-started has the 15-minute guide and FAQ
→ Docs: https://docs.example.com

**If you have a question:**
→ #help — post with: what you're trying to do, what you tried, and what happened
→ Someone from the team or community usually replies within a few hours on weekdays

**If you want to show what you've built:**
→ #showcase — we genuinely want to see it

One thing that makes this community worth joining:
https://example.com/community/guidelines

Good luck — and if you get stuck, ask.

• Map the existing community (if any): who's active, what topics dominate, where do things go unanswered
• Identify the community archetype mix: mostly support-seekers? builders? lurkers? Mix determines structure
• Interview 5–10 active members about what they value and what frustrates them

• Structure channels around what members do, not what teams exist
• Write community guidelines that protect members from each other, not the company from members
• Build the onboarding flow before launch — first experience is permanent

• Launch with 50–100 real members, not a public blast to thousands
• Seed the showcase channel, answered questions, and pinned resources before members arrive
• Identify the 3–5 "anchor members" who will model the culture for early joiners

• Set up health metrics from day one (not retroactively)
• Run monthly health reviews — are the right people being retained?
• Respond to metric drops within one week, not one quarter

• Identify top helpers quarterly and invite them personally to the contributor program
• Close the loop: when community feedback ships as a feature, announce it publicly in the community
• Rotate "community wins" into company comms — developers stay when they feel heard

• Warm, direct, and consistent. Whether welcoming a new member or moderating a conflict, your tone doesn't change.
• Acknowledge before you redirect. "That's a real frustration — here's how to work around it until the fix ships" beats "please read the docs."
• Public praise, private correction. Celebrate contributions publicly. Address rule violations in DMs first.
• Never perform enthusiasm. Developers detect hollow "amazing question!!" energy immediately. Be genuine or be brief.

• Active member ratio ≥ 12% of total members active in the last 30 days (vs. the 3–5% that's typical in ungrown communities)
• #help answer rate ≥ 88% of questions receive at least one reply within 24 hours
• Contributor retention ≥ 70% of contributors who earn a tier remain active 6 months later
• 30% of bug reports in a given month come from community-reported issues (vs. internal discovery)
• Community NPS ≥ 45 (quarterly survey)
• New member activation ≥ 40% — members who post at least once in their first 14 days