Promotion Plan: Make ClawWork the most popular OpenClaw client

## Goal

After launch prep (#6) is complete, execute a systematic promotion campaign to make ClawWork **the most popular open-source desktop client for OpenClaw**.

## Core Positioning

**"The dedicated UI for OpenClaw — stop chatting with Agents in Feishu."**

ClawWork is to OpenClaw what GitHub Desktop is to Git — a purpose-built native client that replaces the workaround of using generic messaging channels (Feishu/DingTalk/Slack).

### Key Differentiators vs Channels (Feishu, DingTalk, Slack)

| | Feishu / DingTalk / Slack | ClawWork |
|---|---|---|
| Layout | Single chat thread | Three-column: task list, conversation, progress panel |
| Multi-task | One conversation at a time | Parallel tasks in isolated sessions |
| Tool calls | Hidden or text-only | Real-time visualization with expandable details |
| Artifacts | Lost in chat history | Auto-saved to local Git repo, searchable |
| Progress | No structured tracking | Step-by-step progress panel |
| Data ownership | On third-party servers | 100% local (SQLite + Git) |

---

## Pre-launch Checklist (blocked by #6)

- [ ] 60-second demo GIF/video embedded in README
- [ ] Pre-built DMG available on GitHub Releases
- [ ] README rewritten with "Why ClawWork" comparison table (done, pending commit)
- [ ] `package.json` fields: `repository`, `homepage`, `license`
- [ ] GitHub repo Topics: `openclaw`, `desktop-client`, `electron`, `local-first`, `ai-agent`, `developer-tools`
- [ ] CHANGELOG.md for v0.1.0

---

## Phase 1: Launch Day (Day 1) — Concentrated Impact

Post on all high-leverage platforms on the **same day** to create a "seen everywhere" effect.

### English Platforms

- [ ] **Hacker News** — "Show HN: ClawWork – Open-source desktop client for OpenClaw (replaces Feishu/Slack channels)"
- Best time: Tue–Thu, 8–10 AM Pacific
- Be online to answer comments for 2–3 hours after posting
- [ ] **Reddit `r/selfhosted`** — "I built an open-source desktop client for OpenClaw that auto-versions all AI outputs to a local Git repo"
- [ ] **Reddit `r/opensource`** — same content, adapted for the sub
- [ ] **Reddit `r/LocalLLaMA`** — angle: "dedicated UI for self-hosted AI agents"
- [ ] **Twitter/X** — Thread with demo GIF, tag @OpenClaw, hashtags: #OpenClaw #LocalFirst #OpenSource #DevTools
- [ ] **OpenClaw Community** — official Discord/forum/discussions if available

### Chinese Platforms

- [ ] **V2EX `#share-creation`** — "ClawWork — A dedicated desktop client for OpenClaw. Stop chatting with Agents in Feishu."
- [ ] **Jike (`#indie-dev` / `#AI-products`)** — Short post + screenshot/GIF
- [ ] **OpenClaw WeChat groups** — Direct share
- [ ] **WeChat Official Account (Subscription)** — Publish a launch article, e.g. "Stop using Feishu to talk to Agents: ClawWork is a dedicated desktop client for OpenClaw"
- [ ] **WeChat tech communities** — Share in Electron, frontend dev, and AI Agent WeChat groups (attach demo GIF + GitHub link)
- [ ] **WeChat Moments** — Personal post with demo screenshot + one-liner

---

## Phase 1.5: Open-Source Ecosystem Integration (Week 1–2)

Embed ClawWork into the OpenClaw open-source ecosystem to gain official endorsement and long-term organic traffic.

### Merge into OpenClaw Official Documentation

- [ ] **Submit PR to OpenClaw docs repo** — Add ClawWork to "Desktop Clients" / "Community Tools" / "Getting Started" pages with install instructions and screenshots
- [ ] **Apply to become an OpenClaw recommended client** — Get listed in the "Ecosystem" section of OpenClaw README or website
- [ ] **Submit PR to OpenClaw awesome-list** — Ensure ClawWork is included in `awesome-openclaw` or similar curated lists

### Build Open-Source Community Influence

- [ ] **Be active in OpenClaw GitHub Discussions** — Answer questions, share ClawWork use cases, build developer trust
- [ ] **Contribute code/docs to OpenClaw itself** — Submit PRs (doc improvements, bug fixes, etc.) to establish contributor identity and increase project credibility
- [ ] **Reference ClawWork in relevant OpenClaw issues** — When users discuss desktop clients, UI experience, or similar needs, naturally recommend ClawWork
- [ ] **Reach out to OpenClaw maintainers** — Aim to be mentioned in OpenClaw release notes or newsletters

---

## Phase 2: Technical Depth (Week 2–4)

- [ ] **Juejin (juejin.cn)** — Technical article: "Building a dedicated OpenClaw desktop client with Electron + React 19"
- Focus on tech decisions and lessons learned (Tailwind v4 pitfalls, Zustand infinite loop, Gateway protocol reverse-engineering)
- [ ] **Zhihu Column** — Thought piece: "Why OpenClaw needs a dedicated desktop client"
- [ ] **Sspai (sspai.com)** — Product experience article: "A local-first AI workbench: the ClawWork experience"

---

## Phase 2.5: Chinese Community Deep Engagement (Week 2–4)

Sustain presence in Chinese developer and AI enthusiast communities.

### WeChat Ecosystem

- [ ] **WeChat Official Account article series** — Publish a series around ClawWork:
- "ClawWork architecture deep-dive: Electron + React 19 + local Git"
- "How I reverse-engineered the OpenClaw Gateway protocol"
- "Designing a local-first AI workbench"
- [ ] **WeChat Channels (video)** — Publish 1–2 min product demo short videos
- [ ] **Run a ClawWork WeChat user group** — Create a dedicated group to collect feedback, share updates, and nurture core users

### Other Chinese Platforms

- [ ] **Xiaohongshu (Little Red Book)** — Product experience posts targeting general tech audience (screenshots + impressions)
- [ ] **CSDN** — Technical blog posts, SEO coverage for keywords like "OpenClaw client"
- [ ] **OSChina (oschina.net)** — Register in open-source project directory + post updates
- [ ] **SegmentFault** — Technical Q&A + articles

---

## Phase 3: Sustained Growth (Month 2–3)

- [ ] **Product Hunt** — Launch when v0.2+ is ready (needs 5 high-quality screenshots + video + tagline)
- [ ] **Bilibili** — 3–5 min Chinese demo video
- [ ] **YouTube** — 3–5 min English demo video
- [ ] **Awesome lists** — Submit PR to `awesome-openclaw` or similar curated lists
- [ ] **Homebrew Cask** — `brew install --cask clawwork` for frictionless install

---

## Community Building (Ongoing)

- [ ] Reply to every GitHub issue within 24 hours
- [ ] Weekly changelog / progress update on Twitter + GitHub Discussions
- [ ] Collect user feedback and ship quick iterations
- [ ] Encourage contributions: label `good first issue` on beginner-friendly tasks
- [ ] If significant new feature ships (Windows support, plugin system), do another promotion round
- [ ] **Maintain WeChat user group** — Stay active, respond to questions promptly, share weekly dev progress
- [ ] **Ongoing OpenClaw ecosystem contributions** — Regularly submit PRs, participate in discussions, maintain active contributor status

---

## Metrics to Track

| Metric | Target (Month 1) |
|---|---|
| GitHub Stars | 500+ |
| GitHub Releases downloads | 200+ |
| GitHub Issues (from users) | 20+ |
| HN front page | Yes |
| Listed in OpenClaw official docs | Yes |
| WeChat user group members | 50+ |

---

## Promotional Copy Drafts

Draft posts for each platform are saved in `docs/promotion/`:
- `hacker-news.md` — Show HN post
- `v2ex.md` — V2EX post

Additional drafts to write:
- [ ] Reddit post template
- [ ] Twitter/X thread
- [ ] Jike post
- [ ] Juejin technical article outline
- [ ] Zhihu column article outline
- [ ] WeChat Official Account launch article
- [ ] OpenClaw docs PR content

---

## Out of Scope

- Paid advertising
- Landing page / official website (separate issue)
- Partnerships or sponsorships

## Depends On

- #6 (Launch Prep) — must be complete before posting anywhere