developer-marketing-playbook
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
ChineseDeveloper Marketing Playbook — DevRel, Docs & Community Funnels
开发者营销手册 — DevRel、文档与社区漏斗
📦 Install
📦 安装
bash
clawhub install developer-marketing-playbookWhat 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
bash
clawhub install developer-marketing-playbook安装后你将获得：
- 开发者社区建设手册（Discord/Slack/GitHub Discussions）
- 面向开发者受众的技术内容策略
- DevRel指标框架（认知 → 采用 → 拥护）
工程师不会对传统营销做出反应。以下是真正有效的方法：
- DevRel项目设计: 推动用户采用的角色、指标和活动
- 文档作为增长引擎: 优秀的文档如何成为你最佳的获客渠道
- API体验: 提升DX（开发者体验）以缩短首次API调用时间
- 社区漏斗: Discord/Slack → 贡献者 → 倡导者 → 客户转化路径
- 黑客松投资回报率: 黑客松的适用场景、举办方法以及效果衡量
Developer acquisition operating system
开发者获客操作系统
Stage 1 — reconstruct category history
阶段1 — 重构品类历史
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.
使用Wayback快照查看竞品的首个网站、测试版网站和首次重大发布版本。记录每个阶段的定位、页面深度、用例、导航/定价变化，以及SEO/社区投入的起始时间。这能避免将成熟竞品当前的渠道组合直接复制到从零到一的产品中。
Stage 2 — benchmark the best channel operator
阶段2 — 对标最佳渠道运营者
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不要将所有渠道都对标同一个竞品。针对网站/定位对标品类领导者，然后为每个渠道选择最强的运营者。追踪官方账号、创始人账号、DevRel账号和创作者账号；区分测试版节奏、发布周爆发期和稳定运营项目。
所需研究表格行：
品牌 | 渠道 | 日期 | 格式 | 品类 | URL | 内容框架 | 浏览量/互动量 | 营销活动归属 | 行动号召（CTA）Stage 3 — convert docs into adoption
阶段3 — 将文档转化为用户采用
Measure docs on , 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.
landing → quick start → first successful call/deploy → second session衡量文档的指标应基于“着陆页 → 快速入门 → 首次成功调用/部署 → 第二次使用”，而不仅仅是页面浏览量。每个发布包必须包含经过测试的快速入门指南、错误恢复方案、部署路径、参考文档、示例以及社区/支持下一步操作。
Stage 4 — ecosystem campaign
阶段4 — 生态系统营销活动
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.
对于企业/开源营销活动，协调README、对比文章、生态系统合作伙伴/赞助商、相关反向链接、社区帖子和DevRel跟进。将曝光量和星标数与激活开发者和合格账号分开统计。
Stage 5 — interview and iterate
阶段5 — 访谈与迭代
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.
与已激活和流失的开发者进行一对一访谈。请他们屏幕共享工作流程，找出第一个“惊喜时刻”，并展示他们已付费使用的产品。如果获客量上升但激活率低于目标，请暂停推广并修复产品/文档路径。
资料框架：为本次技能更新提供的Iris竞品研究维基和开源全球运营演示文稿。