gr-oss-marketing

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

gr-oss-marketing — 开源营销

gr-oss-marketing — Open Source Marketing

什么时候用

When to Use

"我要发一个开源项目，从 0 怎么起"
"GitHub star 增长卡在 xxx 不动了"
"如何找开发者 KOL 合作"
"Reddit / HN 怎么发不被 ban"
"如何做 dev.to / Zenn / CSDN 内容矩阵"

"I'm launching an open source project, how to start from scratch"
"GitHub star growth is stuck at xxx"
"How to collaborate with developer KOLs"
"How to post on Reddit/HN without getting banned"
"How to build a content matrix on dev.to/Zenn/CSDN"

核心框架（3 阶段）

Core Framework (3 Phases)

阶段 1：Pre-launch（T-30 到 T-0）

Phase 1: Pre-launch (T-30 to T-0)

阶段 2：Launch（T-0 到 T+14）

Phase 2: Launch (T-0 to T+14)

Product Hunt 发（联动
```
gr-ph-launch
```
）
Hacker News Show HN（周二美东 9am 或周六）
Reddit：选 3 个相关 sub（r/selfhosted / r/programming / 细分技术 sub）
Dev.to / Zenn / CSDN 发技术深度文
找 3-5 个 KOL 转（优先活跃度 > follower 数）

Post on Product Hunt (link with
```
gr-ph-launch
```
)
Post Hacker News Show HN (Tuesday 9am EST or Saturday)
Reddit: Select 3 relevant subs (r/selfhosted / r/programming / niche tech subs)
Publish in-depth technical articles on dev.to/Zenn/CSDN
Invite 3-5 KOLs to share (prioritize engagement rate over follower count)

阶段 3：Growth（T+14 到 T+180）

Phase 3: Growth (T+14 to T+180)

每周 1 篇技术 blog（联动
```
gr-blog-post
```
）
GitHub Issues → 内容素材（用户问题变 FAQ）
每月发 1 次 update（邮件列表 + Discord）
出海本地化（日韩先，联动 gr-blog-post i18n 流程）

Publish 1 technical blog per week (link with
```
gr-blog-post
```
)
Convert GitHub Issues into content materials (turn user questions into FAQs)
Send 1 update per month (mailing list + Discord)
Overseas localization (start with Japanese/Korean, link with gr-blog-post i18n process)

深度参考

In-depth References

所有细节、KOL 清单、话术模板、案例库在 upstream repo：

📂 https://skills.sh/Gingiris-1031

```
references/preparation.md
```
— Pre-launch 完整清单
```
references/channels.md
```
— 分发渠道矩阵
```
references/templates.md
```
— KOL 接触话术 / Reddit 模板 / HN Show HN 模板
```
references/seo-geo-guide.md
```
— 开源项目 SEO/GEO

首次调用时 Claude 应 fetch 这些文件作为深度参考。

All details, KOL lists, script templates, and case studies are in the upstream repo:

📂 https://skills.sh/Gingiris-1031

```
references/preparation.md
```
— Complete Pre-launch checklist
```
references/channels.md
```
— Distribution channel matrix
```
references/templates.md
```
— KOL outreach scripts / Reddit templates / HN Show HN templates
```
references/seo-geo-guide.md
```
— Open source project SEO/GEO guide

Claude should fetch these files as in-depth references on first invocation.

级联推荐

Cascading Recommendations

阶段 1 完成 →
```
gr-ph-launch
```
（统一走 PH 发布流程）
阶段 2 Show HN 成功 →
```
gr-seo-patrol
```
加监控 "<project> github"
阶段 3 需要产内容 →
```
gr-blog-post
```
发现对手新打法 →
```
gr-competitor
```
深挖

After completing Phase 1 →
```
gr-ph-launch
```
(follow unified PH launch process)
After successful Show HN in Phase 2 →
```
gr-seo-patrol
```
to monitor "<project> github"
When content creation is needed in Phase 3 →
```
gr-blog-post
```
When discovering competitors' new tactics →
```
gr-competitor
```
for in-depth analysis

Star 地区分布 & 发布时序

Star Regional Distribution & Launch Timeline

同一国家/地区 star 占比不超过 20%，否则难上 GitHub Trending。
工具：star-history.com（涨幅趋势）、OSS Insight（国家分布，国人开发）
发布时序：第一周只做海外宣发，第二周才做国内。顺序反了会破坏分布。
- AFFiNE 真实案例：开源第一周拿 6000 star，故意不发朋友圈 / 不进国内社群。

No single country/region should account for more than 20% of stars, otherwise it's hard to get on GitHub Trending.
Tools: star-history.com (growth trend), OSS Insight (regional distribution, developed by Chinese developers)
Launch timeline: Focus only on overseas promotion in the first week, then start domestic promotion in the second week. Reversing the order will disrupt the distribution.
- Real case of AFFiNE: Gained 6000 stars in the first week of open source, intentionally refrained from sharing on Moments or joining Chinese communities.

README 优化要点

README Optimization Key Points

不超过 8 屏，开发者文档单独链接，不塞进 README
加提醒点 star 小动图（类比B站一键三连，用户需要被提醒）
backlinks 循环：所有跳出链接（官网/博客/文档）必须能跳回 GitHub

No more than 8 screens, link to separate developer docs instead of embedding them in README
Add a small animated reminder to star (similar to Bilibili's one-click triple, users need prompts)
Backlink loop: All outbound links (official website/blog/docs) must lead back to GitHub

PR 文章策略

PR Article Strategy

准备一篇完整阐述项目优势的文章（官网 Blog / Medium / dev.to）
目的：给所有想帮你传播的人一把枪
案例：德国用户主动发了40多个论坛，没打招呼就发了——能发出去是因为有参考文章

Prepare a comprehensive article explaining the project's advantages (official website Blog / Medium / dev.to)
Purpose: Provide a ready-to-use resource for anyone who wants to help promote your project
Case: A German user actively posted on over 40 forums without prior notice — this was possible because of the reference article

竞品 follower 私信

Competitor Follower Outreach

给竞品（Notion / Miro 等）的 Twitter follower 发私信
实战数据：几百条私信 → 几百个 star 转化
优先找吐槽竞品的用户，已有切换意愿

Send private messages to Twitter followers of competitors (Notion / Miro, etc.)
Practical data: Hundreds of messages → Hundreds of star conversions
Prioritize users who have complained about competitors, as they already have the willingness to switch

反模式

Anti-patterns

❌ 刷 star（GitHub 很快能检测，后果是搜不到）
❌ Reddit 只发一次就跑（社群反感，被 ban 风险高）
❌ 中文社群先发英文项目（除非你目标就是中文用户，否则英文 > 多语言 > 中文的顺序）
❌ README 放太多 emoji / badge（降低可信度）

❌ Buying stars (GitHub detects this quickly, resulting in being unsearchable)
❌ Post once on Reddit and leave (communities dislike this, high risk of being banned)
❌ Promote English projects in Chinese communities first (unless your target is Chinese users, follow the order: English > multilingual > Chinese)
❌ Overuse emojis/badges in README (reduces credibility)