{
  "schemaVersion": "0.2",
  "generatedAt": "2026-08-13T18:19:52.845Z",
  "provider": "DeepSeek API / deepseek-v4-pro",
  "note": "Generated from the local DSH Promotion Toolkit baseline, then source-checked for demo use.",
  "platforms": [
    "x",
    "xiaohongshu",
    "zhihu",
    "wechat",
    "wechat_moments",
    "weibo",
    "bilibili",
    "douyin",
    "kuaishou",
    "linkedin",
    "threads",
    "reddit",
    "tiktok",
    "youtube",
    "medium",
    "facebook",
    "instagram"
  ],
  "cases": [
    {
      "id": "product-launch",
      "label": "Product launch story",
      "labelZh": "产品发布长文",
      "sourceUrl": "https://github.com/lhmd/dsh-promotion-toolkit",
      "source": "我们做了一款面向独立创作者的长文宣发工具。最初的产品说明有十几个段落，里面混着用户场景、功能边界、为什么不做自动编造，以及使用记录。我们没有把它压缩成一条万能文案，而是先抽取可验证的观点、证据和反例，再按平台重写：知乎展开方法论和取舍，小红书整理成可保存清单，公众号保留完整叙事，朋友圈写成像朋友分享，视频平台转成分镜和口播。测试时最明显的变化不是发布数量，而是每次打开草稿箱都知道下一步该写什么。这个工具的目标不是让每个平台说同一句话，而是让同一个真实故事拥有更多进入读者视线的入口。",
      "baseline": {
        "language": "zh",
        "score": 70,
        "signals": [
          "tension",
          "clear topic",
          "quotable length"
        ],
        "evidence": [
          "测试时最明显的变化不是发布数量，而是每次打开草稿箱都知道下一步该写什么。",
          "这个工具的目标不是让每个平台说同一句话，而是让同一个真实故事拥有更多进入读者视线的入口。",
          "我们没有把它压缩成一条万能文案，而是先抽取可验证的观点、证据和反例，再按平台重写：知乎展开方法论和取舍，小红书整理成可保存清单，公众号保留完整叙事，朋友圈写成像朋友分享，视频平台转成分镜和口播。"
        ],
        "platformCount": 17
      },
      "polished": {
        "zh": {
          "tagline": "同一个真实故事，多平台入口",
          "coreIdea": "面向独立创作者的长文宣发工具：先把长文中的可验证观点、证据和反例抽出来，再按平台重写。目标不是让每个平台说同一句话，而是让同一个真实故事拥有更多进入读者视线的入口。实际使用最明显的变化：每次打开草稿箱都知道下一步该写什么。",
          "titles": [
            "长文宣发别再一键群发：我们如何让同一个故事在各平台长成不同样子",
            "打开草稿箱就知道下一步写什么：长文宣发工具的“分平台重写”实测",
            "不做万能文案，只做多入口：一次长文宣发的30天记录"
          ],
          "hook": "测试时最明显的变化不是发布数量，而是每次打开草稿箱都知道下一步该写什么。",
          "quote": "这个工具的目标不是让每个平台说同一句话，而是让同一个真实故事拥有更多进入读者视线的入口。",
          "platforms": {
            "x": "我们做了一款面向独立创作者的长文宣发工具。测试最明显的变化不是发得更多，而是每次打开草稿箱都知道下一步写什么。不靠一键群发，而是先抽可验证观点，再按平台重写。同一个真实故事，多几个进入读者视线的入口。仓库：https://github.com/lhmd/dsh-promotion-toolkit",
            "xiaohongshu": "📝 独立创作者长文宣发：别再把同一段话复制到所有平台了\n😩 痛点：写完长文后，打开各个平台草稿箱，完全不知道改写什么、怎么开头。\n💡 我们的方法：不压缩成万能文案，而是先抽取可验证的观点、证据和反例，再按平台重写。\n✅ 可保存清单：\n1️⃣ 知乎：展开方法论和取舍，适合深度讨论\n2️⃣ 小红书：整理成可保存的清单，直接收藏\n3️⃣ 公众号：保留完整叙事，让读者读完整个故事\n4️⃣ 朋友圈：写成像朋友分享，一句话就能看懂\n5️⃣ 视频平台：转成分镜和口播，照着拍就行\n🔗 工具仓库：https://github.com/lhmd/dsh-promotion-toolkit\n#独立创作者 #长文宣发 #内容运营 #多平台分发 #真实故事",
            "zhihu": "# 长文宣发工具为什么要“分平台重写”而不是一键群发\n\n## 结论\n我们做了一款面向独立创作者的长文宣发工具。在使用过程中，最明显的变化不是发布数量增加，而是每次打开草稿箱时，都清楚下一步该写什么。工具的目标不是让每个平台说同一句话，而是让同一个真实故事拥有更多进入读者视线的入口。\n\n## 背景\n最初的产品说明有十几个段落，混合了用户场景、功能边界、为什么不做自动编造，以及使用记录。我们没有把这些内容压缩成一条万能文案，因为那会丢失平台语境和读者预期。独立创作者面对的问题是：内容真实、有限，但需要出现在不同平台上，并且每个平台需要不同的表达方式。\n\n## 方法\n我们先从原始说明中抽取可验证的观点、证据和反例。然后按平台重写：\n- 知乎：展开方法论和取舍，适合讨论“为什么这么做”以及边界；\n- 小红书：整理成可保存的清单，方便快速参考；\n- 公众号：保留完整叙事，让读者看到完整过程；\n- 朋友圈：写成像朋友分享，缩短到一句自然的话；\n- 视频平台：转成分镜和口播，直接用于拍摄脚本。\n\n这样做避免了“一条文案复制所有平台”造成的表达错位。测试中，最直接的效果是写作者不再面对空白草稿箱犹豫，因为每个平台的内容框架已经提前确定。\n\n## 限制\n该工具目前主要解决写作者从长文到多平台草稿的转换，不承诺自动生成爆款，也不制造不存在的案例或数据。使用记录只是一段时间的个人经验，未必适用于所有创作者或所有内容类型。更多细节与代码见：https://github.com/lhmd/dsh-promotion-toolkit",
            "wechat": "标题：长文宣发工具：不是让每个平台说同一句话，而是让同一个故事找到更多入口\n\n导语：对独立创作者来说，写完一篇长文只是开始，更难的是把同一个故事拆到不同平台，同时不变成复制粘贴。我们做了一个工具，实际使用后，发现关键变化不是发布数量，而是每次打开草稿箱都知道下一步该写什么。\n\n一、为什么不做万能文案\n最初的产品说明有十几个段落，混着用户场景、功能边界和使用记录。如果压缩成一条，很多信息会丢。我们选择先抽可验证的观点、证据和反例。\n\n二、按平台重写，而不是按平台复制\n知乎展开方法论和取舍；小红书整理成可保存清单；公众号保留完整叙事；朋友圈写成像朋友分享；视频平台转成分镜和口播。\n\n三、使用过程中最明显的变化\n不是发布数量，而是打开草稿箱知道下一步写什么。这听起来很小，但解决了创作者最消耗心力的“空白页焦虑”。\n\n结尾：工具的目标不是制造统一口径，而是给同一个真实故事更多入口。完整说明与代码：https://github.com/lhmd/dsh-promotion-toolkit",
            "wechat_moments": "做了一个长文宣发工具，实际使用，最明显的变化不是发得更多，而是打开草稿箱就知道下一步写什么。不复制粘贴，按平台重写真实故事。仓库：https://github.com/lhmd/dsh-promotion-toolkit 😊",
            "weibo": "独立创作者的长文宣发，别再一键群发了。我们做了一款工具：先抽可验证的观点，再按平台重写，知乎讲方法论，小红书做清单，公众号留叙事，视频转分镜。实际使用，最明显的变化是每次打开草稿箱都知道下一步写什么。🔗 https://github.com/lhmd/dsh-promotion-toolkit",
            "bilibili": "【镜头1 0:00-0:05】特写草稿箱界面，光标闪烁\n旁白：打开草稿箱，却不知道下一步写什么？很多独立创作者卡在这里。\n字幕：长文宣发，卡在第一步\n\n【镜头2 0:05-0:15】屏幕切换：十几个段落的产品说明\n旁白：我们最初写了一堆长文说明，里面混着用户场景、功能边界和使用记录。\n字幕：不是内容不够，是入口不对\n\n【镜头3 0:15-0:30】分屏展示不同平台重写结果：知乎方法论、小红书清单、公众号长文\n旁白：我们没把它压缩成一条万能文案，而是先抽证据，再按平台重写。\n字幕：同一个故事，不同入口\n\n【镜头4 0:30-0:45】日历翻页，显示实际使用\n旁白：使用下来，最明显的变化不是发布数量，而是每次打开草稿箱都知道下一步写什么。\n字幕：目标不是发更多，是心里有数\n\n【镜头5 0:45-0:55】工具界面展示仓库地址\n旁白：完整工具和代码在 GitHub，链接放在简介。\n字幕：🔗 https://github.com/lhmd/dsh-promotion-toolkit\n\nCTA：想看我们怎么拆解？点个关注，下次更新方法。",
            "douyin": "【0-3s】镜头：创作者盯着电脑，草稿箱空\n旁白：你知道吗？长文宣发最大的坑，不是写不好，是不知道下一步写什么。\n字幕：空白草稿箱\n\n【3-8s】镜头：快速展示产品说明十几段\n旁白：我们做了一款工具，先把可验证的观点、证据、反例抽出来。\n字幕：先拆真信息\n\n【8-15s】镜头：平台图标切换，知乎/小红书/公众号/朋友圈/视频\n旁白：然后按平台重写，不是复制粘贴。\n字幕：小红书清单，知乎方法论，视频分镜\n\n【15-22s】镜头：记录结果，打勾草稿箱\n旁白：实际使用，最明显的变化不是发更多，而是每次都知道写什么。\n字幕：目标：真实故事多入口\n\n【22-25s】镜头：二维码/网址\n旁白：完整工具在 GitHub，链接看评论区。\n字幕：https://github.com/lhmd/dsh-promotion-toolkit\n\nCTA：关注我，下次拆解更多创作流程。",
            "kuaishou": "【0:00-0:04】镜头：手机录屏草稿箱\n旁白：老铁们，做长视频/文章的朋友，是不是总卡在打开草稿箱不知道写啥？\n字幕：草稿箱恐惧症\n\n【0:04-0:10】镜头：翻出十几段产品说明\n旁白：我们做了个工具，把长文说明拆成证据、观点、反例。\n字幕：拆开真东西\n\n【0:10-0:18】镜头：平台图标一个个亮起\n旁白：然后按平台重写，知乎讲方法，小红书给清单，视频直接出分镜。\n字幕：一个故事多入口\n\n【0:18-0:25】镜头：一段时间打卡记录\n旁白：使用后，最明显变化不是发得多，而是打开草稿箱知道该写啥。\n字幕：不复制，只重写\n\n【0:25-0:30】镜头：网址\n旁白：工具代码放 GitHub 了，链接在评论区。\n字幕：https://github.com/lhmd/dsh-promotion-toolkit\n\nCTA：觉得有用点个赞，下次继续唠。",
            "linkedin": "我们做了一款面向独立创作者的长文宣发工具。与一键群发不同，它先从长文说明中抽取可验证的观点、证据和反例，再按平台重写：知乎展开方法论，小红书整理成可保存清单，公众号保留完整叙事，朋友圈写成像朋友分享，视频平台转成分镜和口播。实际使用最明显的变化不是发布数量，而是每次打开草稿箱都知道下一步该写什么。工具的目标不是让每个平台说同一句话，而是让同一个真实故事拥有更多进入读者视线的入口。完整说明与代码：https://github.com/lhmd/dsh-promotion-toolkit",
            "threads": "独立创作者长文宣发，不要再一键群发了。我们做了一款工具：先抽可验证观点，再按平台重写。实际使用，最明显的变化是打开草稿箱就知道下一步写什么。同一个真实故事，多几个入口。链接：https://github.com/lhmd/dsh-promotion-toolkit",
            "reddit": "我做了一款面向独立创作者的长文宣发工具，想听听大家的看法。\n问题：写完长文后，面对不同平台，你们是直接复制粘贴，还是重新改写？我们试了一个方法：先抽取可验证的观点、证据和反例，再按平台重写（知乎方法、小红书清单、公众号叙事、朋友圈短句、视频分镜）。使用下来，最明显的变化不是发布数量，而是打开草稿箱时知道下一步该写什么。这个方法有局限：不生成虚构案例，也不保证爆款。工具代码在 GitHub，感兴趣可以看看，也欢迎提 issue 讨论多平台内容拆解的更好方式。https://github.com/lhmd/dsh-promotion-toolkit",
            "tiktok": "【0:00-0:03】镜头：快速切换各种草稿箱界面\n旁白：打开草稿箱，脑子一片空白？\n字幕：卡稿日常\n\n【0:03-0:08】镜头：长文说明滚动\n旁白：我们做了一款工具，把长文拆成证据和观点。\n字幕：不制造，只拆解\n\n【0:08-0:15】镜头：平台重写演示\n旁白：知乎写方法，小红书做清单，视频出分镜。\n字幕：按平台重写\n\n【0:15-0:20】镜头：记录结果\n旁白：使用后，最明显的变化不是发更多，而是打开草稿箱就知道写什么。\n字幕：目标：真实故事多入口\n\n【0:20-0:24】镜头：网址\n旁白：完整代码在 GitHub，链接放简介。\n字幕：https://github.com/lhmd/dsh-promotion-toolkit\n\nCTA：关注我看更多创作工具。",
            "youtube": "【0:00-0:10】镜头：黑屏白字“长文宣发为什么难？”\n旁白：独立创作者写完一篇长文，真正的挑战才刚刚开始：怎么把同一个故事放到不同平台，而不是变成复制粘贴？\n字幕：长文宣发，多平台难题\n\n【0:10-0:25】镜头：展示十几段原始说明文档\n旁白：我们最初的说明有十几个段落，混着用户场景、功能边界和使用记录。直接压缩成一条文案，信息会丢，平台读者也不买账。\n字幕：不要万能文案\n\n【0:25-0:45】镜头：动画展示抽取证据、观点、反例\n旁白：所以我们先抽取可验证的观点、证据和反例，然后按平台重写。\n字幕：先拆真信息\n\n【0:45-1:05】镜头：分屏展示知乎、小红书、公众号、朋友圈、视频脚本\n旁白：知乎展开方法论和取舍，小红书整理成可保存清单，公众号保留完整叙事，朋友圈写成像朋友分享，视频平台转成分镜和口播。\n字幕：同一个故事，多入口\n\n【1:05-1:25】镜头：实际使用记录，草稿箱逐渐填满\n旁白：测试一段时间，最明显的变化不是发布数量，而是每次打开草稿箱都知道下一步该写什么。这解决了创作者最消耗心力的空白页焦虑。\n字幕：目标不是发更多，是心里有数\n\n【1:25-1:40】镜头：工具界面和 GitHub 页面\n旁白：工具代码和完整说明放在 GitHub，链接在简介和评论区。想看我们怎么把一条长文拆成多平台草稿吗？点个关注，我们下期继续。\n字幕：🔗 https://github.com/lhmd/dsh-promotion-toolkit\n\nCTA：点赞、评论、订阅，下次更新多平台内容工作流。",
            "medium": "标题：从长文到多平台：我们如何解决“打开草稿箱不知道写什么”\n\n导语：独立创作者常常把时间花在“发布”上，但真正消耗心力的是面对空白草稿箱时的犹豫。我们做了一款工具，用一段时间测试了一种不同的做法：不把内容压缩成一条文案，而是先抽取可验证的信息，再按平台重写。\n\n## 为什么一条万能文案不够\n万能文案会丢掉平台语境，读者看到的是同一段话，而不是适合他们的表达。\n\n## 我们的拆解方法：先证据后表达\n先抽取可验证的观点、证据和反例，然后知乎展开方法，小红书做清单，公众号保留叙事，朋友圈写短句，视频出分镜。\n\n## 使用过程中最明显的变化\n不是发布数量变多，而是每次打开草稿箱都知道下一步该写什么。\n\n## 局限与下一步\n不自动生成爆款，不编造案例；下一步会继续优化不同平台的内容框架。\n\n结尾：工具代码和详细说明：https://github.com/lhmd/dsh-promotion-toolkit",
            "facebook": "我们做了一款面向独立创作者的长文宣发工具。不搞一键群发，先抽取可验证观点、证据和反例，再按平台重写：知乎方法、小红书清单、公众号叙事、朋友圈短句、视频分镜。实际使用最明显的变化：打开草稿箱就知道下一步写什么。目标不是让每个平台说同一句话，而是让同一个真实故事拥有更多入口。🔗 https://github.com/lhmd/dsh-promotion-toolkit",
            "instagram": "📌 独立创作者长文宣发：不要一键群发，要分平台重写\n😫 痛点：写完长文后，面对不同平台，不知道改写什么、怎么开头。\n💡 我们的方法：先抽可验证的观点、证据和反例，再按平台重写。\n✅ 可保存清单：\n1️⃣ 知乎：展开方法论和取舍\n2️⃣ 小红书：整理成可保存清单\n3️⃣ 公众号：保留完整叙事\n4️⃣ 朋友圈：写成像朋友分享\n5️⃣ 视频：转成分镜和口播\n🔗 工具仓库：https://github.com/lhmd/dsh-promotion-toolkit\n#独立创作者 #长文宣发 #内容运营 #多平台 #真实故事"
          },
          "hashtags": [
            "独立创作者",
            "长文宣发",
            "内容运营",
            "多平台分发",
            "真实故事"
          ],
          "imagePrompt": "一张分屏插画：左侧是一份长文档，右侧分裂出多个平台入口（知乎、小红书、公众号、朋友圈、视频），草稿箱里逐渐填满清晰的下一步提示，风格克制、现代、无品牌标志。"
        },
        "en": {
          "tagline": "One true story, many platform entries",
          "coreIdea": "A long-form promotion tool for independent creators that extracts verifiable points, evidence, and counterexamples, then rewrites them per platform. The goal is not one message everywhere, but many entry points for the same true story. The clearest result in a while of testing: opening the draft box and knowing exactly what to write next.",
          "titles": [
            "Don't Copy-Paste Your Long-Form Story: Rewrite It for Every Platform",
            "The Draft Box Problem: How a Repurposing Tool Made Next Steps Obvious",
            "One True Story, Many Entries: a while with a Creator Promotion Tool"
          ],
          "hook": "The clearest change after testing wasn't more posts. It was opening the draft box and knowing exactly what to write next.",
          "quote": "The goal isn't to make every platform say the same sentence; it's to give the same true story more ways into a reader's attention.",
          "platforms": {
            "x": "We built a long-form promo tool for independent creators. after using it, the biggest change wasn't posting more—it was opening the draft box and knowing exactly what to write next. No one-size copy. Extract verifiable points first, then rewrite per platform. Same true story, more entries. Repo: https://github.com/lhmd/dsh-promotion-toolkit",
            "xiaohongshu": "📝 Long-form promo for independent creators: stop pasting the same text everywhere.\n😩 Pain point: after finishing a long piece, you open each platform and don't know what to rewrite or how to start.\n💡 Our approach: don't shrink it into universal copy. Extract verifiable points, evidence, and counterexamples, then rewrite per platform.\n✅ Save this checklist:\n1️⃣ Zhihu: expand methodology and trade-offs\n2️⃣ Xiaohongshu: turn it into a saveable list\n3️⃣ WeChat articles: keep the full narrative\n4️⃣ Moments: write like a friend\n5️⃣ Video: turn it into storyboard and voiceover\n🔗 Toolkit repo: https://github.com/lhmd/dsh-promotion-toolkit\n#creator #contentrepurposing #longform #multiplatform #true story",
            "zhihu": "# Why a Long-Form Promotion Tool Rewrites Per Platform Instead of Sending One Copy Everywhere\n\n## Conclusion\nWe built a long-form promotion tool for independent creators. In a test, the clearest change was not an increase in posts, but knowing exactly what to write next every time we opened the draft box. The tool's goal is not to make every platform say the same sentence, but to give the same true story more entry points into a reader's attention.\n\n## Background\nThe original product description had more than ten paragraphs mixing user scenarios, feature boundaries, why it does not auto-fabricate, and using it record. We did not compress this into a single piece of copy, because that would lose platform context and reader expectations. Independent creators face a specific problem: their content is real and finite, but it must appear on different platforms, and each platform needs a different expression.\n\n## Method\nWe first extracted verifiable viewpoints, evidence, and counterexamples from the source material. Then we rewrote per platform:\n- Zhihu: expand methodology and trade-offs;\n- Xiaohongshu: organize as a saveable checklist;\n- WeChat articles: keep the full narrative;\n- WeChat Moments: write like a friend;\n- Video platforms: turn into storyboard and voiceover.\n\nThis avoids the misalignment caused by copying one piece across all platforms. In testing, the most direct effect was that writers no longer faced a blank draft box, because each platform's content frame had already been decided.\n\n## Limits\nThe tool currently mainly solves the transition from long-form content to multi-platform drafts. It does not promise viral results, and it does not fabricate cases or data. The usage record is a period of time of personal use and may not apply to every creator or content type. More details and code: https://github.com/lhmd/dsh-promotion-toolkit",
            "wechat": "Title: Not One Message Everywhere: How a Repurposing Tool Gives a True Story More Entries\n\nLead: For independent creators, finishing a long piece is only the beginning. The harder part is turning the same story into posts for different platforms without turning it into copy-paste. We built a tool, and after testing, found that the clearest change wasn't more posts—it was opening the draft box and knowing exactly what to write next.\n\nSection 1: Why we don't make universal copy\nThe original description had more than ten paragraphs. It mixed user scenarios, feature boundaries, and using it record. If we compressed it into one post, too much would be lost.\n\nSection 2: Rewrite per platform, not copy per platform\nWe extract verifiable viewpoints, evidence, and counterexamples first, then rewrite: Zhihu gets methodology, Xiaohongshu gets a checklist, WeChat articles keep the full narrative, Moments get a friend-style short note, video platforms get storyboards and voiceover.\n\nSection 3: The most obvious change after using it\nNot the number of posts. It's that every time we open the draft box, we know the next step. That sounds small, but it removes the blank-page anxiety that drains creators.\n\nEnding: The goal is not to enforce one message across platforms, but to give the same true story more entry points. Full documentation and code: https://github.com/lhmd/dsh-promotion-toolkit",
            "wechat_moments": "Built a long-form promo tool for creators. after using it, the biggest change wasn't posting more—it was opening the draft box and knowing the next step. Repo: https://github.com/lhmd/dsh-promotion-toolkit 🙌",
            "weibo": "For independent creators: stop copy-pasting long-form posts across platforms. We built a tool that extracts verifiable points, then rewrites per platform—Zhihu methodology, Xiaohongshu checklist, WeChat narrative, video storyboard. after using it, the clearest change was knowing the next step in every draft. 🔗 https://github.com/lhmd/dsh-promotion-toolkit",
            "bilibili": "[0:00-0:05] Close-up of an empty draft box, cursor blinking\nVO: Open the draft box and don't know what to write next? That's where many creators get stuck.\nCaption: Stuck at the draft\n\n[0:05-0:15] Screen shows a long document with many paragraphs\nVO: We started with a long description mixing user scenarios, feature limits, and using it record.\nCaption: One long source, many mixed parts\n\n[0:15-0:30] Split screen: platform rewrites\nVO: Instead of compressing it into one piece, we extract verifiable points and rewrite per platform.\nCaption: Same story, different entries\n\n[0:30-0:45] Calendar flips through a while\nVO: after using it, the biggest change wasn't more posts—it was knowing what to write next every time we opened the draft.\nCaption: Clarity over volume\n\n[0:45-0:55] Tool interface and repo URL\nVO: Full toolkit and code on GitHub, link in description.\nCaption: 🔗 https://github.com/lhmd/dsh-promotion-toolkit\n\nCTA: Want the full breakdown? Subscribe for the next update.",
            "douyin": "[0-3s] Creator staring at empty draft box\nVO: The biggest trap in long-form promo? Not writing badly—it's not knowing what to write next.\nCaption: Blank draft anxiety\n\n[3-8s] Long description scrolling\nVO: We built a tool that extracts verifiable points, evidence, and counterexamples first.\nCaption: Extract real info\n\n[8-15s] Platform icons switching: Zhihu, Xiaohongshu, WeChat, video\nVO: Then rewrite per platform—no copy-paste.\nCaption: Checklist, methodology, storyboard\n\n[15-22s] Month of checkmarks on drafts\nVO: after using it, the clearest change wasn't more posts; it was knowing what to write every time.\nCaption: More entries for the same story\n\n[22-25s] URL\nVO: Full code on GitHub, link in comments.\nCaption: https://github.com/lhmd/dsh-promotion-toolkit\n\nCTA: Follow for more creator workflows.",
            "kuaishou": "[0:00-0:04] Phone screen showing draft box\nVO: Creators, do you ever open the draft box and have no idea what to write?\nCaption: Draft box fear\n\n[0:04-0:10] Long source doc\nVO: We made a tool that breaks a long description into evidence, viewpoints, and counterexamples.\nCaption: Break it down\n\n[0:10-0:18] Platform icons light up\nVO: Then rewrite per platform—Zhihu gets method, Xiaohongshu gets checklist, video gets storyboard.\nCaption: One story, many doors\n\n[0:18-0:25] Month of records\nVO: after using it, the biggest change wasn't more posts—it was knowing exactly what to write when opening drafts.\nCaption: No copy-paste\n\n[0:25-0:30] URL\nVO: Code is on GitHub, link in comments.\nCaption: https://github.com/lhmd/dsh-promotion-toolkit\n\nCTA: Give it a like if this helped, more next time.",
            "linkedin": "We built a long-form promotion tool for independent creators. Instead of one-click distribution, it first extracts verifiable viewpoints, evidence, and counterexamples from the source, then rewrites for each platform: Zhihu expands methodology and trade-offs, Xiaohongshu becomes a saveable checklist, WeChat articles keep the full narrative, Moments sound like a friend, and video platforms get storyboards and voiceover. After using it, the clearest change wasn't more posts—it was opening the draft box and knowing exactly what to write next. The goal is not one identical message on every platform, but more entry points for the same true story. Full documentation and code: https://github.com/lhmd/dsh-promotion-toolkit",
            "threads": "Independent creators: stop copy-pasting long-form posts across platforms. We built a tool that extracts verifiable points, then rewrites per platform. after using it, the clearest change was knowing the next step every time we opened a draft. Same true story, more entries. Link: https://github.com/lhmd/dsh-promotion-toolkit",
            "reddit": "I built a long-form promotion tool for independent creators and want to hear your take.\nProblem: after writing a long piece, do you copy-paste across platforms or rewrite? We tried a method: extract verifiable viewpoints, evidence, and counterexamples, then rewrite per platform (Zhihu methodology, Xiaohongshu checklist, WeChat narrative, short friend-style notes, video storyboards). after using it, the clearest change wasn't more posts—it was opening the draft box and knowing what to write next. Limits: no fabricated cases, no guarantee of virality. Code on GitHub if you want to look, and I'd welcome discussion on better ways to break down multi-platform content. https://github.com/lhmd/dsh-promotion-toolkit",
            "tiktok": "[0:00-0:03] Rapid cuts of empty draft boxes\nVO: Open the draft box and your mind goes blank?\nCaption: Creator's block\n\n[0:03-0:08] Long description scrolling\nVO: We built a tool that turns a long source into evidence and viewpoints.\nCaption: Extract, don't invent\n\n[0:08-0:15] Platform rewrite demo\nVO: Zhihu gets method, Xiaohongshu gets checklist, video gets storyboard.\nCaption: Rewrite per platform\n\n[0:15-0:20] Month record\nVO: after using it, the clearest change wasn't more posts—it was knowing what to write the moment you open a draft.\nCaption: Same story, more entries\n\n[0:20-0:24] URL\nVO: Full code on GitHub, link in bio.\nCaption: https://github.com/lhmd/dsh-promotion-toolkit\n\nCTA: Follow for more creator tools.",
            "youtube": "[0:00-0:10] Black screen with text \"Why is long-form promo hard?\"\nVO: For independent creators, finishing a long piece is just the start. The real challenge is turning the same story into posts for different platforms without copy-paste.\nCaption: Multi-platform challenge\n\n[0:10-0:25] Show original long document\nVO: Our original description had more than ten paragraphs mixing user scenarios, feature boundaries, and using it record. Compressing it into one post would lose too much context.\nCaption: No universal copy\n\n[0:25-0:45] Animation of extracting points, evidence, counterexamples\nVO: So we first extract verifiable viewpoints, evidence, and counterexamples, then rewrite per platform.\nCaption: Extract real info\n\n[0:45-1:05] Split screen showing Zhihu, Xiaohongshu, WeChat, Moments, video scripts\nVO: Zhihu expands methodology and trade-offs, Xiaohongshu becomes a saveable checklist, WeChat articles keep the full narrative, Moments write like a friend, video platforms get storyboards and voiceover.\nCaption: One story, many entries\n\n[1:05-1:25] Usage record, draft boxes filling up\nVO: after using it, the clearest change wasn't more posts—it was opening the draft box and knowing exactly what to write next. That removes the blank-page anxiety that drains creators.\nCaption: Clarity over volume\n\n[1:25-1:40] Tool UI and GitHub page\nVO: Full code and docs are on GitHub, link in description. Want to see how we break a long source into multi-platform drafts? Subscribe for the next update.\nCaption: 🔗 https://github.com/lhmd/dsh-promotion-toolkit\n\nCTA: Like, comment, subscribe for more creator workflows.",
            "medium": "Title: How to Turn One Long-Form Story into Many Platform Entries (Without Copy-Paste)\n\nLead: Independent creators often waste energy facing a blank draft box, not publishing. We built a tool and ran a test around a simple idea: don't make one piece of copy for all platforms. Extract verifiable information first, then rewrite per platform.\n\n## The problem with universal copy\nOne message for every platform loses context. A Zhihu reader wants reasoning; a Xiaohongshu reader wants a saveable list; a video viewer wants a storyboard. One text cannot serve all.\n\n## Our method: evidence first, expression second\nWe extract verifiable viewpoints, evidence, and counterexamples from the long source. Then we rewrite: Zhihu gets methodology, Xiaohongshu gets checklist, WeChat gets narrative, Moments gets friend-style short note, video gets storyboard and voiceover.\n\n## What changed after using it\nThe clearest change wasn't more posts. It was that every time we opened the draft box, we knew the next step. That removed the blank-page anxiety that stops creators before they start.\n\n## Limits and next steps\nThe tool does not fabricate cases or data, and it does not promise virality. Next steps include refining platform-specific frameworks and testing with more creators.\n\nEnding: Full documentation and code: https://github.com/lhmd/dsh-promotion-toolkit",
            "facebook": "We built a long-form promo tool for independent creators. No one-click copy-paste. It extracts verifiable viewpoints, evidence, and counterexamples, then rewrites per platform—Zhihu method, Xiaohongshu checklist, WeChat narrative, Moments short note, video storyboard. after using it, the clearest change was opening the draft box and knowing the next step. Goal: not one message everywhere, but more entry points for the same true story. 🔗 https://github.com/lhmd/dsh-promotion-toolkit",
            "instagram": "📌 Long-form promo for creators: stop pasting the same text everywhere.\n😫 Pain point: after finishing a long piece, you open each platform and don't know what to rewrite or how to start.\n💡 Our approach: don't shrink it into universal copy. Extract verifiable points, evidence, and counterexamples, then rewrite per platform.\n✅ Save this checklist:\n1️⃣ Zhihu: expand methodology and trade-offs\n2️⃣ Xiaohongshu: turn it into a saveable list\n3️⃣ WeChat articles: keep the full narrative\n4️⃣ Moments: write like a friend\n5️⃣ Video: turn it into storyboard and voiceover\n🔗 Toolkit repo: https://github.com/lhmd/dsh-promotion-toolkit\n#creator #contentrepurposing #longform #multiplatform #true story"
          },
          "hashtags": [
            "creator",
            "contentrepurposing",
            "longform",
            "multiplatform",
            "true story"
          ],
          "imagePrompt": "A split-screen illustration: on the left a long manuscript, on the right it branches into multiple platform entry points (Zhihu, Xiaohongshu, WeChat, Moments, video), a draft box filling with clear next-step notes, restrained modern style, no brand logos."
        }
      }
    },
    {
      "id": "indie-builder",
      "label": "Indie builder log",
      "labelZh": "独立开发者日志",
      "source": "I stopped adding features for a week and rebuilt my tiny SaaS onboarding flow around one question: what should a new user accomplish in the first five minutes? The result was not a bigger dashboard. It was a shorter path from the first click to a useful result, with fewer choices and a clear next action. I documented the trade-offs, the screens I removed, the questions that remained, and the signs I will watch before deciding whether the change worked.",
      "baseline": {
        "language": "en",
        "score": 72,
        "signals": [
          "tension",
          "conversation",
          "clear topic"
        ],
        "evidence": [
          "I stopped adding features for a week and rebuilt my tiny SaaS onboarding flow around one question: what should a new user accomplish in the first five minutes?",
          "It was a shorter path from the first click to a useful result, with fewer choices and a clear next action.",
          "I documented the trade-offs, the screens I removed, the questions that remained, and the signs I will watch before deciding whether the change worked."
        ],
        "platformCount": 17
      },
      "polished": {
        "zh": {
          "tagline": "把“更多功能”换成“更快到达第一个有用结果”",
          "coreIdea": "停一周新功能，围绕“新用户前五分钟应该完成什么”重构 onboarding，砍掉多余选择，缩短到最短有用路径，并记录取舍与验证信号。",
          "titles": [
            "我停了一周新功能，只问了一个问题，SaaS 激活路径反而短了",
            "从仪表盘到最短路径：重构 onboarding 的取舍清单",
            "新用户前 5 分钟：决定 SaaS 成败的关键问题"
          ],
          "hook": "当你停止加功能，开始问“新用户前五分钟要什么”，你会发现很多屏幕只是噪音。",
          "quote": "新用户在前五分钟应该完成什么？",
          "platforms": {
            "x": "停了一周新功能，只问一个问题：“新用户前五分钟该完成什么？”结果是更短的路径、更少的选择、明确的下一步。我记录了取舍、删掉的屏幕、留下的问题，以及之后观察哪些信号。不追求大而全，先让用户尝到第一个有用结果。 #SaaS #Onboarding",
            "xiaohongshu": "标题：我停了一周新功能，把 SaaS 激活路径改短了｜5分钟原则\n\n痛点：你是不是也总在加功能，却没人真正用起来？新用户一进来就被仪表盘淹没，不知道该点哪。\n\n我做了这件事：围绕“新用户前5分钟该完成什么”重构 onboarding，删掉多余屏幕，只留一条最短路径和一个明确下一步。\n\n✅ 可保存清单（我的做法）：\n1. 写下用户第一分钟、第三分钟、第五分钟应该达到什么状态\n2. 删除所有不直接服务于这个目标的页面和按钮\n3. 把欢迎流程压缩到最少步骤，每个步骤只留一个主行动\n4. 记录被删掉的功能、留下的问题、以及未来要观察的信号（激活率、完成率、流失点）\n5. 先小范围上线，看数据再决定是否继续砍\n\n结果不是更大的仪表盘，而是从第一次点击到有用结果的更短距离。\n\n📌 先别急着加功能，先帮用户赢一次。\n\n#SaaS #产品设计 #用户激活 #onboarding #精益创业 #独立开发者",
            "zhihu": "# 如何用“前五分钟目标”重构 SaaS 的 onboarding 流程？\n\n## 结论\n停止添加功能，转而回答“新用户在前五分钟内应该完成什么”，可以显著缩短从首次点击到有用结果的路径。我通过删减冗余屏幕、压缩选择、明确下一步，把 onboarding 从展示产品的仪表盘变成了引导用户达成首个小胜利的流程。这个改变不是更大的仪表盘，而是更短的距离。目前仍需观察激活率、完成率和流失点的变化来判断是否真正有效。\n\n## 背景\n我的产品是一个小型 SaaS。在过去一段时间里，我们不断添加新功能，但新用户的激活情况并没有随之改善。面对不断膨胀的仪表盘，用户往往不知所措。我决定停一周开发新功能，把精力集中在 onboarding 的重构上，核心问题是：一个新用户在前五分钟里到底应该完成什么？这个问题的答案决定了我们该保留什么、删除什么，以及如何在早期给用户一个明确的“我做到了”的时刻。\n\n## 方法\n1. 定义五分钟内的成功状态：用户在第一、三、五分钟分别应该看到什么、理解什么、完成什么动作。例如，第一分钟完成注册并看到核心价值；第三分钟创建第一个项目或导入数据；第五分钟看到第一个可用的结果。\n2. 映射现有 onboarding 流程：找出所有屏幕、按钮、弹窗，标注它们是否直接服务于上述成功状态。\n3. 删除不直接相关的元素：包括多余的欢迎页、功能导览、不必要的设置步骤和次要 CTA。我移除了几个描述性屏幕和高级选项，只保留一条主线。\n4. 压缩步骤并强化主行动：将原来多步骤的引导压缩到最少，每个屏幕只保留一个主要操作，并用明确的下一步按钮引导。\n5. 记录取舍和遗留问题：哪些功能入口被牺牲、哪些用户教育被延后、哪些问题尚未解决（比如高级用户可能需要更多引导）。同时列出未来要观察的信号：激活率、首次关键行为完成率、流程中途退出点、以及用户反馈。\n6. 小范围上线并观察：先让部分新用户进入新版流程，对比数据变化，再决定是否全面切换。\n\n## 限制\n这个改变是基于我个人的产品场景和有限的用户反馈，样本量小，尚未经过长期验证。不同产品、不同用户群体的“前五分钟成功”定义可能完全不同。此外，删除功能入口可能影响某些老用户或高级需求，需要在后续迭代中补充分层引导。目前只能把它看作一次有依据的实验，而非放之四海皆准的方法。",
            "wechat": "标题：我停了一周新功能，把 SaaS 激活路径改短了：关于 onboarding 的一次重构实验\n\n导语：当产品开始堆积功能，新用户反而更迷茫。我决定停下手头的新功能开发，用一周时间只做一件事：把 onboarding 流程重新设计，回答一个关键问题——新用户在前五分钟内应该完成什么？结果不是更大的仪表盘，而是一条更短、更清晰的路。这篇文章记录了我的取舍、删掉的屏幕、留下的问题，以及我会观察哪些信号来判断这次改变是否成功。\n\n一、从“加功能”到“问问题”\n我的产品是一个小型 SaaS，过去一段时间我们一直在添加新功能，但新用户激活率并没有明显提升。用户注册后面对一个复杂的仪表盘，不知道该点哪里，很多人用完免费阶段就流失了。我意识到，问题可能不在于功能不够多，而在于用户没有在第一时间感受到价值。于是我停了一周新功能开发，把精力全部放在 onboarding 上，核心问题是：一个新用户在前五分钟内应该完成什么？\n\n二、定义五分钟的成功路径\n要回答这个问题，必须先明确用户在早期阶段要完成的关键动作。我把前五分钟拆成三个时间点：第一分钟，用户应该完成注册/登录并看到产品的核心价值主张；第三分钟，用户应该创建第一个项目或导入数据，开始接触产品的核心功能；第五分钟，用户应该看到第一个可用的结果，哪怕是一个简单的输出或预览。有了这个框架，我就可以对照现有流程进行删减。\n\n三、删掉什么？留下什么？\n我回顾了 onboarding 流程中的每一个屏幕和按钮，问自己：它是否直接帮助用户达到上述任一成功状态？如果不是，就删除或者延后。结果，我删掉了两个描述性欢迎页、一个功能介绍弹窗、一个高级设置步骤，还把原本五步的引导压缩到了三步。每个屏幕只保留一个主要 CTA，比如“创建项目”或“导入数据”，其他次要选项全部折叠进“稍后再说”。路径变得更短，用户的选择更少，但每一步都更明确。\n\n四、取舍与遗留问题\n删除并不是没有代价的。一些功能入口被藏得更深，可能会影响那些本来就会主动探索的高级用户；同时，一些教育性的内容（比如功能亮点）被推迟到用户完成首个关键动作之后。我记录下这些取舍，并保留了一个“问题清单”：如果用户需要更多引导怎么办？如果高级用户找不到入口怎么办？这些都需要在后续迭代中通过分层 onboarding 或上下文提示来解决。\n\n五、接下来观察哪些信号？\n我不会马上宣布这次改版成功。我需要观察几个关键指标：新用户激活率是否提升；从注册到首次关键行为的完成率是否提高；流程中途的退出点是否减少；以及用户是否有明确的正面反馈或抱怨。我会在小范围内先运行新流程，对比旧版数据，再决定是否全面切换。\n\n结尾：这次实验让我重新理解了 onboarding 的本质：不是展示产品有多强大，而是帮助用户在最短时间内完成一次有意义的任务。先让用户赢一次，比任何功能介绍都重要。至于这次改变是否真的有效，数据会给我答案。",
            "wechat_moments": "停了一周新功能，只问了一个问题：新用户前五分钟该完成什么？结果是更短的路径和更少的按钮。先帮用户赢一次，比加功能重要。🧭",
            "weibo": "我停了一周新功能，把 onboarding 重新设计了一遍，只围绕一个问题：“新用户在前五分钟应该完成什么？”结果不是更大的仪表盘，而是更短的路径、更少的选择、更明确的下一步。我记录了取舍、删掉的屏幕、留下的问题，以及之后要观察哪些信号。先让用户尝到第一个有用结果，再谈功能。 #SaaS #产品设计",
            "bilibili": "[镜头1 - 0:00-0:15]\n画面：开发者对着电脑屏幕，屏幕上显示复杂的仪表盘，然后手绘一个问号。\n配音：“我停了一周新功能，只因为问了自己一个问题：新用户前五分钟应该完成什么？”\n字幕：“停一周，只问一个问题”\n表情符号：🤔\n\n[镜头2 - 0:15-0:45]\n画面：屏幕录制，展示旧 onboarding 流程，多个欢迎页和弹窗，然后被一一划掉。\n配音：“原来的流程里，用户要经过五六个屏幕，到处都是按钮。我删掉了两个欢迎页、一个弹窗，把步骤压缩到三步，每个屏幕只留一个主行动。”\n字幕：“删掉多余的，留下必要的”\n表情符号：✂️\n\n[镜头3 - 0:45-1:15]\n画面：新流程演示，用户点击一个按钮，很快看到第一个有用结果。\n配音：“现在，用户从第一次点击到看到第一个结果，路径短了很多。不再是展示产品有多少功能，而是帮用户完成一次有意义的任务。”\n字幕：“先让用户赢一次”\n表情符号：✅\n\n[镜头4 - 1:15-1:45]\n画面：开发者记录文档，展示取舍清单和观察指标。\n配音：“我记录了所有取舍：哪些功能入口被牺牲、哪些问题还没解决，以及未来要观察的激活率、完成率和退出点。数据会告诉我这次改版是否真的有效。”\n字幕：“不止改版，还要验证”\n表情符号：📊\n\n[镜头5 - 1:45-2:00]\n画面：结束画面，大字：先帮用户赢，再谈功能。\n配音：“如果你也在做 SaaS，不妨停下来问问：你的新用户在前五分钟完成了什么？”\n字幕：“关注我，看后续数据”\nCTA：“评论区聊聊你的 onboarding 经验”\n表情符号：👉",
            "douyin": "[0:00-0:05] 画面：手机屏幕特写，点击注册按钮。配音：“停了一周新功能，我只问一个问题” 字幕：停一周，问一个问题\n[0:05-0:15] 画面：旧界面多个弹窗，快速划掉。配音：“新用户前五分钟该完成什么？不是看仪表盘，是拿到第一个有用结果。” 字幕：不是大而全，是快而准\n[0:15-0:25] 画面：新流程三步演示，点击一个按钮出结果。配音：“删掉多余屏幕，压缩到三步，每屏只有一个主行动。” 字幕：短路径，少选择，明确下一步\n[0:25-0:35] 画面：数据图表和笔记。配音：“我记录了取舍和要观察的激活率、完成率。数据会说话。” 字幕：验证再决定\n[0:35-0:45] 结束画面：大字“先帮用户赢一次”。配音：“你的新用户前五分钟完成了什么？评论区聊聊。” CTA：关注+评论",
            "kuaishou": "[开场] 画面：我坐在电脑前，转头对镜头。配音：“我把我家 SaaS 的 onboarding 重新做了一遍，就靠一个问题。” 字幕：一个问题改流程\n[过程] 画面：屏幕录制，删除页面。配音：“新用户前五分钟得完成啥？我列了三个时间点，第一分钟注册，第三分钟建项目，第五分钟看到结果。然后把不相关的全删了。” 字幕：第一、三、五分钟\n[结果] 画面：新流程操作。配音：“现在从点击到有用结果，路径短多了，按钮也少了。” 字幕：更快到达有用结果\n[结尾] 画面：笔记特写。配音：“我记了取舍和信号，激活率、完成率啥的。先跑小范围，看数据再决定。” 字幕：数据验证\n[CTA] 画面：大字“先让用户赢一次”。配音：“你的产品前五分钟啥样？评论区见。”",
            "linkedin": "我最近做了一次小实验：停了一周新功能开发，把 SaaS 的 onboarding 流程彻底重构，只围绕一个问题——新用户在前五分钟内应该完成什么？结果是更短的路径、更少的选择、更明确的下一步。我删除了几个不直接服务于早期成功的屏幕，把引导压缩到三步，并记录了取舍和待观察的激活信号。这次经历让我重新理解 onboarding：不是展示产品，而是帮助用户快速获得第一个有用结果。你的产品“前五分钟”定义是什么？欢迎交流。 #SaaS #ProductManagement #UserOnboarding",
            "threads": "停了一周新功能，只问：“新用户前五分钟该完成什么？”答案不是更大仪表盘，而是更短路径、更少选择、明确下一步。删掉多余屏幕，记录取舍和信号。先让用户赢一次。 #SaaS #Onboarding",
            "reddit": "标题：我停了一周新功能，把 SaaS onboarding 重构了，只围绕一个问题\n\n正文：我的产品是个小型 SaaS，之前一直加功能但激活率没改善。上周我停掉新功能开发，重新设计 onboarding，只问：新用户在前五分钟应该完成什么？我删了两个欢迎页、一个弹窗，压缩到三步，每屏一个主按钮。结果是路径更短，选择更少，下一步更明确。我记录了取舍和要观察的激活率、完成率、退出点。还没数据，所以不知道是否成功。有人做过类似实验吗？你们定义的“前五分钟成功”是什么？",
            "tiktok": "[0:00-0:05] Visual: phone screen with signup. Voiceover: \"I stopped shipping features for a week and rebuilt my SaaS onboarding.\" Caption: \"One question changed everything 🔍\"\n[0:05-0:15] Visual: messy dashboard being crossed out. Voiceover: \"The question: what should a new user accomplish in the first 5 minutes?\" Caption: \"Not a bigger dashboard, a shorter path\"\n[0:15-0:25] Visual: new flow with one button. Voiceover: \" I cut screens, reduced choices, and made one clear next action.\" Caption: \"Fewer choices, faster win ⚡\"\n[0:25-0:35] Visual: notes and metrics. Voiceover: \"Documented trade-offs, removed screens, and signals to watch: activation, completion, drop-off.\" Caption: \"Let data decide 📊\"\n[0:35-0:45] End screen: \"Help users win in 5 minutes.\" Voiceover: \"What does your new user accomplish in 5 minutes? Comment below.\" CTA: Follow for part 2",
            "youtube": "[0:00-0:30] 开场\n画面：开发者面对镜头，背景是工作台，屏幕显示产品界面。\n配音：“大家好，今天聊聊我最近做的一个实验。我停了一周新功能开发，把整个 onboarding 流程重新设计了一遍，围绕一个问题：新用户在前五分钟内应该完成什么？”\n字幕：“停一周，重构 onboarding”\n表情符号：🎬\n\n[0:30-2:00] 背景与问题\n画面：屏幕录制，展示旧版 onboarding，多个页面和弹窗，用户点击混乱。\n配音：“以前我们总在加功能，仪表盘越来越复杂，但新用户激活没提升。用户进来不知道点哪，很快就流失了。我意识到，问题不是功能不够，而是用户没在第一时间感受到价值。”\n字幕：“功能多≠激活好”\n表情符号：📉\n\n[2:00-3:30] 定义五分钟成功\n画面：白板动画，列出第一、三、五分钟的目标。\n配音：“我把前五分钟拆成三个节点：第一分钟完成注册并看到核心价值；第三分钟创建第一个项目或导入数据；第五分钟看到第一个可用的结果。这个框架帮我判断每个屏幕该不该留。”\n字幕：“第一分钟注册，第三分钟建项目，第五分钟出结果”\n表情符号：⏱️\n\n[3:30-5:00] 删减与重构\n画面：屏幕录制，演示删除流程，旧页面被划掉，新流程逐步出现。\n配音：“然后我开始删：两个欢迎页、一个功能介绍弹窗、一个高级设置步骤。原来五步压缩到三步，每屏只留一个主按钮。路径短了，选择少了，但每一步更明确。”\n字幕：“删掉噪音，保留主线”\n表情符号：✂️\n\n[5:00-6:30] 取舍与遗留问题\n画面：展示笔记文档，列出取舍清单和问题。\n配音：“删除有代价：功能入口变深，教育内容延后。我记录了这些问题，比如高级用户找不到入口怎么办，需要后续分层引导。同时列出要观察的信号：激活率、完成率、退出点。”\n字幕：“有取舍，也有待解问题”\n表情符号：📝\n\n[6:30-8:00] 验证计划与结尾\n画面：回到开发者面对镜头，身后屏幕显示数据图表。\n配音：“现在新版在小范围测试，我不会马上说成功。数据会告诉我是否真的有效。但有一点我很确定：onboarding 的核心是帮用户完成一次有意义的任务，而不是展示产品有多强大。先让用户赢一次，比任何功能介绍都重要。”\n字幕：“先帮用户赢一次”\n表情符号：🏁\nCTA：“如果你也在做类似实验，欢迎在评论区分享你的‘前五分钟’定义。别忘了点赞订阅，后续我会更新数据结果。”",
            "medium": "标题：重构 SaaS onboarding：我问了一个问题，然后删掉了半个流程\n\n导语：在产品世界里，我们习惯用加法解决问题：用户不活跃？加功能。转化率低？加引导。但有时候，减法才是答案。我停了一周新功能，把 onboarding 流程重新设计，只为了回答一个问题：新用户在前五分钟内应该完成什么？下面是我的完整记录。\n\n一、问题的诞生\n我的产品是一个小型 SaaS，用户注册后面对的是一个功能越来越多的仪表盘。我们总在添加新东西，但激活率始终不温不火。直到某天我停下来问自己：如果一个新用户只给我五分钟，我该让他体验到什么？这个问题的答案将决定整个 onboarding 的设计。\n\n二、定义“成功”的三分钟节点\n我把前五分钟拆成三个具体的时刻：第一分钟，完成注册并看到产品的核心价值——不是欢迎语，而是能立刻理解的“这个工具能帮我做什么”。第三分钟，创建第一个项目或导入数据，开始真正的使用。第五分钟，看到第一个可用的结果，哪怕只是一个预览或简单输出。这三个节点成了我的过滤器。\n\n三、用过滤器删除噪音\n我把现有 onboarding 流程的每个屏幕、按钮、弹窗都过了一遍：它是否直接帮助用户到达这三个节点之一？如果不是，就删除或延后。最终我删掉了两个描述性欢迎页、一个功能介绍弹窗、一个高级设置步骤，并把原来的五步压缩为三步。每个屏幕只保留一个主要行动，其他选项全部收进“稍后再说”。\n\n四、取舍与遗留问题\n删除不是没有代价。一些功能入口被隐藏得更深，教育用户的内容被推迟。我列了一个清单：如果用户需要更多引导怎么办？高级用户找不到入口怎么办？这些都需要在之后通过分层 onboarding 或上下文提示解决。同时，我记录了未来要观察的信号：激活率、首次关键行为完成率、流程退出点、以及用户反馈。\n\n五、先小范围验证\n我不会马上宣布这次改版成功。我会在新用户中先随机分出一部分使用新版流程，对比数据后再决定是否全面切换。我的判断是：onboarding 的目标不是展示产品，而是帮助用户完成一次有意义的任务。先让用户赢一次，再谈其他。\n\n结尾：这次实验还在进行中，但我已经学到一件事：少即是多，尤其是在用户还没建立起使用习惯的时候。你的产品“前五分钟”是什么？欢迎分享。",
            "facebook": "停了一周新功能，把 tiny SaaS 的 onboarding 重新设计，只围绕一个问题：“新用户在前五分钟应该完成什么？”结果不是更大的仪表盘，而是更短的路径、更少的选择、更明确的下一步。我删除了几个不直接服务早期成功的屏幕，记录了取舍和要观察的信号（激活率、完成率、退出点）。先让用户尝到第一个有用结果，比堆功能更重要。你的产品前五分钟体验如何？ #SaaS #Onboarding #ProductDesign",
            "instagram": "标题：停一周新功能，重新设计 onboarding，只为回答一个问题\n\n痛点：新用户进来不知道点哪？仪表盘太复杂？你缺的不是功能，是帮用户赢一次。\n\n做法：围绕“新用户前五分钟该完成什么”重构流程。删掉多余屏幕，压缩到三步，每屏一个主行动。\n\n✅ 保存这份清单：\n1️⃣ 定义第一、三、五分钟的成功状态\n2️⃣ 删除所有不服务的页面和按钮\n3️⃣ 每步只留一个 CTA\n4️⃣ 记录取舍和要观察的激活率、完成率、退出点\n5️⃣ 小范围测试，数据说话\n\n结果：更短的路径，更少的选择，更明确的下一步。先让用户尝到甜头，再谈功能。\n\n#SaaS #产品设计 #增长 #用户激活 #独立开发 #startup"
          },
          "hashtags": [
            "#SaaS",
            "#产品设计",
            "#用户激活",
            "#Onboarding",
            "#精益创业"
          ],
          "imagePrompt": "对比图：左边是复杂的仪表盘，右边是一条简洁的路径，中间一个大问号，标题“前五分钟该完成什么？”"
        },
        "en": {
          "tagline": "From shipping features to shortening the path to a first win",
          "coreIdea": "Paused feature development for a week to rebuild a tiny SaaS onboarding flow around one question: what should a new user accomplish in the first five minutes? Result: a shorter path, fewer choices, and a clear next action, with documented trade-offs and signals to watch.",
          "titles": [
            "I Stopped Shipping Features for a Week and Rebuilt My SaaS Onboarding Around One Question",
            "From Dashboard Overload to a 5-Minute Win: A Tiny SaaS Onboarding Redesign",
            "The First 5 Minutes: The Question That Changed My Onboarding Flow"
          ],
          "hook": "When you stop adding features and ask what a new user should accomplish in the first five minutes, you realize most screens are just noise.",
          "quote": "What should a new user accomplish in the first 5 minutes?",
          "platforms": {
            "x": "Stopped shipping features for a week and rebuilt onboarding around one question: “What should a new user accomplish in the first 5 minutes?” Result: shorter path, fewer choices, clear next action. Documented the trade-offs, removed screens, remaining questions, and signals to watch. #SaaS #Onboarding",
            "xiaohongshu": "Title: I stopped shipping features for a week and rebuilt my tiny SaaS onboarding around one question: “What should a new user accomplish in the first 5 minutes?”\n\nPain point: Tired of adding features but users still churn? New users get overwhelmed by dashboards and don’t know what to click.\n\nWhat I did: Rebuilt the onboarding to answer that question. The result: a shorter path from first click to useful result, fewer choices, and one clear next action.\n\n✅ Save this checklist:\n1. Define what success looks like at minute 1, 3, and 5\n2. Remove every screen that doesn’t serve that goal\n3. Compress welcome flow to minimal steps, one primary action each\n4. Document trade-offs, removed screens, remaining questions, and signals to watch (activation, completion, drop-off)\n5. Test in a small cohort before expanding\n\n📌 Don’t add features first. Help users win once.\n\n#SaaS #ProductDesign #UserActivation #Onboarding #LeanStartup #IndieHacker",
            "zhihu": "# How to Rebuild a SaaS Onboarding Flow Around the “First 5 Minutes” Goal?\n\n## Conclusion\nStopping feature development and instead answering “What should a new user accomplish in the first 5 minutes?” can significantly shorten the path from first click to a useful result. By removing redundant screens, compressing choices, and clarifying the next action, I turned onboarding from a product showcase into a flow that guides users to an early small win. This change is not a bigger dashboard, but a shorter distance. The effectiveness still needs to be validated by observing activation rate, completion rate, and drop-off points.\n\n## Background\nMy product is a tiny SaaS. Over time, we kept adding features, but new user activation did not improve. Facing an ever-expanding dashboard, users were often lost. I decided to pause feature development for a week and focus on rebuilding the onboarding flow. The core question was: What should a new user accomplish in the first 5 minutes? The answer determined what to keep, what to remove, and how to give users a clear “I did it” moment early on.\n\n## Method\n1. Define success states within five minutes: what the user should see, understand, and do at minute 1, 3, and 5. For example, minute 1: complete signup and see the core value proposition; minute 3: create the first project or import data; minute 5: see the first usable result.\n2. Map the existing onboarding flow: list every screen, button, and popup, and mark whether it directly serves the defined success states.\n3. Remove elements not directly related: including redundant welcome pages, feature tours, unnecessary settings steps, and secondary CTAs. I removed several descriptive screens and advanced options, keeping only the main path.\n4. Compress steps and strengthen the main action: reduce the multi-step guide to a minimum, keep only one primary action per screen, and guide with a clear next-step button.\n5. Document trade-offs and remaining questions: which feature access points were sacrificed, which user education was postponed, and which issues remain unsolved (e.g., advanced users may need more guidance). Also list signals to watch: activation rate, first key action completion rate, mid-flow drop-off points, and user feedback.\n6. Launch to a small cohort and observe: let a portion of new users experience the new flow, compare data changes, and then decide whether to fully switch.\n\n## Limits\nThis change is based on my personal product scenario and limited user feedback; the sample size is small and not yet validated over time. The definition of “first 5-minute success” may vary completely across different products and user groups. Additionally, removing feature access points might affect some existing users or advanced needs, requiring layered guidance in future iterations. For now, it should be seen as a reasoned experiment rather than a universal method.",
            "wechat": "Title: I Stopped Shipping Features for a Week and Made My SaaS Activation Path Shorter: An Onboarding Redesign Experiment\n\nLead: When a product accumulates features, new users become more confused. I decided to stop all new feature development for a week and do one thing: redesign the onboarding flow to answer a key question—What should a new user accomplish in the first 5 minutes? The result was not a bigger dashboard, but a shorter and clearer path. This article records my trade-offs, the screens I removed, the questions that remained, and the signals I will watch to judge whether the change worked.\n\n1. From “Adding Features” to “Asking Questions”\nMy product is a tiny SaaS. Over the past period, we kept adding features, but new user activation did not improve. Users faced a complex dashboard after signup, didn't know where to click, and many churned after the free usage. I realized the problem might not be too few features, but that users didn't feel value in the first moments. So I paused feature development for a week and focused entirely on onboarding, with the core question: What should a new user accomplish in the first 5 minutes?\n\n2. Defining the Five-Minute Success Path\nTo answer that question, I had to define the key actions a user should complete early on. I broke the first five minutes into three time points: minute 1, complete signup/login and see the core value proposition; minute 3, create the first project or import data; minute 5, see the first usable result, even a simple output or preview. With this framework, I could review the existing flow and cut.\n\n3. What to Remove? What to Keep?\nI reviewed every screen and button in the onboarding flow, asking: Does it directly help the user reach any of those success states? If not, remove or postpone. As a result, I removed two descriptive welcome pages, a feature intro popup, and an advanced settings step, and compressed the original five-step guide into three steps. Each screen kept only one primary CTA, like “Create Project” or “Import Data,” with secondary options tucked into “Later.” The path became shorter, choices fewer, but each step clearer.\n\n4. Trade-offs and Remaining Questions\nRemoving things has costs. Some feature access points went deeper, which might affect advanced users who would have explored on their own; some educational content was delayed until after the first key action. I recorded these trade-offs and kept a “question list”: What if users need more guidance? What if advanced users can't find the entry? These need to be addressed in later iterations through layered onboarding or contextual prompts.\n\n5. What Signals Will I Watch?\nI won't declare this redesign a success immediately. I need to watch several key metrics: new user activation rate; completion rate from signup to first key action; mid-flow drop-off points; and clear positive or negative user feedback. I'll run the new flow on a small cohort first, compare with the old version's data, and then decide whether to fully switch.\n\nEnding: This experiment taught me the essence of onboarding: it's not about showing how powerful the product is, but helping users complete a meaningful task in the shortest time. Let users win once first—more important than any feature showcase. Whether this change truly works, the data will tell.",
            "wechat_moments": "Paused new features for a week to ask one question: What should a new user accomplish in the first 5 minutes? The result: a shorter path and fewer buttons. Help users win once before adding more. 🧭",
            "weibo": "I stopped shipping features for a week and redesigned my onboarding around one question: “What should a new user accomplish in the first 5 minutes?” The result wasn't a bigger dashboard, but a shorter path, fewer choices, and a clear next action. I documented the trade-offs, screens removed, questions remaining, and signals to watch. Let users taste the first useful result before talking about features. #SaaS #ProductDesign",
            "bilibili": "[Shot 1 - 0:00-0:15]\nVisual: Developer at computer, screen shows complex dashboard, then hand draws a question mark.\nVoiceover: \"I stopped shipping features for a week because I asked myself one question: What should a new user accomplish in the first 5 minutes?\"\nCaption: \"One week, one question\"\nEmoji: 🤔\n\n[Shot 2 - 0:15-0:45]\nVisual: Screen recording of old onboarding flow with multiple welcome pages and popups, then crossed out one by one.\nVoiceover: \"The old flow had five or six screens, buttons everywhere. I removed two welcome pages, one popup, compressed to three steps, and kept one primary action per screen.\"\nCaption: \"Cut the noise, keep the essential\"\nEmoji: ✂️\n\n[Shot 3 - 0:45-1:15]\nVisual: New flow demo, user clicks one button and quickly sees the first useful result.\nVoiceover: \"Now the path from first click to first result is much shorter. It's not about showing how many features the product has, but helping the user complete a meaningful task.\"\nCaption: \"Help users win once\"\nEmoji: ✅\n\n[Shot 4 - 1:15-1:45]\nVisual: Developer writing notes, trade-off list and metrics on screen.\nVoiceover: \"I documented all trade-offs: which feature entries were sacrificed, which questions remain, and the signals to watch—activation rate, completion rate, drop-off points. Data will tell if this works.\"\nCaption: \"Not just a redesign, but validation\"\nEmoji: 📊\n\n[Shot 5 - 1:45-2:00]\nVisual: End screen with big text: Help users win, then talk features.\nVoiceover: \"If you're building a SaaS, ask yourself: What does your new user accomplish in the first 5 minutes?\"\nCaption: \"Follow for data update\"\nCTA: \"Comment your onboarding experience\"\nEmoji: 👉",
            "douyin": "[0:00-0:05] Visual: Phone screen close-up, tapping signup. Voiceover: \"Stopped shipping features for a week, I asked one question\" Caption: One week, one question\n[0:05-0:15] Visual: Old UI with popups, quickly swiped away. Voiceover: \"What should a new user accomplish in the first 5 minutes? Not a dashboard, but a useful result.\" Caption: Not more, but faster\n[0:15-0:25] Visual: New flow three steps, one button leads to result. Voiceover: \"Removed screens, compressed to three steps, each with one primary action.\" Caption: Shorter path, fewer choices, clear next action\n[0:25-0:35] Visual: Charts and notes. Voiceover: \"I documented trade-offs and signals: activation, completion, drop-off. Data decides.\" Caption: Validate before deciding\n[0:35-0:45] End screen: \"Help users win first\". Voiceover: \"What does your new user accomplish in 5 minutes? Comment below.\" CTA: Follow + comment",
            "kuaishou": "[Opening] Visual: Me sitting at computer, turning to camera. Voiceover: \"I rebuilt my SaaS onboarding with just one question.\" Caption: One question changed the flow\n[Process] Visual: Screen recording, deleting pages. Voiceover: \"What should a new user do in the first 5 minutes? I set three checkpoints: minute 1 signup, minute 3 create project, minute 5 see result. Then removed everything unrelated.\" Caption: Minute 1, 3, 5\n[Result] Visual: New flow operation. Voiceover: \"Now from click to useful result, path is much shorter, buttons fewer.\" Caption: Faster to useful result\n[Ending] Visual: Notes close-up. Voiceover: \"I recorded trade-offs and signals like activation and completion. Running small cohort, data will decide.\" Caption: Data validates\n[CTA] Visual: Big text \"Help users win once\". Voiceover: \"What's your product's first 5 minutes? Comment below.\"",
            "linkedin": "I paused feature development for a week to rebuild my tiny SaaS onboarding around a single question: What should a new user accomplish in the first five minutes? The outcome: a shorter path from first click to a useful result, fewer choices, and one clear next action. I removed redundant screens, condensed the flow, and documented trade-offs plus signals to monitor (activation, completion, drop-off). Key lesson: onboarding isn't about showing off features; it's about helping users win once. What does your product's first five minutes look like? Let's discuss. #SaaS #ProductManagement #UserOnboarding",
            "threads": "Stopped shipping features for a week to ask: “What should a new user accomplish in the first 5 minutes?” Result: shorter path, fewer choices, clear next action. Removed screens, documented trade-offs and signals to watch. Help users win once. #SaaS #Onboarding",
            "reddit": "Title: I stopped adding features for a week and rebuilt my SaaS onboarding around one question.\n\nBody: My tiny SaaS kept adding features but activation didn't improve. Last week I paused new development and redesigned the onboarding flow, focusing on: \"What should a new user accomplish in the first 5 minutes?\" I removed a couple of welcome screens and a popup, condensed the flow to three steps, each with one primary CTA. The result is a shorter path from first click to a useful result, fewer choices, and a clear next action. I documented trade-offs, removed screens, remaining questions, and signals to watch (activation rate, completion rate, drop-off points). No data yet, so I can't say if it worked. Has anyone else tried this? How do you define \"first 5-minute success\" for your product? Let's discuss.",
            "tiktok": "[0:00-0:05] Visual: phone screen with signup. Voiceover: \"I stopped shipping features for a week and rebuilt my SaaS onboarding.\" Caption: \"One question changed everything 🔍\"\n[0:05-0:15] Visual: messy dashboard being crossed out. Voiceover: \"The question: what should a new user accomplish in the first 5 minutes?\" Caption: \"Not a bigger dashboard, a shorter path\"\n[0:15-0:25] Visual: new flow with one button. Voiceover: \" I cut screens, reduced choices, and made one clear next action.\" Caption: \"Fewer choices, faster win ⚡\"\n[0:25-0:35] Visual: notes and metrics. Voiceover: \"Documented trade-offs, removed screens, and signals to watch: activation, completion, drop-off.\" Caption: \"Let data decide 📊\"\n[0:35-0:45] End screen: \"Help users win in 5 minutes.\" Voiceover: \"What does your new user accomplish in 5 minutes? Comment below.\" CTA: Follow for part 2",
            "youtube": "[0:00-0:30] Intro\nVisual: Developer facing camera, workspace background, screen shows product UI.\nVoiceover: \"Hey everyone, today I want to talk about an experiment I ran. I stopped shipping new features for a week and completely redesigned my onboarding flow around one question: What should a new user accomplish in the first 5 minutes?\"\nCaption: \"One week, redesign onboarding\"\nEmoji: 🎬\n\n[0:30-2:00] Background & Problem\nVisual: Screen recording of old onboarding, multiple pages and popups, user clicks confused.\nVoiceover: \"We used to keep adding features; the dashboard got more complex but new user activation didn't improve. Users came in not knowing where to click and churned quickly. I realized the problem wasn't lack of features, but that users didn't feel value in the first moments.\"\nCaption: \"More features ≠ better activation\"\nEmoji: 📉\n\n[2:00-3:30] Defining 5-Minute Success\nVisual: Whiteboard animation listing minute 1, 3, 5 goals.\nVoiceover: \"I broke the first five minutes into three checkpoints: minute 1 complete signup and see core value; minute 3 create the first project or import data; minute 5 see the first usable result. This framework helped me decide what to keep.\"\nCaption: \"Minute 1 signup, minute 3 create, minute 5 result\"\nEmoji: ⏱️\n\n[3:30-5:00] Cutting & Rebuilding\nVisual: Screen recording showing deletion, old pages crossed out, new flow appears.\nVoiceover: \"Then I started cutting: two welcome pages, a feature intro popup, an advanced settings step. Compressed the original five steps to three, with one primary button per screen. The path got shorter, choices fewer, but each step clearer.\"\nCaption: \"Cut noise, keep the essential path\"\nEmoji: ✂️\n\n[5:00-6:30] Trade-offs & Open Questions\nVisual: Show notes document with trade-off list and questions.\nVoiceover: \"Cutting has costs: feature entries deeper, education delayed. I recorded these questions, like how to handle advanced users who can't find the entry. I also listed signals to watch: activation rate, completion rate, drop-off points.\"\nCaption: \"Trade-offs and unresolved questions\"\nEmoji: 📝\n\n[6:30-8:00] Validation Plan & Conclusion\nVisual: Back to developer facing camera, screen shows data charts.\nVoiceover: \"The new flow is in a small cohort test; I won't claim success yet. Data will tell. But one thing is clear: onboarding is about helping users complete a meaningful task, not showcasing the product. Help users win once—more important than any feature demo.\"\nCaption: \"Help users win first\"\nEmoji: 🏁\nCTA: \"If you're running similar experiments, share your 'first 5 minutes' definition in the comments. Like and subscribe for data updates.\"",
            "medium": "Title: I Rebuilt My SaaS Onboarding Around One Question and Deleted Half the Flow\n\nLead: In product development, we often solve problems by adding: low activation? Add features. Low conversion? Add more guidance. But sometimes the answer is subtraction. I stopped shipping features for a week and redesigned my onboarding flow to answer one question: What should a new user accomplish in the first 5 minutes? Here's my full record.\n\n1. The Birth of the Question\nMy product is a tiny SaaS. Users signed up and landed on a dashboard that kept growing with features. We kept adding things, but activation stayed flat. Then I stopped and asked: If a new user gives me only five minutes, what should I let them experience? The answer would determine the entire onboarding design.\n\n2. Defining Success at Three Minute-Marks\nI broke the first five minutes into three concrete moments: minute 1, complete signup and see the core value—not a welcome message, but an immediate understanding of \"what can this tool do for me.\" Minute 3, create the first project or import data, starting real usage. Minute 5, see the first usable result, even a preview or simple output. These three checkpoints became my filter.\n\n3. Using the Filter to Delete Noise\nI reviewed every screen, button, and popup in the existing onboarding flow: Does it directly help the user reach one of those three checkpoints? If not, remove or postpone. In the end, I removed two descriptive welcome pages, one feature intro popup, and one advanced settings step, and compressed the original five steps into three. Each screen kept only one primary action, with everything else tucked into \"Later.\"\n\n4. Trade-offs and Remaining Questions\nDeletion has costs. Some feature entries became deeper, some educational content delayed. I kept a list: What if users need more guidance? What if advanced users can't find the entry? These need to be addressed through layered onboarding or contextual prompts later. I also recorded signals to watch: activation rate, first key action completion rate, drop-off points, and user feedback.\n\n5. Validate on a Small Cohort First\nI won't declare success immediately. I'll randomly split new users and run the new flow on a subset, then compare data before deciding. My belief: onboarding isn't about showing off the product; it's about helping users complete a meaningful task. Let users win once first.\n\nEnding: The experiment is still ongoing, but I've learned one thing: less is more, especially before users build habits. What does your product's first five minutes look like? Share your thoughts.",
            "facebook": "I stopped shipping features for a week and rebuilt my tiny SaaS onboarding flow around one question: \"What should a new user accomplish in the first 5 minutes?\" The outcome: a shorter path from first click to a useful result, fewer choices, and a clear next action. Removed redundant screens, documented trade-offs, and listed signals to watch (activation, completion, drop-off). Lesson: help users win once before showing off all features. What does your product's first 5 minutes look like? #SaaS #Onboarding #ProductDesign",
            "instagram": "Title: I paused feature development for a week to redesign my onboarding around one question\n\nPain point: New users don't know where to click? Dashboard too complex? You don't need more features—you need to help users win once.\n\nWhat I did: Rebuilt the flow around \"What should a new user accomplish in the first 5 minutes?\" Removed redundant screens, compressed to three steps, one main action each.\n\n✅ Save this checklist:\n1️⃣ Define success at minute 1, 3, and 5\n2️⃣ Remove every page and button that doesn't serve that goal\n3️⃣ Keep only one CTA per step\n4️⃣ Document trade-offs and signals to watch (activation, completion, drop-off)\n5️⃣ Test on a small cohort, let data decide\n\nResult: shorter path, fewer choices, clearer next action. Let users taste a win before talking features.\n\n#SaaS #ProductDesign #Growth #UserActivation #IndieHacker #Startup"
          },
          "hashtags": [
            "#SaaS",
            "#ProductDesign",
            "#UserActivation",
            "#Onboarding",
            "#LeanStartup"
          ],
          "imagePrompt": "Split image: left side cluttered dashboard, right side clean path with one button, big question mark in center, text 'What should a new user accomplish in the first 5 minutes?'"
        }
      }
    },
    {
      "id": "creator-workflow",
      "label": "Creator workflow",
      "labelZh": "创作者工作流",
      "source": "我把每天收藏的文章、会议纪要和灵感碎片，整理成一个可复用的内容工作流。过去我通常会把同一段文字复制到多个平台，再补几个标签，结果每个平台都像半成品。后来我先提取一个能被引用的观点，给它标出原文证据和不能越过的边界，再为不同平台改写：知乎写背景与因果，小红书写步骤和清单，公众号保留完整叙事，朋友圈只留下一个真实的分享理由，短视频则先设计画面和口播。为了验证它是否真的有用，我持续记录：哪些内容被保存，哪些内容引发回复，哪些内容虽然写得很长却没人看。这样做的价值不是每天发更多，而是减少从想法到发布之间的摩擦。",
      "baseline": {
        "language": "zh",
        "score": 70,
        "signals": [
          "tension",
          "clear topic",
          "quotable length"
        ],
        "evidence": [
          "为了验证它是否真的有用，我持续记录：哪些内容被保存，哪些内容引发回复，哪些内容虽然写得很长却没人看。",
          "这样做的价值不是每天发更多，而是减少从想法到发布之间的摩擦。",
          "后来我先提取一个能被引用的观点，给它标出原文证据和不能越过的边界，再为不同平台改写：知乎写背景与因果，小红书写步骤和清单，公众号保留完整叙事，朋友圈只留下一个真实的分享理由，短视频则先设计画面和口播。"
        ],
        "platformCount": 17
      },
      "polished": {
        "zh": {
          "tagline": "把散落内容变成可复用工作流，减少想法到发布的摩擦",
          "coreIdea": "每天收藏的文章、会议纪要和灵感碎片，通过提取可引用观点、标注证据与边界、按平台改写的方法，转化成一个可复用且持续验证的内容工作流，核心价值是降低发布摩擦。",
          "titles": [
            "我用把收藏夹变成内容流水线：步骤、边界与复盘",
            "别再复制粘贴到每个平台了：一个可复用的内容改写工作流",
            "从收藏到发布，我如何设计减少摩擦的内容系统"
          ],
          "hook": "过去我常把同一段文字复制到多个平台，结果每个平台都像半成品。后来我改变方式：先提取一个可引用的观点，标出原文证据和不能越过的边界，再为不同平台改写。持续记录后，我发现真正的价值不是每天发更多，而是减少从想法到发布之间的摩擦。",
          "quote": "这样做的价值不是每天发更多，而是减少从想法到发布之间的摩擦。",
          "platforms": {
            "x": "我此前做了一个实验：把每天收藏的文章、会议纪要和灵感碎片，整理成可复用的内容工作流。核心只有三步：提取可引用观点、标注证据和边界、按平台改写。结果发现，真正有用的不是发得更多，而是减少从想法到发布之间的摩擦。 #内容工作流 #发布系统",
            "xiaohongshu": "🔄 标题：每天收藏一堆，却发不出东西？试试这个可复用内容工作流\n\n你有没有这样：收藏夹里全是好文章、会议纪要和灵感，但每次想发点什么，不是复制粘贴到每个平台，就是加几个标签草草了事，最后每个平台都像半成品？\n\n我后来换了一套流程，使用后感觉顺手很多：\n\n1️⃣ 从当天收藏里挑一个能引用的观点，而不是整段搬运。\n2️⃣ 给这个观点标出原文证据，以及不能越过的边界（别脑补数据、别编造结论）。\n3️⃣ 再按平台改写：知乎写背景和因果，小红书写步骤和清单，公众号保留完整叙事，朋友圈只留一个真实的分享理由，短视频先想画面和口播。\n4️⃣ 持续记录，看哪些内容被保存、哪些引发回复、哪些写得很长却没人看。\n5️⃣ 根据记录调整，重点不是多发，而是降低每次发布的阻力。\n\n这样下来，我不再觉得每个平台都是半成品，也少了很多从想到做的犹豫。\n\n#内容工作流 #笔记整理 #发布系统 #减少摩擦 #平台改写",
            "zhihu": "# 如何把每天收藏的内容整理成可复用的内容工作流？\n\n## 结论\n\n把收藏的文章、会议纪要和灵感碎片，先提取一个可被引用的观点，标出原文证据和不能越过的边界，再为不同平台改写，并持续记录用于验证，能够有效减少从想法到发布之间的摩擦。真正的价值不是每天发更多，而是让发布变得顺畅。\n\n## 背景\n\n过去我习惯把同一段文字复制到多个平台，再补几个标签，结果每个平台都像半成品。原因在于：内容没有经过平台适配，观点没有边界，发布动作重复而低效。于是我尝试建立一套流程，把“收藏—改写—发布—复盘”串起来。\n\n## 方法\n\n1. 从当天收藏的文章、会议纪要或灵感碎片中，提取一个能被引用的观点。\n2. 给这个观点标出原文证据，以及不能越过的边界，确保改写时不夸大、不编造。\n3. 为不同平台做适配改写：\n   - 知乎写背景与因果；\n   - 小红书写步骤和清单；\n   - 公众号保留完整叙事；\n   - 朋友圈只留下一个真实的分享理由；\n   - 短视频先设计画面和口播。\n4. 持续记录，统计哪些内容被保存、哪些引发回复、哪些虽然写得很长却没人看。\n5. 根据记录调整流程，重点降低摩擦。\n\n## limits\n\n这套流程只基于我个人记录，没有大规模样本，也未对比不同行业或账号类型。它适用于希望减少发布摩擦的内容创作者，但效果可能因人而异。记录内容时，需要避免把“保存量”或“回复量”误当成唯一目标，因为有的长文即使无人看，也可能有长期价值。",
            "wechat": "标题：我把收藏夹变成了一条内容流水线，不是为了发更多，而是为了少摩擦\n\n导语：每天收藏很多，真正发出来的却很少；即使发出来，也像半成品。我用一段时间整理出一套可复用的内容工作流，核心只有一件事：减少从想法到发布之间的摩擦。\n\n正文：\n\n**一、问题：为什么每个平台都像半成品？**\n\n过去，我习惯把同一段文字复制到多个平台，再补几个标签。结果呢？知乎上像没讲完的答案，小红书上像没头没尾的笔记，公众号上像碎片拼凑，朋友圈像广告。问题不在内容本身，而在没有为平台做适配，也没有给观点设边界。\n\n**二、流程：三步把收藏变成可发布内容**\n\n第一步，提取一个能被引用的观点。每天收藏的文章、会议纪要、灵感碎片很多，但真正能用来发布的，通常是一个清晰的、可复述的观点。\n\n第二步，标注原文证据和不能越过的边界。证据告诉你这个观点从哪里来，边界提醒你不要脑补数据、不要夸大结果。这样改写时才不会走样。\n\n第三步，按平台改写。我给每个平台规定了改写重点：知乎写背景与因果，小红书写步骤和清单，公众号保留完整叙事，朋友圈只留一个真实的分享理由，短视频先设计画面和口播。这样每个平台的内容不再是同一个半成品，而是各自完整的表达。\n\n**三、验证：持续记录**\n\n为了确认这套流程是否真的有用，我记录了一段时间：哪些内容被保存，哪些内容引发回复，哪些内容虽然写得很长却没人看。记录不是为了追求“爆款”，而是为了找到摩擦点——比如某个平台我总写得过长，或者某个观点我总在边界上犹豫。\n\n**四、价值：不是多发，而是少摩擦**\n\n最大的感受是，这套流程让我不再把发布当成一个沉重的任务。以前从收藏到发布之间，有太多决策：写什么、怎么写、发哪里。现在这些决策被流程接管，我只需要关注观点本身。这样做，并不是为了每天发更多，而是让每一次发布都更顺。\n\n结尾：如果你也有收藏很多、发布很少的困扰，不妨试试这个思路：先提取观点，再标边界，最后按平台改写，记录看看变化。内容工作流不是模板，而是一套能减少犹豫的系统。",
            "wechat_moments": "过去总把一段话复制到所有平台，结果每个都像半成品。现在改成先提取观点、标边界，再按平台改写，记录使用后发现：真正的价值不是多发，而是少摩擦。分享给同样在整理内容的朋友。",
            "weibo": "试了可复用的内容工作流：每天收藏的文章、纪要和灵感，先提一个可引用观点，标好证据和边界，再按平台改写。知乎写因果，小红书列步骤，公众号保留叙事，朋友圈只留真实理由。最后发现，重点不是每天发更多，而是减少从想到发之间的摩擦。 #内容工作流",
            "bilibili": "【视频脚本：一个内容工作流的真实记录】\n\n0:00-0:10\n镜头：桌面铺满打印文章、会议记录本、手机备忘录。\n口播：每天收藏很多，真正发出来的却很少。这个月我试了一套新流程。\n字幕：从收藏到发布，减少摩擦。\n\n0:10-0:30\n镜头：快速剪辑过去复制粘贴到多个平台的画面，配“半成品”字幕。\n口播：以前我总把同一段文字复制到各个平台，再加几个标签，结果每个平台都像半成品。\n字幕：复制粘贴 ≠ 平台适配\n\n0:30-1:00\n镜头：手写三个步骤：提取观点、标记证据边界、平台改写。\n口播：后来我改了：先提取一个可以被引用的观点，给它标出原文证据和不能越过的边界，再为不同平台改写。\n字幕：三步：观点、边界、适配\n\n1:00-1:30\n镜头：分屏展示不同平台改写要点：知乎（背景因果）、小红书（步骤清单）、公众号（完整叙事）、朋友圈（真实理由）、短视频（画面口播）。\n口播：知乎写背景与因果，小红书写步骤和清单，公众号保留完整叙事，朋友圈只留一个真实的分享理由，短视频先设计画面和口播。\n字幕：每个平台都有自己的任务\n\n1:30-2:00\n镜头：日历上连续打钩，旁边有“被保存”“引发回复”“长但没人看”三类标签。\n口播：为了验证是否有用，我持续记录：哪些内容被保存，哪些引发回复，哪些虽然写得很长却没人看。\n字幕：记录结果，找到摩擦点\n\n2:00-2:30\n镜头：回到桌面，把标签整理成“减少摩擦”的便签。\n口播：真正的价值不是每天发更多，而是减少从想法到发布之间的摩擦。如果你也有收藏多发布少的困扰，可以试试这个流程。\n字幕：减少摩擦，而不是增加数量\nCTA：评论区说说你发布前最大的阻力是什么？",
            "douyin": "【短视频脚本：别再让收藏吃灰】\n\n0:00-0:05\n镜头：手机屏幕滑动收藏夹，密密麻麻。\n口播：收藏夹爆了，但发出来的没几条。\n字幕：你的收藏夹吃灰了吗？\n\n0:05-0:15\n镜头：快速展示复制粘贴到不同平台的画面，配上“半成品”贴纸。\n口播：以前我也复制粘贴到每个平台，结果都像半成品。\n字幕：复制粘贴，平台全废\n\n0:15-0:30\n镜头：手写流程图：观点→证据边界→平台改写。\n口播：后来我改成：先提取一个可引用观点，标上原文证据和不能越过的边界，再按平台改写。\n字幕：三步走：观点、边界、适配\n\n0:30-0:50\n镜头：分屏展示不同平台改写重点，图标配合文字。\n口播：知乎写背景因果，小红书列步骤清单，公众号保留叙事，朋友圈只留真实理由，短视频先设计画面口播。\n字幕：平台不同，写法不同\n\n0:50-1:05\n镜头：日历记录一段时间，三类标签闪现。\n口播：我记录了一段时间：哪些被保存、哪些引发回复、哪些长但没人看。最后发现，真正有用的是减少摩擦，不是多发。\n字幕：价值 = 减少摩擦\nCTA：关注我，下期讲怎么提取观点。",
            "kuaishou": "【快手视频脚本：把收藏变发布的土办法】\n\n0:00-0:08\n镜头：老式笔记本和手机并排，纸上写着“收藏→发布”。\n口播：老铁们，我最近试了个办法，把每天收藏的东西变成能发的内容。\n字幕：收藏变发布，试试这个\n\n0:08-0:20\n镜头：演示以前复制粘贴到多个平台，画面乱。\n口播：以前复制同一段话到所有平台，结果每个都像半成品，没人看。\n字幕：复制粘贴不顶用\n\n0:20-0:38\n镜头：在黑板上画三个框：提取观点、标边界、平台改写。\n口播：现在我先找一个能说的观点，标上证据和不能瞎编的线，再按平台改。\n字幕：观点、边界、改写\n\n0:38-0:55\n镜头：展示不同平台怎么改：知乎写因果，小红书列步骤，公众号写全，朋友圈说人话，短视频先想画面。\n口播：知乎写为什么，小红书写怎么做，公众号写完整，朋友圈说真话，短视频先想画面和口播。\n字幕：一个平台一个写法\n\n0:55-1:10\n镜头：一段时间日历，画圈和文字。\n口播：我记了一段时间，看哪些被存、哪些有回复、哪些没人看。最后悟了：不是发得多，是少费劲。\n字幕：少费劲，才对路\nCTA：觉得有用点个赞，评论区聊聊你的流程。",
            "linkedin": "我用把每天收藏的文章、会议纪要和灵感碎片，整理成了一套可复用的内容工作流。核心是三步：提取可引用观点、标注证据与边界、按平台改写。知乎写背景因果，小红书列步骤清单，公众号保留完整叙事，朋友圈只留真实理由，短视频先设计画面口播。连续记录后我发现，真正的价值不是每天发更多，而是减少从想法到发布之间的摩擦。如果你也在做内容，建议从“降低摩擦”开始优化。#内容策略 #工作流",
            "threads": "过去复制粘贴到每个平台，结果全是半成品。后来改成先提取观点、标边界，再按平台改写，记录使用后发现：真正有用的不是多发，而是减少摩擦。",
            "reddit": "（发在 r/ContentCreation 或类似中文子版）标题：一个减少发布摩擦的内容工作流，有人试过类似方法吗？\n\n正文：我每天收藏文章、会议纪要和灵感，但发布总是拖。此前我尝试一个流程：先从收藏中提取一个可引用的观点，标出原文证据和不能越过的边界，再为不同平台改写（知乎写因果，小红书列步骤，公众号写完整，朋友圈只说真实理由，短视频先想画面）。然后我记录了一段时间：哪些被保存、哪些有回复、哪些长但没人看。结果发现最大的价值不是发更多，而是减少犹豫。你们有没有自己的内容工作流？欢迎分享，尤其是怎么降低发布摩擦的。",
            "tiktok": "【短视频脚本：你的收藏夹为什么一直吃灰？】\n\n0:00-0:06\n镜头：手机收藏夹截图，配文字“999+”。\n口播：你是不是也收藏一堆，但发出来的没几个？\n字幕：收藏999+，发布0\n\n0:06-0:16\n镜头：快速演示复制粘贴到多个平台，结果乱七八糟。\n口播：我以前也这样，复制同一段话到所有平台，结果全是半成品。\n字幕：复制粘贴，都像半成品\n\n0:16-0:32\n镜头：动画演示三个步骤：提取观点、标记边界、平台改写。\n口播：后来我改成：先提取一个可引用观点，标出原文证据和不能越过的边界，再按平台改写。\n字幕：三步工作流\n\n0:32-0:48\n镜头：分屏展示不同平台：知乎写因果，小红书列步骤，公众号写完整，朋友圈说真实理由，短视频先想画面。\n口播：知乎写背景因果，小红书列步骤清单，公众号保留完整叙事，朋友圈只留真实理由，短视频先设计画面口播。\n字幕：每个平台不一样\n\n0:48-1:02\n镜头：日历上记录一段时间，显示“保存”“回复”“没人看”。\n口播：我记了一段时间，看哪些被保存、哪些有回复、哪些长但没人看。最后发现，价值不是多发，是减少摩擦。\n字幕：减少摩擦 > 增加数量\nCTA：关注我，一起做内容不费劲。",
            "youtube": "【YouTube 视频脚本：我如何设计一个减少发布摩擦的内容工作流】\n\n0:00-0:15\n镜头：桌面上散落着打印文章、笔记本、手机，镜头缓慢推进。\n口播（画外音）：每天我们收藏大量文章、会议纪要和灵感，但真正发布出来的很少，甚至发出来也像半成品。\n字幕：从收藏到发布，中间隔着什么？\n\n0:15-0:40\n镜头：屏幕录制演示复制粘贴到多个平台，并打开几个平台对比，显示内容重复、不协调。\n口播：过去我常把同一段文字复制到多个平台，再加几个标签，结果每个平台都显得不完整。问题不是内容不好，而是没有为平台做适配。\n字幕：复制粘贴 ≠ 内容适配\n\n0:40-1:10\n镜头：白板动画，画出三个步骤：1. 提取可引用观点；2. 标注原文证据和边界；3. 按平台改写。\n口播：后来我建立了一个流程。首先，从当天收藏中提取一个能被引用的观点；其次，给它标出原文证据和不能越过的边界，这样改写时不会走样；最后，为不同平台做适配。\n字幕：三步：观点、边界、适配\n\n1:10-1:50\n镜头：分屏展示五个平台，每个平台下方标注改写重点：知乎—背景因果；小红书—步骤清单；公众号—完整叙事；朋友圈—真实理由；短视频—画面口播。\n口播：每个平台有不同任务：知乎写背景与因果，小红书写步骤和清单，公众号保留完整叙事，朋友圈只留一个真实的分享理由，短视频先设计画面和口播。这样每个平台的内容都是完整的。\n字幕：一个平台一个任务\n\n1:50-2:30\n镜头：日历特写，连续一段时间，某些日期被圈出，旁边贴着三类标签。\n口播：为了验证这个流程是否真的有用，我持续记录：哪些内容被保存，哪些内容引发回复，哪些内容虽然写得很长却没人看。记录帮助我找到摩擦点，而不是追求爆款。\n字幕：记录结果，找到摩擦\n\n2:30-3:00\n镜头：回到桌面，整理出一张“减少摩擦”的便签，结尾定格。\n口播：最终我意识到，这套流程的价值不是每天发更多，而是减少从想法到发布之间的摩擦。如果你也有收藏多、发布少的困扰，可以试试这个思路。\n字幕：减少摩擦，顺畅发布\nCTA：欢迎在评论区分享你在发布前最大的阻力是什么。",
            "medium": "标题：从收藏到发布：我用一段时间搭建的内容工作流，核心是减少摩擦\n\n导语：收藏了很多，却发布不出来；即使发布，也像半成品。这是我过去的状态。后来我设计了一套流程，把一段时间的记录变成可复用的系统。这篇文章分享具体做法和边界。\n\n正文：\n\n**为什么每个平台都像半成品？**\n\n过去我习惯把同一段文字复制到多个平台，再补几个标签。结果呢？知乎上像没写完的答案，小红书上像没有步骤的清单，公众号上像拼凑的草稿，朋友圈像广告。根源在于：内容没有针对平台特性进行改写，观点没有来源边界。\n\n**我的工作流：三步走**\n\n第一步：提取一个可被引用的观点。每天收藏的文章、纪要和灵感很多，但能用来发布的通常只是其中一个清晰的观点。\n\n第二步：标注原文证据和不能越过的边界。证据告诉你观点来自哪里，边界防止你在改写时脑补数据、夸大效果。这是保持内容可信的关键。\n\n第三步：按平台改写。我给不同平台规定了改写方向：知乎写背景与因果，小红书写步骤和清单，公众号保留完整叙事，朋友圈只留一个真实的分享理由，短视频先设计画面和口播。每个平台的内容都应该是完整的，而不是同一段话的复制。\n\n**如何验证是否有用？**\n\n我持续记录，统计三类信号：哪些内容被保存，哪些内容引发回复，哪些内容虽然写得很长却没人看。记录不是为了追求数量，而是找到摩擦点。例如，如果某个平台总是写得过长，就减少字数；如果某个观点总在边界上犹豫，就重新审视证据。\n\n**真正的价值：减少摩擦**\n\n最终我意识到，这套流程最大的价值不是每天发更多，而是减少从想法到发布之间的摩擦。以前每次发布都要重新决定写什么、怎么写、发哪里；现在这些决策被流程接管。内容工作流不是模板，而是让创作更顺畅的系统。\n\n结尾：如果你也有收藏多、发布少的困扰，不妨从“提取观点—标边界—平台改写—记录复盘”开始，试看看变化。",
            "facebook": "此前我试着把每天收藏的文章、会议纪要和灵感碎片，整理成一套内容工作流。核心是：先提取一个可引用的观点，标出原文证据和边界，再按平台改写。知乎写因果，小红书列步骤，公众号写完整叙事，朋友圈只留真实理由，短视频先想画面。持续记录后，我发现真正的价值不是每天发更多，而是减少从想法到发布之间的摩擦。如果你也在做内容，可以试试这个方法。",
            "instagram": "📌 标题：收藏夹吃灰？试试这个可复用内容工作流\n\n痛点：收藏一堆，发布困难，复制粘贴到每个平台都像半成品。\n\n我的方法：\n1️⃣ 从当天收藏里提取一个可引用的观点\n2️⃣ 标注原文证据和不能越过的边界\n3️⃣ 按平台改写：知乎写因果，小红书列步骤，公众号写完整，朋友圈说真实理由，短视频先想画面\n4️⃣ 持续记录：看保存、回复、没人看的地方\n5️⃣ 根据记录调整，重点减少摩擦\n\n这样做下来，发布不再像任务，而是一条顺滑的流水线。\n\n#ContentWorkflow #NoteTaking #PublishingSystem #ReduceFriction #PlatformTips"
          },
          "hashtags": [
            "#内容工作流",
            "#笔记整理",
            "#发布系统",
            "#减少摩擦",
            "#平台改写"
          ],
          "imagePrompt": "一张温暖色调的工作台俯视图，左侧有收藏的文章打印件、会议笔记本和便签，中央是连接不同平台图标的手绘流程图，右侧手机屏幕显示发布草稿，整体突出从想法到发布的路径，减少摩擦。"
        },
        "en": {
          "tagline": "Turn daily saves into a repeatable content workflow that reduces friction from idea to publish.",
          "coreIdea": "Extract one quotable point from daily saves, mark its evidence and boundaries, then rewrite for each platform, and track the results to reduce publishing friction.",
          "titles": [
            "How I Turned My Endless Saves Into a Low-Friction Content Workflow",
            "Stop Copy-Pasting Everywhere: A Platform-Specific Rewriting System",
            "From Idea to Publish: My short Experiment in Reducing Friction"
          ],
          "hook": "I used to copy the same text to every platform, and each one felt half-finished. Then I changed my approach: extract a quotable point, mark its evidence and boundaries, and rewrite for each platform. After tracking the results, I found the real value isn't posting more—it's reducing the friction between idea and publish.",
          "quote": "The real value isn't posting more every day; it's reducing the friction between idea and publish.",
          "platforms": {
            "x": "Spent a while turning daily saves—articles, meeting notes, idea fragments—into a repeatable content workflow. Core steps: extract one quotable point, mark evidence and boundaries, then rewrite per platform. The biggest win? Less friction from idea to publish, not more posts. #ContentWorkflow #PublishingSystem",
            "xiaohongshu": "🔄 Title: Save everything but publish nothing? Try this repeatable content workflow\n\nSound familiar? Your bookmarks are full of articles, meeting notes, and sparks, but when you try to post, you either copy-paste the same text everywhere or just add a few tags—and every platform ends up looking like a draft.\n\nI switched to a new process over time:\n\n1️⃣ Pick one quotable point from today's saves instead of moving whole blocks.\n2️⃣ Mark the original evidence and the boundary you can't cross (no inventing data, no overclaiming).\n3️⃣ Rewrite for each platform: Zhihu gets background and causality, Xiaohongshu gets steps and checklists, WeChat articles keep the full narrative, Moments gets only a genuine share reason, short video starts with visuals and voiceover.\n4️⃣ track the results: see which saves get kept, which trigger replies, which are long but nobody reads.\n5️⃣ Adjust based on the record—the goal is less friction, not more volume.\n\nNow every platform feels intentional, and publishing is no longer a chore.\n\n#ContentWorkflow #NoteTaking #PublishingSystem #ReduceFriction #PlatformAdaptation",
            "zhihu": "# How to organize daily saves into a repeatable content workflow?\n\n## conclusion\n\nExtract one quotable point from daily saves, mark its original evidence and non-negotiable boundaries, rewrite for each platform, and track the results to verify. The real value is reducing friction between idea and publish, not posting more.\n\n## background\n\nI used to copy the same text to multiple platforms and add tags, but every platform felt half-finished. The reason: content wasn't adapted to platform expectations, viewpoints lacked boundaries, and publishing was repetitive and inefficient. So I built a process linking collection, rewriting, publishing, and review.\n\n## method\n\n1. From daily saved articles, meeting notes, or idea fragments, extract one point that can be quoted.\n2. Mark that point with original evidence and the boundary that cannot be crossed—don't invent facts, don't overstate outcomes.\n3. Rewrite for each platform:\n   - Zhihu: background and causality;\n   - Xiaohongshu: steps and checklist;\n   - WeChat article: full narrative;\n   - WeChat Moments: a genuine share reason;\n   - Short video: design visuals and voiceover first.\n4. Track for a period of time: which content gets saved, which triggers replies, which is long but unread.\n5. Adjust based on the record, focusing on reducing friction.\n\n## limits\n\nThis workflow is based on a period of time of personal tracking, without a large sample or comparison across industries or account types. It suits creators who want to reduce publishing friction, but results may vary. Avoid treating saves or replies as the only goal; some long pieces may have long-term value even if unread.",
            "wechat": "Title: I Turned My Save Folder Into a Content Pipeline—Not to Publish More, but to Friction Less\n\nLead: Every day we save articles, meeting notes, and sparks. Yet few become posts, and those that do often feel half-done. over time, I built a repeatable content workflow with a single focus: reduce friction from idea to publish.\n\nBody:\n\n**The Problem: Why every platform feels like a draft**\n\nI used to copy the same text to multiple platforms and add a few tags. The result? Zhihu answers that lacked cause and effect, Xiaohongshu notes without steps, WeChat articles that read like clippings, Moments that sounded like ads. The content wasn't bad; it just wasn't adapted, and the viewpoint had no boundary.\n\n**The Workflow: Three steps from save to publish**\n\nStep one: Extract one quotable point. Out of all the daily saves, the piece worth publishing is usually a single clear, repeatable idea.\n\nStep two: Mark the original evidence and the boundary you can't cross. Evidence tells you where the point comes from; the boundary keeps you from inventing data or overclaiming. This keeps rewriting trustworthy.\n\nStep three: Rewrite for each platform. I assigned each platform a specific task: Zhihu explains background and causality, Xiaohongshu lists steps and checklists, WeChat article keeps the full narrative, Moments shares one genuine reason, short video designs visuals and voiceover first. Now every platform gets a complete piece, not a copy.\n\n**The Verification: a period of time of tracking**\n\nTo see if the workflow actually helps, I tracked the results: which content was saved, which triggered replies, which was long but unread. The tracking wasn't about chasing virality; it was about locating friction—like a platform where I always overwrote, or a point where I hesitated on the boundary.\n\n**The Value: Less friction, not more posts**\n\nThe biggest shift: publishing no longer feels like a heavy task. Before, between idea and publish there were many decisions—what to write, how to write, where to post. Now the process handles those. The value isn't posting more every day; it's making each publish smoother.\n\nClosing: If you save a lot but publish little, try this: extract a point, mark boundaries, rewrite per platform, and track the results. A content workflow isn't a template; it's a system that reduces hesitation.",
            "wechat_moments": "Used to copy the same text to every platform and each one felt half-done. Now I extract a point, mark boundaries, and rewrite per platform. after using it of tracking, the real win is less friction, not more posts.",
            "weibo": "Tested a content workflow over time: from daily saves, pick one quotable point, mark evidence and boundary, then rewrite per platform—Zhihu for cause, Xiaohongshu for steps, WeChat for narrative, Moments for a real reason. The real value? Less friction from idea to publish. #ContentWorkflow",
            "bilibili": "Video script: My short Content Workflow Experiment\n\n0:00-0:10\nShot: Desk covered with printed articles, a notebook, phone.\nVoiceover: Every day we save a lot, but publish very little. This month I tested a new workflow.\nCaption: From save to publish, less friction\n\n0:10-0:30\nShot: Screen recording of copying the same text to multiple platforms, then comparing tabs, all looking incomplete.\nVoiceover: I used to copy the same text everywhere, add tags, and every platform felt half-finished.\nCaption: Copy-paste ≠ adaptation\n\n0:30-1:00\nShot: Whiteboard animation with three steps: Extract point, Mark evidence & boundary, Rewrite per platform.\nVoiceover: I changed to: first extract one quotable point, then mark its original evidence and the boundary I can't cross, then rewrite for each platform.\nCaption: Three steps: point, boundary, adapt\n\n1:00-1:30\nShot: Split screen showing five platforms with labels: Zhihu—cause/effect; Xiaohongshu—steps; WeChat—narrative; Moments—real reason; Short video—visuals/voiceover.\nVoiceover: Each platform has a job: Zhihu gets background and causality, Xiaohongshu gets steps, WeChat keeps the full story, Moments shares a genuine reason, short video starts with visuals and voiceover.\nCaption: One platform, one job\n\n1:30-2:00\nShot: Calendar with checkmarks over time, three tag stickers: saved, replies, long but unread.\nVoiceover: To verify, I tracked the results: which content was saved, which triggered replies, which was long but unread.\nCaption: a while of tracking to find friction\n\n2:00-2:30\nShot: Back to desk, a sticky note reading “Less friction”.\nVoiceover: The real value isn't posting more; it's reducing friction between idea and publish. If you also save more than you publish, try this flow.\nCaption: Less friction, not more volume\nCTA: What's your biggest publishing friction? Comment below.",
            "douyin": "Short video script: Stop Letting Your Saves Go to Waste\n\n0:00-0:05\nShot: Phone screen scrolling a huge bookmark list.\nVoiceover: Bookmarks overflowing, but posts near zero.\nCaption: Saves gathering dust?\n\n0:05-0:15\nShot: Quick demo of copying to multiple platforms, each looking messy, “Draft” stickers.\nVoiceover: I used to copy-paste to every platform, and they all looked half-baked.\nCaption: Copy-paste = half-baked posts\n\n0:15-0:30\nShot: Hand-drawn flowchart: Point → Evidence/Boundary → Platform rewrite.\nVoiceover: Now I extract one quotable point, mark evidence and the boundary I can't cross, then rewrite per platform.\nCaption: Three steps: point, boundary, adapt\n\n0:30-0:50\nShot: Split screen with platform icons and rewrite notes.\nVoiceover: Zhihu gets cause, Xiaohongshu gets steps, WeChat gets the full story, Moments shares a real reason, short video starts with visuals and voiceover.\nCaption: Different platform, different angle\n\n0:50-1:05\nShot: Calendar with a period of time of tracking, three labels.\nVoiceover: I tracked the results: saved, replies, long but unread. The real win is less friction, not more posts.\nCaption: Value = less friction\nCTA: Follow for how to extract a quotable point next.",
            "kuaishou": "Kuaishou video script: A Down-to-Earth Way to Turn Saves Into Posts\n\n0:00-0:08\nShot: Simple notebook and phone, paper showing “Saves → Posts”.\nVoiceover: Folks, I tried a method to turn daily saves into something worth posting.\nCaption: Saves to posts, give it a try\n\n0:08-0:20\nShot: Showing copy-paste to many platforms, screen messy.\nVoiceover: Before, I copied the same text to all platforms, and each one looked like a draft, no one read.\nCaption: Copy-paste won't work\n\n0:20-0:38\nShot: Chalkboard with three boxes: Extract point, Mark boundary, Rewrite.\nVoiceover: Now I find one point I can say, mark the evidence and the line I can't cross, then rewrite for each platform.\nCaption: Point, boundary, rewrite\n\n0:38-0:55\nShot: Showing how to rewrite for each platform: Zhihu—why, Xiaohongshu—how, WeChat—full story, Moments—real talk, Short video—visuals first.\nVoiceover: Zhihu writes the why, Xiaohongshu writes the how, WeChat writes the whole story, Moments says the real reason, short video thinks visuals first.\nCaption: Each platform, its own way\n\n0:55-1:10\nShot: Usage calendar with marks and notes.\nVoiceover: I tracked a while: what got saved, what got replies, what got ignored. Lesson: not more posts, just less friction.\nCaption: Less friction, better flow\nCTA: Like if useful, tell me your publishing flow in comments.",
            "linkedin": "after using it of tracking, I turned my daily saves—articles, meeting notes, idea fragments—into a repeatable content workflow. The core: extract one quotable point, mark evidence and boundaries, then rewrite per platform. Zhihu gets cause/effect, Xiaohongshu gets steps, WeChat keeps narrative, Moments shares a real reason, short video starts with visuals. The outcome wasn't more volume; it was less friction from idea to publish. If you create content, start by reducing friction, not adding output. #ContentStrategy #Workflow #Publishing",
            "threads": "I used to copy-paste the same text to every platform, and they all felt half-finished. Now I extract a point, mark boundaries, rewrite per platform, and track the results. The real win: less friction, not more posts.",
            "reddit": "Title: Anyone else built a low-friction content workflow from daily saves?\n\nBody: I save articles, meeting notes, and idea fragments daily, but publishing always felt like a chore. previously I tried a new process: extract one quotable point from the saves, mark its original evidence and the boundary I can't cross, then rewrite per platform (Zhihu gets cause/effect, Xiaohongshu gets steps, WeChat gets full narrative, Moments gets a real reason, short video starts with visuals). Then I tracked the results: which content got saved, which got replies, which was long but unread. Turns out the biggest benefit was reducing friction between idea and publish, not posting more. Do you have a content workflow? How do you lower publishing friction?",
            "tiktok": "TikTok script: Why Your Saves Never Turn Into Posts\n\n0:00-0:06\nShot: Phone bookmarks showing “999+”.\nVoiceover: You save everything, but publish almost nothing?\nCaption: 999+ saves, 0 posts\n\n0:06-0:16\nShot: Quick copy-paste to all platforms, each looks off.\nVoiceover: I used to do that—copy the same text everywhere, and each platform looked half-done.\nCaption: Copy-paste, all half-done\n\n0:16-0:32\nShot: Animated three steps: Extract point, mark evidence/boundary, rewrite per platform.\nVoiceover: Then I changed: extract one quotable point, mark the original evidence and the boundary not to cross, rewrite for each platform.\nCaption: A three-step workflow\n\n0:32-0:48\nShot: Split screen with five platforms and their rewrite focus.\nVoiceover: Zhihu gets background and causality, Xiaohongshu gets steps, WeChat gets full narrative, Moments gets a real reason, short video gets visuals first.\nCaption: Every platform gets its own version\n\n0:48-1:02\nShot: Calendar with tracking: saved, replies, unread.\nVoiceover: I tracked the results—what got saved, what got replies, what got ignored. The real value? Less friction, not more posts.\nCaption: Less friction > more volume\nCTA: Follow for more content workflow tips.",
            "youtube": "YouTube video script: How I Designed a Low-Friction Content Workflow\n\n0:00-0:15\nShot: Desk with printed articles, notebook, phone; slow pan.\nVoiceover (VO): Every day we collect articles, meeting notes, and ideas. But very few become published pieces, and those that do often feel half-finished.\nCaption: From save to publish—what's in between?\n\n0:15-0:40\nShot: Screen recording of copy-pasting to multiple platforms, then side-by-side comparison showing repetition and mismatch.\nVO: I used to copy the same text to every platform, add a few tags, and each one felt incomplete. The issue wasn't the content; it was the lack of platform adaptation.\nCaption: Copy-paste is not adaptation\n\n0:40-1:10\nShot: Whiteboard animation with three steps: 1) Extract a quotable point; 2) Mark original evidence and boundary; 3) Rewrite per platform.\nVO: So I built a process. First, extract one point from daily saves that can be quoted. Second, mark its evidence and the boundary you can't cross, so rewriting stays honest. Third, adapt for each platform.\nCaption: Three steps: point, boundary, adapt\n\n1:10-1:50\nShot: Split screen showing five platforms with labels: Zhihu—cause & effect; Xiaohongshu—steps & checklist; WeChat—full narrative; Moments—real reason; Short video—visuals & voiceover.\nVO: Each platform has a role: Zhihu gets background and causality, Xiaohongshu gets steps, WeChat keeps the narrative, Moments shares a genuine reason, short video starts with visuals and voiceover. Every deliverable becomes complete.\nCaption: One platform, one role\n\n1:50-2:30\nShot: Calendar close-up, a period of time of checkmarks, with three tags: saved, replies, long but unread.\nVO: To test if this works, I tracked the results: which content was saved, which sparked replies, which was long but ignored. Tracking helped me find friction, not chase growth.\nCaption: a while of tracking\n\n2:30-3:00\nShot: Back to desk, a sticky note “Reduce friction”, final hold.\nVO: The core value is not posting more; it's reducing the friction between idea and publish. If you save more than you publish, try this flow.\nCaption: Reduce friction, publish smoothly\nCTA: Share your biggest publishing friction in the comments.",
            "medium": "Title: From Save Folder to Publishing Pipeline: My short Experiment in Reducing Friction\n\nLead: We save articles, meeting notes, and ideas every day. Few become posts; those that do often feel half-finished. I spent a while building a repeatable content workflow, and the core lesson is: stop optimizing for volume, start reducing friction.\n\nBody:\n\n**Why every platform feels like a draft**\n\nFor a long time, I copied the same text to multiple platforms and added tags. The results were predictable: Zhihu answers without cause, Xiaohongshu notes without steps, WeChat articles without narrative arc, Moments that sounded like ads. The problem wasn't the content quality; it was the absence of platform adaptation and viewpoint boundaries.\n\n**The workflow: pull, bound, rewrite**\n\nMy system has three stages. First, pull one quotable point from the day's saves. It could be from an article, a meeting note, or a stray thought, but it must be a single clear idea. Second, bound that point: mark the original evidence and the line you cannot cross—no invented stats, no overclaimed outcomes. This keeps the rewrite honest. Third, rewrite for each platform according to a simple rule: Zhihu gets background and causality, Xiaohongshu gets steps and checklists, WeChat gets the full narrative, Moments gets one genuine reason, short video gets visuals and voiceover first. Each platform receives a complete piece, not a fragment.\n\n**Verification through tracking**\n\nTo see if the workflow actually helped, I tracked the results. I recorded three signals: which content was saved, which triggered replies, and which was long but unread. The goal wasn't to chase viral hits; it was to identify friction. For instance, I noticed I kept overwriting on certain platforms, so I forced shorter rewrites. Or I hesitated on boundaries, so I clarified evidence first.\n\n**The real value: less friction**\n\nThe biggest change was psychological: publishing stopped feeling like a burden. Before, every post required multiple decisions—what to write, how to phrase it, where to put it. Now the workflow handles those. The value isn't posting more every day; it's making each publish smoother. If you save a lot and publish little, try the pull-bound-rewrite-track loop over time. You may find the same.",
            "facebook": "I ran a experiment to turn my daily saves—articles, meeting notes, idea fragments—into a repeatable content workflow. The method: extract one quotable point, mark evidence and boundaries, then rewrite per platform (Zhihu for cause, Xiaohongshu for steps, WeChat for narrative, Moments for a real reason, short video for visuals first). After tracking, the real benefit wasn't more posts; it was less friction from idea to publish. If content creation feels heavy, try this flow.",
            "instagram": "📌 Title: Save everything, publish nothing? Build a repeatable content workflow\n\nPain point: Your bookmarks are full, but every platform gets the same copy-paste draft, and none of them feel finished.\n\nMy workflow:\n1️⃣ Pull one quotable point from today's saves\n2️⃣ Mark the original evidence and the boundary you can't cross\n3️⃣ Rewrite per platform: Zhihu for cause, Xiaohongshu for steps, WeChat for full story, Moments for a real reason, short video for visuals first\n4️⃣ track the results: saved, replies, long but unread\n5️⃣ Adjust to reduce friction, not to increase volume\n\nPublishing becomes a smooth pipeline, not a daily struggle.\n\n#ContentWorkflow #NoteTaking #PublishingSystem #ReduceFriction #PlatformTips"
          },
          "hashtags": [
            "#ContentWorkflow",
            "#NoteTaking",
            "#PublishingSystem",
            "#ReduceFriction",
            "#PlatformAdaptation"
          ],
          "imagePrompt": "A warm-toned overhead workspace with printed article clippings, meeting notes, and sticky notes on the left, a hand-drawn flowchart connecting platform icons in the center, and a phone on the right showing a draft, emphasizing the idea-to-publish path with reduced friction."
        }
      }
    },
    {
      "id": "repo-promotion",
      "label": "This repository promotion",
      "labelZh": "本仓库宣发实战",
      "sourceUrl": "https://github.com/lhmd/dsh-promotion-toolkit",
      "source": "我们把一个 DeepSeek Harness 插件做成了通用内容宣发工具。它不只服务于某个框架的首发，也适合产品故事、开源项目、文章、课程、活动和个人经验。输入一篇长文后，工具先抽取核心观点、可引用证据和需要核验的风险，再为小红书、知乎、公众号、朋友圈、微博、B 站、抖音、快手、X、Threads、LinkedIn、Reddit、TikTok、YouTube、Medium、Facebook 和 Instagram 分别生成内容。知乎是 Markdown 科普，小红书是带适量 emoji 的可保存清单，公众号保留长文叙事，朋友圈像朋友分享，视频平台包含分镜、口播、字幕和 CTA。我们用 deepseek-v4-pro 跑了双语长文案例，展示页和 README 直接提供可复制的结果。",
      "baseline": {
        "language": "zh",
        "score": 66,
        "signals": [
          "specificity",
          "clear topic",
          "quotable length"
        ],
        "evidence": [
          "我们用 deepseek-v4-pro 跑了双语长文案例，展示页和 README 直接提供可复制的结果。",
          "输入一篇长文后，工具先抽取核心观点、可引用证据和需要核验的风险，再为小红书、知乎、公众号、朋友圈、微博、B 站、抖音、快手、X、Threads、LinkedIn、Reddit、TikTok、YouTube、Medium、Facebook 和 Instagram 分别生成内容。",
          "知乎是 Markdown 科普，小红书是带适量 emoji 的可保存清单，公众号保留长文叙事，朋友圈像朋友分享，视频平台包含分镜、口播、字幕和 CTA。"
        ],
        "platformCount": 17
      },
      "polished": {
        "zh": {
          "tagline": "一篇文章，17个平台，自动生成适配内容",
          "coreIdea": "输入一篇长文，这个工具先抽取核心观点、可引用证据和需要核验的风险，再为小红书、知乎、公众号、微博、B站、抖音、X、LinkedIn等17个平台生成原生风格的内容。知乎是Markdown科普，小红书是可保存清单，公众号保留长文叙事，视频平台包含分镜、口播、字幕和CTA。项目用deepseek-v4-pro跑了双语案例，展示页和README直接可复制。",
          "titles": [
            "一篇文章，17种表达：内容宣发不再靠手动改写",
            "从长文到多平台文案，这个开源工具帮你自动生成",
            "小红书清单、知乎科普、公众号长文，一个工具全搞定"
          ],
          "hook": "写完深度长文只是开始，真正的痛苦是把同一篇内容改写成十几个平台的风格。这个工具可以帮你自动完成。",
          "quote": "输入一篇长文后，工具先抽取核心观点、可引用证据和需要核验的风险，再为17个平台分别生成内容。",
          "platforms": {
            "x": "写长文后还要手动改成 X 的短帖？这个开源工具输入长文，自动抽观点、标风险，生成适合 X 的简洁版本。结果在 README 可直接复制。仓库：https://github.com/lhmd/dsh-promotion-toolkit",
            "xiaohongshu": "📌 长文不用再手动改17个平台！我也就用它省了80%重复劳动\n谁懂啊，写完一篇深度长文，还要给小红书、知乎、公众号、抖音、B站各写一遍，风格还不一样，真的会谢😭\n后来发现了这个开源工具，输入长文，它自动帮你：\n✅ 抽核心观点和可引用证据\n✅ 标出需要核验的风险\n✅ 生成17个平台的原生文案\n✅ 小红书是可保存清单，知乎是Markdown科普，公众号是长文叙事\n✅ 视频平台连分镜、口播、字幕、CTA都安排好了\n直接去GitHub复制结果：\n🔗 https://github.com/lhmd/dsh-promotion-toolkit\n#内容运营 #多平台分发 #开源工具 #效率神器 #自媒体 #长文改写",
            "zhihu": "# 如何把一篇长文高效分发到17个内容平台？一个开源工具的实践\n\n## 结论\n这个工具（仓库：dsh-promotion-toolkit）的核心价值是：输入一篇长文后，自动提取核心观点、可引用证据和需要核验的风险，然后生成适配17个平台的原生风格内容。不是简单套模板，而是针对小红书、知乎、公众号、视频平台等分别设计结构。项目已经用 deepseek-v4-pro 跑了双语长文案例，展示页和 README 里的结果是可直接复制的。\n\n## 背景\n内容创作者经常面临一个问题：一篇深度文章完成后，分发的成本很高。知乎需要 Markdown 科普结构，小红书需要带 emoji 的可保存清单，公众号需要保留长文叙事，朋友圈需要像朋友分享的短句，B站/抖音/快手/TikTok/YouTube 需要分镜、口播、字幕和 CTA。每个平台的受众习惯和算法偏好不同，纯手动改写耗时且容易遗漏平台特性。\n\n## 方法\n该工具的处理流程分三步：\n1. 输入长文后，先抽取核心观点、可引用证据，并标记需要核验的风险，避免直接生成错误信息。\n2. 根据平台特性生成不同格式：知乎输出 Markdown 科普，小红书生成可保存清单，公众号保留长文叙事，朋友圈生成短分享，视频平台包含分镜、口播、字幕和 CTA。\n3. 使用 deepseek-v4-pro 生成双语案例，展示页和 README 提供可复制的结果，方便直接拿来用。\n\n## 限制\n- 该工具目前是通用内容宣发工具，并不是某个框架的专属首发工具；如果源内容本身是产品发布，需自行判断信息准确性。\n- 生成结果依赖输入长文的质量，抽取的证据和风险标记需要人工复核。\n- 平台覆盖虽然多，但每个平台的算法和社区规范变化较快，需要定期更新提示词模板。\n- 项目当前公开的是展示页和 README 案例，实际部署和使用需参考仓库说明。\n\n项目地址：https://github.com/lhmd/dsh-promotion-toolkit",
            "wechat": "标题：一篇长文，如何自动变成17个平台的定制内容？\n\n导语：内容分发最累的不是写作，而是改写。这篇文章介绍一个开源工具，它把长文处理成适配不同平台的文案，从知乎到抖音，从朋友圈到LinkedIn。\n\n一、问题：多平台分发的重复劳动\n写完一篇深度长文，创作者往往要再花数小时改写：知乎要 Markdown 科普，小红书要可保存清单，公众号保留长文叙事，朋友圈要短分享，视频平台还要分镜、口播、字幕。每个平台的语气、结构、CTA 都不一样，手动操作极易出错。\n\n二、工具的工作流程：抽取、标记、生成\n这个开源工具的处理方式很直接：输入一篇长文后，它先抽取核心观点、可引用证据，并标出需要核验的风险，防止生成错误信息。然后根据平台特性生成不同格式——知乎是 Markdown 科普，小红书是带适量 emoji 的清单，公众号保留长文叙事，朋友圈像朋友分享，视频平台包含分镜、口播、字幕和 CTA。\n\n三、平台差异化：为什么不是简单套模板\n很多改写工具只是替换关键词，但该工具针对每个平台重新组织内容。例如小红书版本会强化清单感和可保存性，知乎版本保持清晰结构，视频平台版本会列出具体分镜和时间戳。这种差异来自对平台用户习惯的理解。\n\n四、案例与可复制结果\n项目用 deepseek-v4-pro 跑了双语长文案例，展示页和 README 直接提供可复制的结果。你可以打开仓库，复制一段小红书文案或知乎回答，稍作调整就能用。\n\n五、使用建议与注意\n如果你也想减少多平台分发的工作量，可以先看看仓库中的案例。注意：生成结果仍需人工核验风险点，平台规则变化时需更新提示词。\n\n结尾：项目地址：https://github.com/lhmd/dsh-promotion-toolkit",
            "wechat_moments": "发现一个长文转多平台文案的工具，自动生成小红书清单、知乎科普、公众号长文，连视频分镜都有。已试，README 可直接复制。🔗 https://github.com/lhmd/dsh-promotion-toolkit",
            "weibo": "写长文后还要手动改17个平台？这个开源工具输入长文，自动抽观点、标风险，生成小红书清单、知乎科普、公众号长文和视频分镜。结果在 README 可直接复制。🔗 https://github.com/lhmd/dsh-promotion-toolkit #内容宣发 #开源工具",
            "bilibili": "🔥 视频脚本：长文一键分发17个平台，这个开源工具太省事了\n时长：约1分钟\n\n分镜与口播：\n0:00-0:05 画面：电脑屏幕显示一篇长文，旁边堆满不同平台图标。口播：写完一篇深度长文，最头疼的是什么？是把它改写成小红书、知乎、B站、公众号……十几遍。字幕：长文分发到底多麻烦？\n0:05-0:15 画面：工具运行界面，长文输入，自动输出多个平台卡片。口播：这个开源工具，输入一篇长文，先自动抽取核心观点、可引用证据，还会标出需要核验的风险。字幕：自动抽取观点+证据+风险\n0:15-0:30 画面：展示小红书清单、知乎 Markdown、公众号长文、朋友圈短句等对比。口播：然后生成17个平台的原生内容：小红书是可保存清单，知乎是 Markdown 科普，公众号保留长文叙事，朋友圈就像朋友分享。字幕：17种平台风格自动生成\n0:30-0:45 画面：视频平台脚本展示，包含分镜、口播、字幕、CTA。口播：视频平台也不落下，分镜、口播、字幕、CTA 都给你列好，直接拿去拍。字幕：视频脚本也自动生成\n0:45-0:55 画面：GitHub 仓库页面，README 和展示页。口播：项目用 deepseek-v4-pro 跑了双语案例，展示页和 README 直接可复制。链接在评论区。字幕：案例可复制\n\nCTA：去 GitHub 仓库看看：https://github.com/lhmd/dsh-promotion-toolkit",
            "douyin": "🔥 30秒视频脚本：长文自动改17个平台\n0-2秒：痛点画面，长文和一堆平台图标。口播：写长文最烦的是什么？改写！字幕：多平台改写有多累？\n2-8秒：工具输入长文。口播：这个工具输入长文，自动抽观点、标风险，生成17个平台文案。字幕：自动抽观点+生成\n8-18秒：平台风格对比。口播：小红书是清单，知乎是科普，公众号长文，朋友圈短句，视频还有分镜字幕。字幕：17种风格\n18-25秒：README 展示。口播：案例直接可复制，链接在评论区。字幕：可复制结果\nCTA：https://github.com/lhmd/dsh-promotion-toolkit",
            "kuaishou": "视频脚本（40秒）：长文多平台自动改写\n0-3秒：痛点：长文和平台图标。口播：一篇长文要发17个平台，改写太累了。字幕：多平台改写有多累？\n3-10秒：工具界面。口播：这个开源工具输入长文，自动抽核心观点、可引用证据，还标风险。字幕：自动抽取观点+风险\n10-20秒：平台风格。口播：小红书清单、知乎科普、公众号长文、视频分镜，全都有。字幕：17种风格自动生成\n20-30秒：结果展示。口播：README 里案例可直接复制，省事。字幕：可复制案例\n30-40秒：CTA。口播：链接在评论区。字幕：仓库地址\nCTA：https://github.com/lhmd/dsh-promotion-toolkit",
            "linkedin": "内容团队常被多平台分发拖慢节奏。这个开源工具输入一篇长文后，自动抽取核心观点、可引用证据和需核验风险，并为知乎、小红书、公众号、视频平台等17个渠道生成适配内容。不是简单替换关键词，而是按平台特性重构：知乎是 Markdown 科普，小红书是可保存清单，公众号保留叙事，视频平台含分镜、口播、字幕和 CTA。项目用 deepseek-v4-pro 跑了双语案例，展示页和 README 可直接复制使用。适合内容运营、产品经理、开源项目维护者参考。仓库：https://github.com/lhmd/dsh-promotion-toolkit",
            "threads": "长文改写多平台太累？这个开源工具自动生成17个平台文案，连视频分镜都有。README 有可复制案例。🔗 https://github.com/lhmd/dsh-promotion-toolkit",
            "reddit": "分享一个我最近在用的开源工具：输入长文后，它自动抽取观点、证据和风险，生成适配17个平台的文案（小红书清单、知乎科普、公众号长文、视频脚本等）。我用它处理了几篇技术文章，省了不少重复劳动。它用 deepseek-v4-pro 跑了双语案例，README 里结果可复制。有人用过类似的工具吗？或者觉得这种自动改写有什么坑？欢迎聊聊。仓库：https://github.com/lhmd/dsh-promotion-toolkit",
            "tiktok": "🔥 TikTok 视频脚本：长文自动变17个平台内容\n0-2秒：痛点：长文和平台图标。口播：写一篇长文，却要手动改成17个平台的风格？太累了！字幕：长文分发的痛\n2-8秒：工具输入。口播：这个工具输入长文，自动抽观点、标风险，然后生成17个平台文案。字幕：自动生成多平台文案\n8-15秒：平台风格展示。口播：小红书是清单，知乎是科普，公众号是长文，视频平台有分镜和口播。字幕：每种平台都不一样\n15-20秒：结果。口播：案例在 README 可直接复制，链接在简介。字幕：可复制结果\nCTA：https://github.com/lhmd/dsh-promotion-toolkit",
            "youtube": "视频脚本：如何把一篇长文自动改写成17个平台内容？\n时长：3分钟\n\n开头（0:00-0:15）：\n画面：创作者面对屏幕，长文和多个平台图标。口播：如果你经常写长文，一定知道多平台分发有多痛苦。今天介绍一个开源工具，能自动帮你生成17个平台的内容。字幕：长文多平台分发自动化\n\n工具原理（0:15-1:00）：\n画面：工具流程动画，输入长文，抽取观点、证据、风险。口播：输入一篇长文后，工具先抽取核心观点、可引用证据，并标出需要核验的风险。然后为每个平台生成不同格式。字幕：抽取观点+证据+风险\n\n平台差异（1:00-2:00）：\n画面：展示小红书清单、知乎 Markdown、公众号长文、朋友圈短句、视频分镜。口播：知乎生成 Markdown 科普，小红书生成可保存清单，公众号保留长文叙事，朋友圈像朋友分享，视频平台包含分镜、口播、字幕和 CTA。字幕：17种平台风格\n\n案例与使用（2:00-2:40）：\n画面：GitHub 仓库 README 和展示页。口播：项目用 deepseek-v4-pro 跑了双语长文案例，展示页和 README 直接提供可复制结果。你可以复制后稍作调整。字幕：可复制案例\n\n结尾 CTA（2:40-3:00）：\n画面：仓库链接。口播：链接在视频简介和评论区，欢迎去试试。字幕：仓库地址\nCTA：https://github.com/lhmd/dsh-promotion-toolkit",
            "medium": "标题：从一篇长文到17个平台：一个开源内容宣发工具的实践\n\n导语：内容分发中，最耗时的往往不是写作本身，而是把一篇深度长文改写成不同平台喜欢的格式。这个开源工具自动化了这个过程。\n\n正文：\n多平台内容分发的难题在于，每个平台都有独特的表达习惯：知乎用户期待结构清晰的科普，小红书用户喜欢可保存的清单和 emoji，公众号读者习惯长文叙事，视频平台需要分镜和口播。手动为每个平台重写，不仅耗时，还容易丢失平台特性。\n\n这个工具的处理流程是：输入长文后，先抽取核心观点、可引用证据，并标出需要核验的风险。然后为17个平台生成内容，包括小红书、知乎、公众号、朋友圈、微博、B站、抖音、快手、X、Threads、LinkedIn、Reddit、TikTok、YouTube、Medium、Facebook、Instagram。每个平台的输出都经过专门设计：知乎是 Markdown 科普，小红书是可保存清单，公众号保留长文叙事，视频平台包含分镜、口播、字幕和 CTA。\n\n项目用 deepseek-v4-pro 跑了双语长文案例，展示页和 README 提供了可直接复制的结果。这对内容运营和开源项目维护者尤其有用，可以减少重复劳动，把精力放回创作本身。\n\n当然，自动生成的内容仍需人工复核，特别是风险点和平台规则变化。但这个工具提供了一个很好的起点。\n\n项目地址：https://github.com/lhmd/dsh-promotion-toolkit",
            "facebook": "写完长文还要逐个平台改写？这个开源工具可以自动生成17个平台的内容，从知乎科普到小红书清单，再到视频脚本。案例在 README 可直接复制。看看：https://github.com/lhmd/dsh-promotion-toolkit",
            "instagram": "✨ 长文不用再手动改17个平台！这个工具替你自动生成\n每次写完深度长文，还要为小红书、知乎、B站、抖音分别改写，风格完全不一样，真的会累😩\n这个开源工具帮你：\n✅ 抽出核心观点和可引用证据\n✅ 标记需要核验的风险\n✅ 生成17个平台的原生文案\n✅ 小红书是可保存清单，知乎是Markdown科普\n✅ 视频平台连分镜、字幕、CTA都有\n去GitHub复制结果：\n🔗 https://github.com/lhmd/dsh-promotion-toolkit\n#ContentRepurposing #OpenSource #Productivity #ContentCreator #MultiPlatform"
          },
          "hashtags": [
            "内容宣发",
            "多平台分发",
            "开源工具",
            "效率提升",
            "内容运营"
          ],
          "imagePrompt": "一幅分屏插画，左侧是一篇长文，右侧是多个平台的内容卡片，包含小红书、知乎、公众号、B站、抖音、X、LinkedIn、TikTok、YouTube等图标；干净扁平设计，柔和蓝白配色，无文字。"
        },
        "en": {
          "tagline": "One long article, 17 platform-native drafts — generated automatically",
          "coreIdea": "Feed it a long article and the tool extracts core viewpoints, quotable evidence, and risks to verify, then generates content for 17 platforms including Xiaohongshu, Zhihu, WeChat, Weibo, Bilibili, Douyin, X, LinkedIn, TikTok, YouTube, Medium, Facebook, and Instagram. Each output is structured for the platform: Zhihu gets Markdown explainers, Xiaohongshu gets saveable checklists, WeChat keeps long-form narrative, and video platforms get shots, voiceover, captions, and CTA. The project includes bilingual long-form examples run with deepseek-v4-pro, with copyable results in the showcase and README.",
          "titles": [
            "One Article, 17 Platforms: Stop Rewriting Manually",
            "From Long-Form to Every Channel: An Open Source Repurposing Tool",
            "Xiaohongshu Checklists, Zhihu Explainers, Video Scripts — All from One Source"
          ],
          "hook": "You wrote a great long-form piece. Now the real work begins: rewriting it for 17 different platforms. This tool does that automatically.",
          "quote": "After you input a long article, the tool extracts core viewpoints, quotable evidence, and risks to verify, then generates content for 17 platforms separately.",
          "platforms": {
            "x": "Tired of rewriting your long article for every platform? This open source tool inputs a long piece, extracts key points and risks, then generates platform-native drafts for X, LinkedIn, Reddit, and 14 more. Copy the results from the README. Repo: https://github.com/lhmd/dsh-promotion-toolkit",
            "xiaohongshu": "📌 Save this if you hate rewriting long posts for every platform\nYou know the pain: one deep article, then you have to adapt it for Xiaohongshu, Zhihu, WeChat, Douyin, Bilibili… all in different styles. Exhausting 😩\nThis open source tool helped me automate that:\n✅ Extracts core points and quotable evidence\n✅ Flags risks to verify\n✅ Generates 17 platform-native drafts\n✅ Xiaohongshu gets a saveable checklist, Zhihu gets Markdown explainer\n✅ Video platforms get shots, voiceover, captions, CTA\nCopy the ready-to-use results from GitHub:\n🔗 https://github.com/lhmd/dsh-promotion-toolkit\n#ContentRepurposing #OpenSource #Productivity #CreatorTools #MultiPlatform",
            "zhihu": "# How to Efficiently Distribute One Long Article to 17 Platforms: An Open Source Tool\n\n## Conclusion\nThis tool (repo: dsh-promotion-toolkit) takes a long article, extracts core viewpoints, quotable evidence, and risks to verify, then generates platform-native content for 17 channels. It doesn't just swap keywords; it restructures for each platform. The project includes bilingual examples run with deepseek-v4-pro, and the README/showcase contain copyable results.\n\n## Background\nContent creators often find distribution to be the most time-consuming part. Zhihu needs Markdown explainers, Xiaohongshu needs saveable checklists with emojis, WeChat articles need long-form narrative, Moments need short friend-style shares, and video platforms need shots, voiceover, captions, and CTAs. Each platform has different audience habits, and manual rewriting is error-prone.\n\n## Method\nThe tool's process has three steps:\n1. After input, extract core viewpoints, quotable evidence, and mark risks that need verification.\n2. Generate platform-specific formats: Zhihu outputs Markdown explainers, Xiaohongshu produces saveable checklists, WeChat keeps long-form narrative, Moments creates short shares, video platforms include shots, voiceover, captions, and CTA.\n3. Use deepseek-v4-pro for bilingual examples; showcase and README provide copyable results.\n\n## Limits\n- The tool is a general content repurposing tool, not a launch tool for a specific framework; verify facts if the source is a product launch.\n- Output quality depends on the input article; extracted evidence and risk flags still need human review.\n- Platform algorithms and community norms change; prompt templates need periodic updates.\n- The public repository currently provides showcase and README examples; deployment requires checking the repo.\n\nProject URL: https://github.com/lhmd/dsh-promotion-toolkit",
            "wechat": "Title: How to Turn One Long Article into 17 Platform-Specific Drafts Automatically\n\nLead: The hardest part of content distribution isn't writing — it's rewriting. This open source tool takes a long article and produces platform-native copy for Zhihu, Xiaohongshu, WeChat, video platforms, and more.\n\n1. The problem: repetitive multi-platform rewriting\nAfter finishing a deep article, creators often spend hours adapting it. Zhihu requires Markdown explainers, Xiaohongshu needs saveable checklists, WeChat keeps long-form narrative, Moments need short shares, and video platforms need shots, voiceover, captions, and CTAs. Each platform's tone and structure differ, making manual work tedious.\n\n2. How the tool works: extract, flag, generate\nThe tool first extracts core viewpoints and quotable evidence, and flags risks to verify. Then it generates different formats for each of 17 platforms. For example, Zhihu gets Markdown explainers, Xiaohongshu gets checklists with a few emojis, WeChat articles keep long-form narrative, and video scripts include shots, voiceover, captions, and CTA.\n\n3. Why platform-specific design matters\nMany tools only replace keywords, but this tool restructures content for each platform. The Xiaohongshu version emphasizes checklist saves, the Zhihu version maintains clear structure, and the video version provides shot-by-shot instructions. This reflects real differences in user expectations.\n\n4. Examples and copyable results\nThe project used deepseek-v4-pro to run bilingual long-form examples. The showcase and README provide copyable results, so you can grab a ready-to-use Xiaohongshu checklist or Zhihu answer and tweak it.\n\n5. Practical notes\nIf you want to reduce multi-platform distribution workload, check the repo examples. Remember to review risk flags and update prompts as platform rules change.\n\nEnding: Repo: https://github.com/lhmd/dsh-promotion-toolkit",
            "wechat_moments": "Found a tool that turns one long article into platform-specific drafts for 17 channels. Generated Xiaohongshu checklists, Zhihu explainers, and video scripts all from one input. Check the README for copyable examples. 🔗 https://github.com/lhmd/dsh-promotion-toolkit",
            "weibo": "Tired of manually rewriting long posts for 17 platforms? This open source tool extracts key points and risks, then generates platform-specific drafts from Zhihu explainers to video scripts. Copyable results in the README. 🔗 https://github.com/lhmd/dsh-promotion-toolkit #ContentRepurposing #OpenSource",
            "bilibili": "Video script: Turn one long article into 17 platform drafts automatically\nDuration: ~1 minute\n\nShots & voiceover:\n0:00-0:05 Visual: A long article on screen with multiple platform icons. Voiceover: You finished a deep article — now the hard part: rewriting for Xiaohongshu, Zhihu, Bilibili, WeChat… over and over. Caption: Multi-platform rewriting is painful\n0:05-0:15 Visual: Tool interface, input article, output cards. Voiceover: This open source tool extracts core points, quotable evidence, and flags risks to verify. Caption: Extract points + evidence + risks\n0:15-0:30 Visual: Side-by-side Xiaohongshu checklist, Zhihu Markdown, WeChat article, Moments short share. Voiceover: Then it generates 17 platform-native versions: saveable checklists for Xiaohongshu, Markdown explainers for Zhihu, long-form for WeChat, short shares for Moments. Caption: 17 platform styles auto-generated\n0:30-0:45 Visual: Video platform script with shots, voiceover, captions, CTA. Voiceover: Video platforms get full scripts with shots, voiceover, captions, and CTA — ready to shoot. Caption: Video scripts included\n0:45-0:55 Visual: GitHub repo and README. Voiceover: Bilingual examples run with deepseek-v4-pro are in the README, copyable. Link in description. Caption: Copyable examples\n\nCTA: https://github.com/lhmd/dsh-promotion-toolkit",
            "douyin": "30-second video script: One long article, 17 platform drafts\n0-2s: Pain point: long article and platform icons. VO: Writing a long article is easy; rewriting for 17 platforms is not. Caption: Multi-platform rewriting is hard\n2-8s: Tool input. VO: This tool inputs a long article, extracts points and risks, generates 17 platform versions. Caption: Auto-generate 17 versions\n8-18s: Platform styles. VO: Xiaohongshu gets checklists, Zhihu gets explainers, WeChat gets long-form, video platforms get scripts. Caption: Platform-specific formats\n18-25s: README. VO: Copyable examples in the README, link in bio. Caption: Copyable results\nCTA: https://github.com/lhmd/dsh-promotion-toolkit",
            "kuaishou": "Video script (40s): Automate multi-platform content from one long article\n0-3s: Pain: article + platform icons. VO: One long article, 17 platforms to rewrite. Too much work. Caption: Rewriting is time-consuming\n3-10s: Tool process. VO: Input the article, tool extracts core points, evidence, and risks. Caption: Extract points + evidence + risks\n10-20s: Platform styles. VO: Xiaohongshu checklist, Zhihu Markdown, WeChat article, video script — all generated. Caption: 17 styles auto-generated\n20-30s: Results. VO: Check the README for copyable examples. Caption: Copyable examples\n30-40s: CTA. VO: Link in comments. Caption: Repo link\nCTA: https://github.com/lhmd/dsh-promotion-toolkit",
            "linkedin": "Content teams lose hours rewriting one long article for multiple platforms. This open source tool changes that: input a long-form piece, and it extracts core points, quotable evidence, and risks to verify, then generates platform-native drafts for 17 channels — Xiaohongshu checklists, Zhihu Markdown explainers, WeChat long-form, video scripts with shots and CTA. The repo includes bilingual examples run with deepseek-v4-pro, with copyable results in the README. Practical for content ops, product marketing, and open source maintainers. Repo: https://github.com/lhmd/dsh-promotion-toolkit",
            "threads": "One long article, 17 platform drafts — this open source tool generates Xiaohongshu checklists, Zhihu explainers, video scripts, and more. Copyable examples in the README. 🔗 https://github.com/lhmd/dsh-promotion-toolkit",
            "reddit": "I've been testing an open source tool that takes a long article and automatically generates platform-specific drafts for 17 platforms (Xiaohongshu checklists, Zhihu Markdown explainers, WeChat long-form, video scripts, etc.). It extracts core points, evidence, and risks first. The repo includes bilingual examples with copyable results. Has anyone else tried tools like this? What are the biggest pitfalls of auto-generated multi-platform content? Repo: https://github.com/lhmd/dsh-promotion-toolkit",
            "tiktok": "TikTok video script: Turn one long article into 17 platform drafts\n0-2s: Pain: article + platform icons. VO: You wrote a long article, but now you have to rewrite it for 17 platforms? Too much! Caption: Multi-platform rewriting is exhausting\n2-8s: Tool input. VO: This tool inputs the article, extracts points and risks, then generates 17 platform versions. Caption: Auto-generate platform drafts\n8-15s: Platform styles. VO: Xiaohongshu checklists, Zhihu explainers, WeChat long-form, video scripts with shots and voiceover. Caption: Each platform gets its own format\n15-20s: Results. VO: Copyable examples in the README, link in bio. Caption: Copyable results\nCTA: https://github.com/lhmd/dsh-promotion-toolkit",
            "youtube": "Video script: How to Automatically Repurpose One Long Article into 17 Platform Drafts\nDuration: ~3 minutes\n\nIntro (0:00-0:15):\nVisual: Creator at desk, long article and platform icons. VO: If you regularly write long-form content, you know multi-platform distribution is painful. Today I'm showing an open source tool that generates 17 platform-specific drafts automatically. Caption: Automate multi-platform content\n\nHow it works (0:15-1:00):\nVisual: Flow animation — input article, extract points, evidence, risks. VO: After you input a long article, the tool extracts core viewpoints, quotable evidence, and flags risks to verify. Then it generates different formats for each platform. Caption: Extract points + evidence + risks\n\nPlatform differences (1:00-2:00):\nVisual: Show Xiaohongshu checklist, Zhihu Markdown, WeChat article, Moments short share, video script. VO: Zhihu gets Markdown explainers, Xiaohongshu gets saveable checklists, WeChat keeps long-form narrative, Moments gets short shares, and video platforms get shots, voiceover, captions, and CTA. Caption: 17 platform-specific styles\n\nExamples and usage (2:00-2:40):\nVisual: GitHub repo README and showcase. VO: The project includes bilingual examples run with deepseek-v4-pro. The README and showcase have copyable results you can tweak. Caption: Copyable examples\n\nCTA (2:40-3:00):\nVisual: Repo link. VO: Link in description and comments. Go try it. Caption: Repo link\nCTA: https://github.com/lhmd/dsh-promotion-toolkit",
            "medium": "Title: From One Long Article to 17 Platform Drafts: An Open Source Approach to Content Repurposing\n\nLead: Most content creators spend more time rewriting than writing. This open source tool automates the tedious process of adapting a long piece for multiple platforms.\n\nThe challenge of multi-platform distribution is real. Zhihu expects structured explainers, Xiaohongshu wants saveable checklists with emojis, WeChat readers prefer long-form narrative, and video platforms need full scripts with shots and voiceover. Manually rewriting for each channel is time-consuming and prone to missing platform-specific nuances.\n\nThis tool addresses that by first extracting core viewpoints, quotable evidence, and risks to verify from the input article. It then generates content for 17 platforms: Xiaohongshu, Zhihu, WeChat, Moments, Weibo, Bilibili, Douyin, Kuaishou, X, Threads, LinkedIn, Reddit, TikTok, YouTube, Medium, Facebook, and Instagram. Each output is structured differently — Zhihu gets Markdown explainers, Xiaohongshu gets saveable checklists, WeChat keeps long-form, and video scripts include shots, voiceover, captions, and CTA.\n\nThe project ran bilingual long-form examples with deepseek-v4-pro, and the showcase and README contain copyable results. This is especially useful for content teams and open source maintainers who need to distribute updates across many channels without redoing the work.\n\nOf course, auto-generated content still requires human review, especially for risk flags and changing platform rules. But it provides a strong starting point.\n\nRepo: https://github.com/lhmd/dsh-promotion-toolkit",
            "facebook": "Stop rewriting your long article for every platform. This open source tool generates 17 platform-specific drafts — Xiaohongshu checklists, Zhihu explainers, video scripts, and more. Copyable examples in the README. Check it out: https://github.com/lhmd/dsh-promotion-toolkit",
            "instagram": "✨ Save this if multi-platform rewriting drains your time\nYou write one deep article, then have to adapt it for Xiaohongshu, Zhihu, WeChat, Douyin, Bilibili… all different formats. So much work 😩\nThis open source tool does the heavy lifting:\n✅ Extracts core points and quotable evidence\n✅ Flags risks to verify\n✅ Generates 17 platform-native drafts\n✅ Xiaohongshu gets a saveable checklist, Zhihu gets Markdown explainer\n✅ Video platforms get shots, captions, and CTA\nGet copyable results from GitHub:\n🔗 https://github.com/lhmd/dsh-promotion-toolkit\n#ContentRepurposing #OpenSource #Productivity #CreatorTools #MultiPlatform"
          },
          "hashtags": [
            "#ContentRepurposing",
            "#OpenSource",
            "#Productivity",
            "#MultiPlatform",
            "#ContentOps"
          ],
          "imagePrompt": "A split-screen illustration showing one long article on the left being processed into multiple platform-specific content cards on the right, with icons for Xiaohongshu, Zhihu, WeChat, Bilibili, Douyin, X, LinkedIn, TikTok, YouTube, Medium, Facebook, Instagram; clean flat design, soft blue and white palette, no text."
        }
      }
    }
  ]
}