developer-marketing-playbook Β· diff

git:20260706.f77d636 to git:20260814.b86ee95

28 added, 0 removed. Audit A to A.

---
name: developer-marketing-playbook
description: |
Complete developer marketing playbook covering DevRel programs, documentation as marketing, API developer experience, community building, and hackathon strategy. For dev-tool founders who need to reach engineers. Follow @WeiYipei on X.
source: https://github.com/Gingiris-1031/gingiris-skills/tree/main/skills/developer-marketing-playbook
tags:
- developer-marketing
- devrel
- developer-community
- documentation
- open-source
- developer
- api
- sdk
- developer-experience
- developer-relations
- claude-code
- ai-agent-skill
- hackathon
- dev-tool
- latest
---
# Developer Marketing Playbook β€” DevRel, Docs & Community Funnels
> 🌍 **Language / 语言**: [δΈ­ζ–‡](#δΈ­ζ–‡η‰ˆ) | [English](references/en/README.md) | [ζ—₯本θͺž](references/ja/README.md) | [ν•œκ΅­μ–΄](references/ko/README.md)
## πŸ“¦ Install
```bash
clawhub install developer-marketing-playbook
```
**What you get after installing:**
- Developer community building playbook (Discord/Slack/GitHub Discussions)
- Technical content strategy for developer audiences
- DevRel metrics framework (awareness β†’ adoption β†’ advocacy)
---
Engineers don't respond to traditional marketing. Here's what actually works.
- **DevRel program design**: Roles, metrics, and activities that drive adoption
- **Docs as growth engine**: How great documentation becomes your best acquisition channel
- **API experience**: DX improvements that reduce time-to-first-API-call
- **Community funnels**: Discord/Slack β†’ contributor β†’ champion β†’ customer pipeline
- **Hackathon ROI**: When hackathons work, how to run them, and measuring impact
+ ## Developer acquisition operating system
+
+ ### Stage 1 β€” reconstruct category history
+
+ Use Wayback snapshots for the competitor's first site, beta site and first major launch. For each stage record positioning, page depth, use cases, navigation/pricing changes, and when SEO/community investment began. This prevents copying a mature competitor's current channel mix into a zero-to-one product.
+
+ ### Stage 2 β€” benchmark the best channel operator
+
+ Do not benchmark every channel against the same competitor. Use the category leader for site/positioning, then select the strongest operator per channel. Track official, founder, DevRel and creator accounts; separate beta cadence, launch-week bursts and steady-state programs.
+
+ Required research row:
+
+ `brand | channel | date | format | category | URL | content framework | views/engagement | campaign membership | CTA`
+
+ ### Stage 3 β€” convert docs into adoption
+
+ Measure docs on `landing β†’ quick start β†’ first successful call/deploy β†’ second session`, not pageviews alone. Every launch packet must include a tested quick start, error recovery, deploy path, reference docs, examples and a community/support next step.
+
+ ### Stage 4 β€” ecosystem campaign
+
+ For an enterprise/open-source campaign, coordinate README, comparison article, ecosystem partners/sponsors, relevant backlinks, community posts and DevRel follow-up. Report impressions and stars separately from activated developers and qualified accounts.
+
+ ### Stage 5 β€” interview and iterate
+
+ Run 1:1 interviews with activated and bounced developers. Ask them to screen-share the workflow, identify the first "aha", and show what they already pay for. If acquisition rises but activation stays below target, pause distribution and fix the product/docs path.
+
+ Source framework: Iris competitor-research wiki and open-source global-operations deck supplied for this skill update.
+
## Related Gingiris Skills
- Full version: https://clawhub.ai/gingiris-1031/skills/gingiris-opensource
- All skills: https://clawhub.ai/gingiris-1031
- Follow: [@WeiYipei on X](https://x.com/WeiYipei)