Back to Details

diff-marketing

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Diff marketing

Diff 营销

Generate content suggestions from recent code changes, commits, merged pull requests, and shipped features.
根据近期的代码变更、提交、已合并的 pull request 和已上线功能，生成内容建议。

Process

流程

  1. Analyze recent changes:
    • Look at the git log for the past week: 
      git log --since="1 week ago" --pretty=format:"%h - %s (%an, %ar)"
    • Check merged pull requests and their descriptions.
    • Review modified files and their purpose.
    • Identify new features, bug fixes, improvements, and refactors.
  2. Categorize changes by impact:
    • High impact: new features, major improvements, breaking changes.
    • Medium impact: enhancements, notable bug fixes, performance improvements.
    • Low impact: minor fixes, refactors, dependency updates.
  3. Read relevant files to understand the user-facing change before writing.
  4. Generate specific content suggestions with drafts, prioritizing user value, SEO opportunities, and useful distribution channels.
  1. 分析近期变更：
    • 查看过去一周的 Git log： 
      git log --since="1 week ago" --pretty=format:"%h - %s (%an, %ar)"
    • 检查已合并的 pull request 及其描述。
    • 审阅修改过的文件及其用途。
    • 识别新功能、bug 修复、改进和重构。
  2. 按影响程度对变更进行分类：
    • 高影响：新功能、重大改进、破坏性变更。
    • 中等影响：功能增强、值得关注的 bug 修复、性能改进。
    • 低影响：小型修复、重构、依赖项更新。
  3. 撰写前，阅读相关文件，以理解面向用户的变更。
  4. 生成附带草稿的具体内容建议，优先突出用户价值、 SEO 机会和实用的分发渠道。

Content suggestions by type

按类型划分的内容建议

Blog posts

博客文章

For high-impact changes:
  • Focus on features that solve user problems.
  • Include the problem, solution, benefits, screenshots or demos, and code examples when useful.
  • Use an educational, in-depth, SEO-optimized angle.
  • Aim for 800–2,000 words.
  • Possible angles:
    • "Introducing [Feature]: How We Built..."
    • "How [Feature] Helps You..."
    • "Behind the Scenes: Building [Feature]"
对于高影响变更：
  • 聚焦于能够解决用户问题的功能。
  • 视情况包括问题、解决方案、收益、截图或演示，以及代码示例。
  • 采用教育性、深入且经过 SEO 优化的角度。
  • 目标篇幅为 800–2,000 字。
  • 可选角度：
    • “推出 [Feature]：我们如何构建……”
    • “[Feature] 如何帮助你……”
    • “幕后解析：构建 [Feature]”

Tweets and social media

推文和社交媒体

Use all impact levels for:
  • Launch posts that explain the benefit and include a visual.
  • Threads that break down complex features.
  • Tip posts with a quick, useful takeaway.
  • Behind-the-scenes posts about decisions and tradeoffs.
Keep the tone conversational, concise, and specific. Include emojis, hashtags, mentions, links, and visuals when they add value. Treat a meaningful release as a launch opportunity and suggest a way to gather early feedback.
对于所有影响级别的变更：
  • 解释产品收益并附上视觉素材的发布帖。
  • 拆解复杂功能的推文串。
  • 提供快捷实用建议的干货帖。
  • 分享开发决策与取舍的幕后内容。
保持语气自然、简洁且具体。在确实能增强效果时，加入 emoji、 hashtag、mention、链接和视觉素材。将有意义的版本发布视为一次发布机会， 并建议一种收集早期反馈的方式。

Changelog updates

更新日志

  • Structure entries as 
    ## [Version] - [Date]
    .
  • Use Added, Changed, Fixed, Deprecated, Removed, and Security categories as applicable.
  • Write in user-facing language.
  • Link to documentation or blog posts for major features.
  • Keep the writing technical but accessible.
  • 条目结构为 
    ## [Version] - [Date]
    。
  • 根据实际情况使用 Added、Changed、Fixed、Deprecated、Removed 和 Security 分类。
  • 使用面向用户的语言。
  • 为主要功能链接到相关文档或博客文章。
  • 保持文字具有技术性，同时做到易于理解。

Email updates

邮件更新

For medium- and high-impact changes, suggest newsletters, feature announcements, or onboarding updates.
  • Include a hero image, brief introduction, feature highlights, and CTA when appropriate.
  • Use a personal, benefit-focused, actionable tone.
对于中等和高影响变更，建议 newsletter、功能公告或 onboarding 更新。
  • 视情况加入 hero image、简短引言、功能亮点和 CTA。
  • 使用个人化、聚焦收益且易于采取行动的语气。

Press releases

新闻稿

Suggest these only for major launches, milestones, partnerships, or funding. Include a headline, summary, quotes, boilerplate, and contact details. Use a professional, newsworthy, quotable tone.
仅针对重大版本发布、里程碑、合作伙伴关系或融资事件提出建议。 包括标题、摘要、引语、boilerplate 和联系信息。使用专业、 具有新闻价值且便于引用的语气。

Documentation

文档

Suggest updates to:
  • Getting-started guides.
  • Feature documentation.
  • API references.
  • Code examples and use cases.
  • Troubleshooting sections.
建议更新：
  • 入门指南。
  • 功能文档。
  • API 参考。
  • 代码示例和使用场景。
  • 故障排查章节。

Video content

视频内容

For high-impact changes, suggest demos, tutorial walkthroughs, release overviews, or development diaries.
对于高影响变更，建议制作 demo、教程 walkthrough、版本概览或开发日志。

Content strategy

内容策略

  1. Repurpose a blog post into a thread, newsletter, and documentation update.
  2. Coordinate content with the release.
  3. Lead with user benefits.
  4. Show the product with screenshots, GIFs, or videos.
  5. Include keywords, meta descriptions, and alt text where relevant.
  6. Give every piece a clear next step.
  7. Cross-link related content.
  8. Suggest how to collect feedback and measure response.
  1. 将一篇博客文章改编为推文串、newsletter 和文档更新。
  2. 让内容发布与版本发布相协调。
  3. 以用户收益为主线。
  4. 使用 screenshot、GIF 或 video 展示产品。
  5. 在相关位置加入 keywords、meta description 和 alt text。
  6. 为每份内容提供明确的下一步操作。
  7. 交叉链接相关内容。
  8. 建议如何收集反馈并衡量效果。

Output format

输出格式

Use this structure:
markdown
undefined
使用以下结构：
markdown
undefined

Week of [Date Range]

Week of [Date Range]

Summary

Summary

[High-level overview of what shipped]
[High-level overview of what shipped]

High impact changes

High impact changes

Medium impact changes

Medium impact changes

Low impact changes

Low impact changes

Content suggestions

Content suggestions

Blog posts

Blog posts

  1. "[Title]": [Brief description, key points, and target audience]
  2. "[Title]": [Brief description, key points, and target audience]
  1. "[Title]": [Brief description, key points, and target audience]
  2. "[Title]": [Brief description, key points, and target audience]

Tweets and threads

Tweets and threads

  1. Launch post: [Draft text with emojis when appropriate]
  2. Thread idea: [Topic and key points]
  3. Tip: [Quick value post]
  1. Launch post: [Draft text with emojis when appropriate]
  2. Thread idea: [Topic and key points]
  3. Tip: [Quick value post]

Changelog entry

Changelog entry

[Version] - [Date]

[Version] - [Date]

Added

Added

  • [Feature]: [User-facing description]
  • [Feature]: [User-facing description]

Fixed

Fixed

  • [Bug]: [What was fixed]
  • [Bug]: [What was fixed]

Email subject lines

Email subject lines

  • "[Compelling subject line option 1]"
  • "[Compelling subject line option 2]"
  • "[Compelling subject line option 1]"
  • "[Compelling subject line option 2]"

Video ideas

Video ideas

  • "[Video concept and key points to cover]"
  • "[Video concept and key points to cover]"

Documentation updates needed

Documentation updates needed

  • Update [doc page] with [new information]
  • Add [new guide] for [feature]
undefined
  • Update [doc page] with [new information]
  • Add [new guide] for [feature]
undefined

Writing standards

写作标准

  • Use customer-centric messaging.
  • Say what shipped and what it does. Do not invent metrics, customer results, or product behavior.
  • Use diff output and relevant source files to ground every claim.
  • Prefer plain language over hype.
  • Avoid generic launch copy, unsupported superlatives, and vague claims.
  • Use sentence-case headings and varied, natural prose.
  • Keep emojis functional and sparse.
  • End with the most useful next action for the reader.
  • 采用以客户为中心的表述方式。
  • 说明发布了什么及其作用。不要编造指标、客户结果或产品行为。
  • 每项陈述都应以 diff 输出和相关源文件为依据。
  • 优先使用平实语言，而非夸张宣传。
  • 避免通用发布文案、无依据的最高级表述和含糊其辞的说法。
  • 标题采用 sentence case，并使用自然多样的表达。
  • 保持 emoji 的功能性并克制使用。
  • 以对读者最有用的下一步操作结尾。