Community Building & Advocacy
Relevant source files
The following files were used as context for generating this wiki page:
Community Building and Advocacy represent the strategic effort to establish, grow, and manage technical communities while empowering individual developers to become vocal advocates for a product or project. This system focuses on creating "Hello World" moments, fostering engagement through structured platforms like Discord or Slack, and scaling impact via conference speaking, live coding, and contributor programs. Sources: skills/community-building/SKILL.md, skills/developer-advocacy/SKILL.md, skills/power-user-cultivation/SKILL.md
The framework operates on the principle that developers value transparency, technical accuracy, and community-led growth over traditional marketing. By identifying power users and providing them with insider access, direct engineering lines, and professional recognition, projects can transition from solo maintenance to community-sustained ecosystems. Sources: skills/power-user-cultivation/SKILL.md:27-32, skills/open-source-marketing/SKILL.md:144-150
Community Structure and Management
Building a thriveable developer community requires selecting the appropriate platform based on the audience's professional context and technical needs. Discord and Slack are primary real-time hubs, while GitHub Discussions serves as an integrated asynchronous alternative. Sources: skills/community-building/SKILL.md:28-44
Platform Selection Matrix
| Platform | Best For | Technical Advantage |
|---|---|---|
| Discord | Dev tools, OSS | Rich features, free, dev-native |
| Slack | Enterprise, B2B | Professional familiarity |
| GitHub Discussions | OSS | Integrated with code, searchable |
| Discourse | Long-form content | High SEO value, ownership |
Sources: skills/community-building/SKILL.md:28-36, skills/community-building/README.md:28-33
Logical Channel Architecture
Effective communities use a hierarchical channel structure to prevent information overload while maintaining support accessibility.
The diagram shows the flow from onboarding information to active engagement and technical support loops. Sources: skills/community-building/SKILL.md:50-80
The Contributor and Advocate Funnel
The project utilizes a multi-stage funnel to transition anonymous users into active maintainers or public advocates. This progression is managed through behavioral signals and specific recognition programs. Sources: skills/open-source-marketing/SKILL.md:144-146, skills/power-user-cultivation/SKILL.md:19-25
User Lifecycle Progression
- User/Star: Initial discovery and interest.
- Engaged User: Participates in community discussions and requests features.
- Advocate: Recommends the tool unprompted; candidate for ambassador programs.
- Champion: Creates content and answers technical queries for others.
- Contributor/Maintainer: Directly impacts codebases or documentation.
Sources: skills/power-user-cultivation/SKILL.md:19-25, skills/open-source-marketing/SKILL.md:144-146
Advocate Scoring Logic
Potential power users are identified via a weighted scoring system based on technical and social contributions.
| Action | Score Weight | Rationale |
|---|---|---|
| Created Content | +25 | High reach and SEO value |
| Top 10% Usage | +20 | Demonstrated product reliance |
| Answers Questions | +20 | Reduces support burden |
| Community Active | +15 | Fosters healthy environment |
| Social Mentions | +10 | Direct word-of-mouth |
Sources: skills/power-user-cultivation/SKILL.md:73-81
Developer Advocacy and Public Presence
Advocacy involves technical storytelling through conference talks, live coding, and podcasts. The goal is to move beyond simple product promotion to solving specific industry problems. Sources: skills/developer-advocacy/SKILL.md:15-20
Conference Talk Framework
Successful advocacy talks follow a formula: Specific Problem + Unique Angle + Clear Takeaways. Key talk types include:
- Lightning (5-10 min): Best for single concepts or quick demos.
- Standard (25-45 min): Technical deep-dives.
- Workshop (2-4 hours): Hands-on guided learning.
Sources: skills/developer-advocacy/SKILL.md:31-60
Live Demo Safety Protocols
Advocacy requires strict mitigation strategies for technical demonstrations to ensure trust and reliability.
This diagram illustrates the "10-3-1 Rule" (10 practices, 3 checkpoints, 1 backup) for technical demos. Sources: skills/developer-advocacy/SKILL.md:86-105
Community Health and Governance
Maintaining community health involves enforcing a Code of Conduct (CoC) and monitoring health metrics to prevent toxicity and burnout.
Moderation Playbook
| Situation | Standard Response | Escalation |
|---|---|---|
| Heated Debate | Move to off-topic/De-escalate | Temp Mute |
| Help Vampire | Provide "asking good questions" guide | Warning |
| Harassment | Immediate removal | Permanent Ban |
| Self-Promo Spam | Delete message | Warning/Ban |
Sources: skills/community-building/SKILL.md:209-222
Health KPI Thresholds
Communities are monitored against specific performance indicators to determine if intervention is required.
| Metric | Healthy | Warning |
|---|---|---|
| Support Response Time | <24 hours | >72 hours |
| Unanswered Questions | <10% | >25% |
| 7-Day Retention | >40% | <20% |
| Monthly Active Ratio | >20% | <10% |
Sources: skills/community-building/SKILL.md:255-260
Implementation of Power User Programs
To scale advocacy, projects implement formal Champion or Ambassador programs that provide high-value, non-monetary benefits to top developers. Sources: skills/power-user-cultivation/SKILL.md:104-125
Benefits Logic
Champions value professional growth and technical influence over generic marketing perks.
- Direct Access: Private Slack/Discord channels with the core engineering team.
- Early Access: Insider previews (e.g., 2-week head start on features).
- Professional Support: Conference ticket sponsorships and reference letters.
- Recognition: Public attribution in
CONTRIBUTORS.mdand website spotlights.
Sources: skills/power-user-cultivation/SKILL.md:118-142, skills/power-user-cultivation/SKILL.md:188-193
Summary
The Community Building & Advocacy system leverages the "Growth Equation," where growth is the product of real value, discoverability, and the first-use experience. By establishing structured community platforms, identifying power users through behavioral data, and supporting advocates in public technical speaking, the project builds a sustainable developer ecosystem. Success is measured not just by total members, but by support deflection, contributor retention, and the speed at which new members reach their first "Hello World" moment. Sources: skills/open-source-marketing/SKILL.md:35-37, skills/community-building/SKILL.md:255-260, skills/power-user-cultivation/SKILL.md:310-315