---
name: devrel-practices
description: |
  Load when working on developer community engagement, technical advocacy,
  developer experience content, or community building. Contains best practices
  for Developer Relations (DevRel) and community management.
---

# Developer Relations (DevRel) Practices Skill

## Core Philosophy

Developer Relations builds authentic connections between developers and technology. The goal is mutual value creation:
- **For Developers**: Resources, community, growth opportunities
- **For Publication**: Engaged audience, feedback, advocacy

## The Four C's Framework

### 1. Code
Technical credibility is essential. DevRel must:
- Write working, quality code examples
- Understand developer pain points firsthand
- Contribute to open source
- Stay current with technology trends

### 2. Content
Create valuable technical content:
- Tutorials and how-to guides
- Documentation improvements
- Blog posts and articles
- Video tutorials and streams

### 3. Community
Build and nurture developer communities:
- Online communities (Discord, forums)
- Events (meetups, conferences)
- Ambassador programs
- User groups

### 4. Creative
Innovate in engagement approaches:
- New content formats
- Interactive experiences
- Hackathons and challenges
- Developer tools and utilities

## Community Building

### Understanding Developer Motivations
Developers join communities for:
- **Belonging**: Finding their tribe
- **Learning**: Solving problems, growing skills
- **Recognition**: Building reputation
- **Career**: Opportunities and networking
- **Fun**: Engaging with interesting tech

### Community Engagement Tactics

**Sustainable Engagement**
Focus on depth over constant presence:
```markdown
## Weekly Rhythm
- Monday: Share learning resource
- Wednesday: Answer community questions
- Friday: Highlight community member work

## Monthly Events
- Week 1: Office hours / AMA
- Week 2: Workshop or tutorial
- Week 3: Community showcase
- Week 4: Planning/feedback session
```

**Scaling Community Management**
```markdown
## Tier 1: Self-Service (80%)
- Comprehensive documentation
- FAQs and knowledge base
- Community-answered questions
- Searchable archives

## Tier 2: Community-Powered (15%)
- Peer-to-peer support
- Ambassador responses
- Community moderators
- User-generated content

## Tier 3: Direct Engagement (5%)
- Complex technical issues
- Strategic relationships
- High-value contributors
- Escalated concerns
```

### Discord Community Best Practices

**Channel Structure**
```
📢 announcements (read-only)
👋 introductions
💬 general
❓ help
   ├── python-help
   ├── data-viz-help
   └── ml-help
📚 resources
🎉 showcase
💡 ideas
🤝 jobs-networking (optional)
```

**Moderation Guidelines**
- Welcome new members promptly
- Set clear community rules
- Address issues privately first
- Celebrate positive contributions
- Remove bad actors quickly

## Technical Advocacy

### Writing for Developers

**Know Your Audience**
```markdown
## Audience Segments
- Beginners: Need fundamentals, no assumptions
- Intermediate: Want best practices, patterns
- Advanced: Seek optimization, edge cases
- Decision Makers: Care about business value
```

**Developer-First Content Principles**
1. **Start with the problem**: What pain does this solve?
2. **Show working code first**: Developers want to copy-paste
3. **Explain the why**: Not just how, but reasoning
4. **Be honest about trade-offs**: Trust through transparency
5. **Provide next steps**: Where to go deeper

### Technical Blog Posts

**Structure Template**
```markdown
# [Problem-Focused Title]

## TL;DR
[3-sentence summary with code snippet]

## The Problem
[Relatable scenario developers face]

## The Solution
[Clear explanation with code]

## Step-by-Step Implementation
[Detailed walkthrough]

## Going Further
[Advanced tips, alternatives, resources]

## Conclusion
[Key takeaways and call to action]
```

### Live Streaming & Video

**Stream Format**
```markdown
## Pre-Stream (10 min before)
- Test audio/video
- Set up code environment
- Have reference docs open

## Stream Structure
1. Hook (0-2 min): What we're building
2. Context (2-5 min): Why this matters
3. Setup (5-10 min): Prerequisites
4. Build (20-40 min): Main content
5. Q&A (5-10 min): Audience questions
6. Close (2 min): Summary and next steps
```

## Ambassador Programs

### Program Design
```markdown
## Tiers
1. **Contributors**: Occasional participation
   - Share content
   - Report bugs
   - Provide feedback

2. **Ambassadors**: Regular engagement
   - Create content
   - Speak at events
   - Mentor newcomers

3. **Champions**: Deep involvement
   - Lead initiatives
   - Strategic input
   - Public representation
```

### Ambassador Value Exchange
```markdown
## What Ambassadors Give
- Content creation
- Event speaking
- Community support
- Product feedback

## What Ambassadors Receive
- Early access / beta features
- Recognition and visibility
- Professional development
- Networking opportunities
- (Optional) Swag, compensation
```

### Avoiding Ambassador Burnout
- Set clear expectations upfront
- Recognize contributions publicly
- Provide support and resources
- Allow flexible participation
- Check in on wellbeing

## Measuring DevRel Impact

### Quantitative Metrics
```markdown
## Awareness
- Content views/reads
- Social reach
- SEO rankings
- Newsletter subscribers

## Engagement
- GitHub stars, forks
- Discord active members
- Event attendance
- Content completion rates

## Adoption
- New users/signups
- Tutorial completions
- API calls
- Project implementations
```

### Qualitative Indicators
- Community sentiment
- Developer testimonials
- Support request quality
- Ambassador retention
- Inbound opportunities

### Reporting Template
```markdown
# DevRel Monthly Report - [Month Year]

## Highlights
- [Top achievement 1]
- [Top achievement 2]
- [Top achievement 3]

## Content
| Type | Published | Views | Engagement |
|------|-----------|-------|------------|
| Blog posts | X | X | X% |
| Tutorials | X | X | X% |
| Videos | X | X | X% |

## Community
- Active members: X (+X% MoM)
- Questions answered: X
- Events held: X

## Looking Ahead
- [Next month priority 1]
- [Next month priority 2]
```

## Spanish-Speaking Developer Community

### Regional Considerations
- **Mexico**: Largest Spanish-speaking developer population
- **Argentina/Colombia**: Strong tech ecosystems
- **Spain**: Different timezone, European context
- **Remote/Global**: Growing remote work culture

### Content Localization
- Keep code in English (industry standard)
- Translate conceptual explanations
- Use local examples and references
- Consider timezone for live events

### Community Building in Spanish
- Lower barrier to entry for non-English speakers
- Address underserved content gaps
- Build bridges to English resources
- Create local leaders and ambassadors

## Resources

- [Developer Relations Activity Patterns](https://link.springer.com/book/9798868818943)
- [The DevRel Collective](https://www.thedevrelcollective.com/)
- [Developer Relations at GitLab](https://about.gitlab.com/blog/2024/03/13/developer-relations-at-gitlab-what-weve-learned-since-our-start/)
- [Common Room Community Guides](https://www.commonroom.io/resources/)