Back to Details

write

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Write — Founder Voice Content

撰写——创始人视角内容

Sound like a real person sharing hard-won lessons, not a marketing department.
要像一个分享来之不易经验的真实人物，而非营销部门的口吻。

Voice Rules

语气规则

  1. First person, always. "I built" not "We implemented."
  2. Specific over general. "37 tools across 9 domains" not "many tools."
  3. Show the mess. The failed draft, the 3am realization, the thing you'd do differently.
  4. One idea per piece. If you can't tweet the core insight in one sentence, refocus.
  5. End with value. Reader leaves with something they can use today.
  1. 始终使用第一人称。用“我打造了”而非“我们实施了”。
  2. 具体而非笼统。用“9个领域的37款工具”而非“许多工具”。
  3. 展现不完美。失败的草稿、凌晨3点的顿悟、你会做出改变的事。
  4. 每篇内容聚焦一个观点。如果核心观点无法用一条推文讲清楚，就重新聚焦。
  5. 以价值收尾。让读者能带走可以立即使用的内容。

X/Twitter Thread Format

X/Twitter推文线程格式

Tweet 1 (Hook):  Bold claim or surprising result. Stop the scroll.
                 Max 280 chars. No hashtags. No "thread incoming."

Tweet 2-3:       Context. Why this matters. What problem you were solving.

Tweet 4-7:       The meat. What you did, what happened, what you learned.
                 Numbers, screenshots, code snippets.
                 Each tweet stands alone AND flows in sequence.

Tweet 8-9:       Counterintuitive insight. What most people get wrong.

Final tweet:     One-sentence takeaway they'll screenshot.
                 Optional: link to blog for depth.
Tweet 1 (Hook):  Bold claim or surprising result. Stop the scroll.
                 Max 280 chars. No hashtags. No "thread incoming."

Tweet 2-3:       Context. Why this matters. What problem you were solving.

Tweet 4-7:       The meat. What you did, what happened, what you learned.
                 Numbers, screenshots, code snippets.
                 Each tweet stands alone AND flows in sequence.

Tweet 8-9:       Counterintuitive insight. What most people get wrong.

Final tweet:     One-sentence takeaway they'll screenshot.
                 Optional: link to blog for depth.

Blog Post Structure

博客文章结构

  1. Hook — The result or surprise (not backstory)
  2. Problem — What you were up against
  3. Journey — What you tried (including what failed)
  4. Solution — What worked and why
  5. Lessons — What you'd tell someone starting today
  1. 钩子——直接给出结果或惊喜（而非背景故事）
  2. 问题——你当时面临的困境
  3. 历程——你尝试过的方法（包括失败的尝试）
  4. 解决方案——有效的方法及其原因
  5. 经验教训——你想告诉新手的建议

What Makes Content Share-worthy

让内容值得分享的要素

  • Contrarian + evidence: "Everyone says X, but here's what happened when I tried Y"
  • Specific numbers: revenue, users, time saved
  • Vulnerability + competence: admit mistakes while showing mastery
  • Actionable: templates, frameworks, step-by-step
  • 反常识+证据：“大家都说X，但我尝试Y时发生了这样的事”
  • 具体数据：收入、用户数、节省的时间
  • 真诚+专业：承认错误的同时展现专业性
  • 可落地：模板、框架、分步指南

Anti-Patterns

反模式

  • Throat-clearing ("In today's fast-paced world...")
  • Hashtag spam
  • Humble-bragging
  • Generic advice anyone could give
  • Corporate voice ("We're excited to announce...")
  • 冗长铺垫（“在当今快节奏的世界里……”）
  • 滥用话题标签
  • 谦虚式炫耀
  • 任何人都能给出的通用建议
  • 官方口吻（“我们很高兴宣布……”）