Back to Details

substack-ghostwriting

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Substack Ghostwriting & Content Optimization

Substack代笔与内容优化

A skill for writing Substack content — both newsletter issues (email-first) and web posts (web-first articles/essays) — that grows subscribers and converts readers. Handles two voice modes (own voice, ghostwriting) and two format modes (newsletter issue, web post).
本技能用于撰写能增长订阅用户并转化读者的Substack内容——包括以邮件优先的新闻通讯刊期和以网页优先的文章/随笔。支持两种风格模式（自有风格、代笔）和两种格式模式（新闻通讯刊期、网页帖子）。

Core philosophy

核心理念

Substack is not a blog with an email list. It's a social-media-newsletter hybrid with an algorithm that optimizes for subscriptions, not engagement. This changes everything about how you write, format, and distribute content on the platform.
The algorithm's incentives genuinely align with quality. Substack's revenue comes from subscription cuts (not ads), so gaming engagement metrics doesn't help. What helps: writing content good enough that readers convert to paid subscribers and recommend you to others.
For ghostwriting specifically: the job is capturing someone's existing insights in their voice, not generating insights from scratch. As Nicolas Cole frames it: clients are "insights-rich and time-poor", writers are "time-rich but insights-poor." The art is extraction and voice matching.
Substack并非带邮件列表的博客，而是社交媒体与新闻通讯的混合平台，其算法以订阅量而非互动量为优化目标。这彻底改变了在该平台上撰写、排版和分发内容的方式。
该算法的激励机制真正与内容质量挂钩。Substack的收入来自订阅分成（而非广告），因此刷互动指标毫无意义。真正有效的是：撰写足够优质的内容，让读者转化为付费订阅用户并向他人推荐你。
针对代笔服务而言：工作核心是捕捉客户已有的见解并模仿其风格，而非从零生成见解。正如Nicolas Cole所言：客户“见解丰富但时间有限”，写手“时间充足但见解匮乏”。关键在于提取见解并匹配风格。

Platform formatting constraints

平台排版限制

Substack is a social-media-newsletter hybrid with an algorithm that optimizes for subscriptions, not engagement. Revenue comes from subscription cuts (not ads), so quality genuinely wins. For ghostwriting: the job is capturing someone's existing insights in their voice — clients are "insights-rich and time-poor."
Read 
references/platform-constraints.md
for post fields, Notes limits, special content blocks, and media embeds.
Substack是社交媒体与新闻通讯的混合平台，其算法以订阅量而非互动量为优化目标。收入来自订阅分成（而非广告），因此内容质量才是王道。代笔服务的核心是捕捉客户已有的见解并模仿其风格——客户“见解丰富但时间有限”。
请阅读
references/platform-constraints.md
了解帖子字段、Notes限制、特殊内容块和媒体嵌入规则。

Mode detection

模式识别

Determine two dimensions:
Voice dimension:
  • Own voice — the user writes/publishes under their own name. Go directly to the Writing Workflow.
  • Ghostwriting — writing in someone else's voice, or preparing content for a client. Complete the Ghostwriting Workflow first, then the Writing Workflow.
Format dimension:
  • Newsletter issue (email-first) — sent to subscribers' inboxes. Subject line and email formatting matter most. Read 
    references/email-formatting.md
    during Phase 3.
  • Web post (web-first) — published as a Substack article/essay, discoverable via search and Substack's feed. SEO and web formatting matter most. Read 
    references/web-post-formatting.md
    during Phase 3.
If unclear, ask the user. Default to newsletter issue when they say "newsletter" or "issue"; default to web post when they say "article", "essay", "post", or "evergreen content".
需确定两个维度：
风格维度：
  • 自有风格——用户以自己的名义撰写/发布内容。直接进入写作流程。
  • 代笔——模仿他人风格撰写内容，或为客户准备内容。先完成代笔流程，再进入写作流程。
格式维度：
  • 新闻通讯刊期（邮件优先）——发送至订阅用户的收件箱。主题行和邮件格式最为重要。在第3阶段阅读
    references/email-formatting.md
    。
  • 网页帖子（网页优先）——发布为Substack文章/随笔，可通过搜索和Substack动态发现。SEO和网页格式最为重要。在第3阶段阅读
    references/web-post-formatting.md
    。
若不确定，请询问用户。当用户提及“新闻通讯”或“刊期”时，默认选择新闻通讯刊期；当用户提及“文章”“随笔”“帖子”或“常青内容”时，默认选择网页帖子。

Ghostwriting Workflow

代笔流程

When writing for someone else, voice matching comes before content. Read 
references/voice-matching.md
for the full extraction process — it covers sample collection (transcripts > writing > media), voice marker extraction, building a voice guide (10-15 markers with examples), and iteration with the user.
Complete the voice guide and get user validation before proceeding to the Writing Workflow.
为他人撰写内容时，风格匹配优先于内容创作。请阅读
references/voice-matching.md
了解完整的风格提取流程——包括样本收集（转录稿>文字内容>媒体）、风格特征提取、构建风格指南（10-15项特征及示例）以及与用户迭代优化。
完成风格指南并获得用户确认后，再进入写作流程。

Writing Workflow

写作流程

Phase 1 is mandatory — always ask the user the intake questions and wait for answers before writing anything. If the user already provided some context, extract what you can and ask only about missing pieces.
**第1阶段为必填项——撰写任何内容前，务必先向用户询问入门问题并等待回复。**若用户已提供部分上下文，提取可用信息并仅询问缺失部分。

Phase 0: Voice calibration (own voice mode)

第0阶段：风格校准（自有风格模式）

Skip this phase if ghostwriting (the Ghostwriting Workflow handles voice separately).
Ask the user for their existing Substack URL. If they have one, recent posts are a valuable source of tone markers — formality level, sentence rhythm, humor style, paragraph length, how they open and close, recurring phrases. Summarize the voice in 5-7 bullet points and confirm with the user before writing.
If they don't have an existing Substack, ask: "How do you want to sound? Casual and conversational, professional and authoritative, or something else?" Use their answer plus any other writing samples they can share.
若为代笔模式，跳过此阶段（代笔流程已单独处理风格问题）。
询问用户的现有Substack网址。若用户已有账号，近期帖子是获取语气特征的宝贵来源——正式程度、句子节奏、幽默风格、段落长度、开头结尾方式、常用短语。用5-7个要点总结风格，并在撰写前获得用户确认。
若用户尚无Substack账号，询问：“你希望呈现何种风格？轻松口语化、专业权威，还是其他风格？”结合用户回答及他们能提供的任何其他写作样本。

Phase 1: Content planning (interview)

第1阶段：内容规划（访谈）

Stop and ask. Present the intake questions below to the user and wait for their answers. Do not skip this phase, do not infer silently, and do not start drafting until you have explicit answers or confirmation on every item.
  1. Topic: What's this about? If vague, ask what specific angle or story the reader should walk away with.
  2. Format: Newsletter issue (email-first) or web post (web-first)? See mode detection above.
  3. Audience: Who reads this? (developers, founders, marketers, general tech, niche community...) A newsletter for junior devs reads very differently than one for CTOs.
  4. Objective: What's the concrete goal?
    • Grow subscribers (free or paid)?
    • Drive signups/traffic to an external product (SaaS, course, tool)?
    • Establish authority / thought leadership?
    • Nurture existing subscribers toward a paid tier?
    • Something else? The objective shapes the CTA, the hook angle, and where depth goes vs where the paywall or link sits.
  5. Context: Part of a series? What have recent posts covered?
  6. Length: Short (500-800 words), Standard (1000-1500), Deep dive (2000+)
If critical pieces are missing (especially topic, audience, objective, or format), ask and wait — don't guess. A wrong assumption wastes an entire draft.
If the user has Notes data (which Notes got engagement), use that to validate topic selection. Notes function as a cheap testing pipeline for long-form content.
暂停并询问。向用户提出以下入门问题并等待回复。请勿跳过此阶段，请勿自行推断，在获得每个问题的明确回复或确认前，请勿开始起草内容。
  1. 主题：内容围绕什么展开？若主题模糊，询问读者应从中获得哪些具体视角或故事。
  2. 格式：新闻通讯刊期（邮件优先）还是网页帖子（网页优先）？参考上述模式识别规则。
  3. 受众：目标读者是谁？（开发者、创始人、营销人员、普通科技受众、小众社群……）面向初级开发者的新闻通讯与面向CTO的新闻通讯风格差异极大。
  4. 目标：具体目标是什么？
    • 增长订阅用户（免费或付费）？
    • 引导注册/流量至外部产品（SaaS、课程、工具）？
    • 建立权威/思想领导力？
    • 培育现有订阅用户转化为付费层级？
    • 其他目标？目标将决定CTA、钩子视角、内容深度分布以及付费墙或链接的位置。
  5. 上下文：是否为系列内容的一部分？近期帖子涵盖了哪些主题？
  6. 篇幅：短篇（500-800词）、标准篇（1000-1500词）、深度篇（2000+词）
若关键信息缺失（尤其是主题、受众、目标或格式），询问并等待——请勿猜测。错误的假设会浪费整个草稿。
若用户有Notes数据（哪些Notes获得了互动），可用于验证主题选择。Notes可作为长内容的低成本测试渠道。

Phase 2: Title and hook selection

第2阶段：标题与钩子选择

Generate 5 title/subject line variants and 3 hook options (opening 2-3 sentences each). Present them together and ask the user to pick or remix before proceeding. Do not write the body until the user has validated a title and hook direction.
Title principles:
  • Specificity beats vagueness
  • Promise a clear benefit or reveal
  • 6-10 words (readable on mobile and in search results)
  • For dev audiences: technical keywords filter for the right audience; "How to" and numbers perform well; avoid urgency/scarcity tactics
Hook types — write 3 distinct hooks using different strategies (e.g. credibility, counter-narrative, curiosity, surprise, data). Each hook should be 2-3 sentences that could open the piece. Present them labeled (Hook A, Hook B, Hook C) with a brief note on the strategy used.
Newsletter issue — subject line + preview text:
  • The subject line is the headline. The preview text (first ~90 chars of the email) is the subhead. Together they determine open rate.
  • Preview text should complement, not repeat, the subject line.
Web post — SEO + discoverability:
  • Keep the main title punchy for the feed. Use the separate SEO title field for a keyword-rich version (under 60 chars).
  • Write a dedicated SEO description (150-160 chars) — don't rely on the subtitle fallback, it's usually too short.
  • Suggest a URL slug: short (3-6 words), keyword-rich, no dates.
  • Assign to a publication section if applicable.
  • Read 
    references/web-post-formatting.md
    for detailed SEO guidance.
Wait for the user to choose a title and hook before moving to Phase 3.
生成5个标题/主题行变体和3个钩子选项（每个钩子为开头2-3句话）。将它们一起呈现，并请用户选择或混搭后再继续。在用户确认标题和钩子方向前，请勿撰写正文。
标题原则：
  • 具体性优于模糊性
  • 承诺明确的收益或亮点
  • 6-10词（在移动端和搜索结果中易读）
  • 面向开发者受众：技术关键词可筛选精准受众；“如何”和数字表现良好；避免紧迫感/稀缺性策略
钩子类型——采用不同策略撰写3个不同的钩子（如可信度、反叙事、好奇心、惊喜、数据）。每个钩子为2-3句话，可作为文章开头。标注钩子类型（钩子A、钩子B、钩子C）并简要说明所用策略。
新闻通讯刊期——主题行+预览文本：
  • 主题行即标题。预览文本（邮件前约90个字符）即副标题。两者共同决定打开率。
  • 预览文本应补充而非重复主题行。
网页帖子——SEO+可发现性：
  • 主标题要醒目以适配动态流。使用单独的SEO标题字段填写含关键词的版本（不超过60字符）。
  • 撰写专门的SEO描述（150-160字符）——不要依赖副标题 fallback，通常副标题太短。
  • 建议URL slug：简短（3-6词）、含关键词、无日期。
  • 若适用，分配至出版物栏目。
  • 阅读
    references/web-post-formatting.md
    获取详细SEO指南。
等待用户选择标题和钩子后，再进入第3阶段。

Phase 3: Write the content

第3阶段：撰写内容

Using the chosen title and hook, write the full piece. The hook opens the article, then continue with:
  1. Hook (chosen from Phase 2)
  2. Context (1-2 paragraphs): Why this matters now. What prompted this.
  3. Body (bulk): The actual content. Structure depends on content type.
  4. Takeaway (1-2 sentences): The one thing the reader should remember.
  5. CTA (1-2 sentences): Ask for a specific action. Questions that invite replies are strongest (replies are an algorithm signal).
Newsletter issue formatting — read 
references/email-formatting.md
for full rules:
  • Paragraphs: 2-3 sentences max (email clients make long paragraphs feel like walls)
  • Code blocks: < 10 lines (link to Gist for longer code)
  • Images: sparingly (many email clients block them by default)
  • TL;DR at top for issues > 1500 words
Web post formatting — read 
references/web-post-formatting.md
for full rules:
  • Paragraphs: 3-4 sentences acceptable (full-width web rendering is more forgiving)
  • Longer code blocks OK (up to 30-40 lines with full syntax highlighting)
  • Images and embeds render reliably — use more liberally
  • Table of contents for posts > 2000 words
Shared formatting rules:
  • Subheadings every 200-400 words. Bold key phrases so skimmers catch the argument.
  • Descriptive anchor text on links, not "click here."
使用选定的标题和钩子，撰写完整内容。钩子作为文章开头，后续结构如下：
  1. 钩子（选自第2阶段）
  2. 上下文（1-2段）：为何现在这个主题很重要，是什么促成了这篇内容。
  3. 正文（主体）：核心内容。结构取决于内容类型。
  4. 要点总结（1-2句话）：读者应记住的核心信息。
  5. CTA（1-2句话）：请求读者采取特定行动。邀请回复的问题效果最佳（回复是算法的互动信号）。
新闻通讯刊期排版——阅读
references/email-formatting.md
获取完整规则：
  • 段落：最多2-3句话（邮件客户端中长段落会显得像文字墙）
  • 代码块：<10行（更长代码请链接至Gist）
  • 图片：谨慎使用（许多邮件客户端默认屏蔽图片）
  • 篇幅>1500词的刊期，在顶部添加TL;DR（摘要）
网页帖子排版——阅读
references/web-post-formatting.md
获取完整规则：
  • 段落：可接受3-4句话（全宽网页渲染更宽松）
  • 可使用更长代码块（最多30-40行，带完整语法高亮）
  • 图片和嵌入内容渲染可靠——可更自由地使用
  • 篇幅>2000词的帖子，添加目录
通用排版规则：
  • 每200-400词添加小标题。加粗关键短语，方便快速浏览的读者抓住核心论点。
  • 链接使用描述性锚文本，而非“点击这里”。

Phase 4: Growth-optimized elements

第4阶段：增长优化元素

Add elements that leverage the Substack algorithm. Read 
references/substack-algorithm.md
for the full mechanics.
  1. Reply prompt: End with a genuine question. Replies signal engagement to the algorithm.
  2. Share prompt: "If you found this useful, forward it to a colleague who [specific situation]." Specificity increases share rate.
  3. Recommendation hook: If the user has recommendation partnerships, weave in natural cross-references.
  4. Notes teaser: Write a 2-3 sentence version for Substack Notes. Notes should stand alone as valuable, not just be a link to the issue.
添加利用Substack算法的元素。阅读
references/substack-algorithm.md
了解完整机制。
  1. 回复提示：以真实问题结尾。回复向算法传递互动信号。
  2. 分享提示：“如果你觉得本文有用，请转发给有[特定需求]的同事。”具体性可提高分享率。
  3. 推荐钩子：若用户有推荐合作关系，自然融入交叉引用。
  4. Notes预告：撰写2-3句话的Substack Notes版本。Notes应具备独立价值，而非仅作为刊期的链接。

Phase 5: Paid vs. free strategy

第5阶段：免费vs付费策略

If the user has a paid tier, advise on the free/paid split:
  • Free issues should be your best work (they drive growth and recommendations)
  • Paid issues should offer depth, exclusivity, or access (not just a paywall on normal content)
  • The most effective model: free issues that demonstrate value so clearly that readers want more
Common mistake: paywalling too early. At < 1000 subscribers, everything should be free. Growth compounds faster than paid conversion at small scale.
若用户设有付费层级，提供免费/付费内容划分建议：
  • 免费刊期应是你的最佳作品（推动增长和推荐）
  • 付费刊期应提供深度内容、独家内容或专属权限（而非仅对普通内容设置付费墙）
  • 最有效的模式：免费刊期清晰展示价值，让读者想要更多内容
常见错误：过早设置付费墙。订阅用户<1000时，所有内容应免费。小规模阶段，增长的复利效应比付费转化率更重要。

Phase 5b: Humanize

第5b阶段：人性化处理

Invoke a humanizer skill (e.g. "humanize", "humanizer", "de-slop", "natural writing check", "AI detection cleanup", "rewrite like a human") to strip AI-generated patterns — filler words, predictable cadence, over-hedging, hollow transitions, inflated language. Substack readers pay for authentic voice; AI-sounding prose kills trust and cancels subscriptions.
Preserve hooks and subject lines. The hook and title/subject line (Phase 2) were deliberately engineered for open rate and curiosity. Instruct the humanizer to leave them intact — rewriting them for "naturalness" destroys the copywriting structure that drives opens and first-scroll retention.
调用人性化技能（如"humanize"、"humanizer"、"de-slop"、"natural writing check"、"AI detection cleanup"、"rewrite like a human"）去除AI生成的模式——填充词、可预测的节奏、过度模糊的表述、空洞的过渡、浮夸的语言。Substack读者为真实风格付费；AI感的文字会破坏信任并导致订阅取消。
保留钩子和主题行。第2阶段的钩子和标题/主题行是专门为提高打开率和好奇心设计的。指示人性化工具保留这些内容——为了“自然性”改写它们会破坏驱动打开率和首次滚动留存的文案结构。

Phase 6: Image suggestions

第6阶段：图片建议

After the content is drafted, suggest 1-3 images with specific placement. For each image, provide:
  • Placement: Where in the issue (e.g. "as the cover image", "after the hook", "between section X and Y")
  • Purpose: What the image adds (set the tone, break up a long section, illustrate a concept, reinforce the emotional beat)
  • Description: What the image should depict
For newsletter issues: use images sparingly — many email clients block them by default. Prioritize a strong cover image and at most 1-2 inline images. For web posts: images render reliably — use more freely (diagrams, charts, screenshots).
Offer to generate a Midjourney prompt for each suggested image. If the user accepts, use the latest Midjourney model conventions to write the prompt. Use 
--ar 16:9
or 
--ar 3:1
for cover images and wide illustrations (optimal for Substack headers and social sharing), 
--ar 3:2
for smaller inline images. Refer to up-to-date Midjourney documentation for current prompt syntax and parameters.
内容起草完成后，建议1-3张图片并指定具体位置。每张图片需提供：
  • 位置：在刊期/帖子中的位置（如“作为封面图”“钩子之后”“X部分与Y部分之间”）
  • 目的：图片的作用（设定基调、分隔长段落、阐释概念、强化情感节奏）
  • 描述：图片应呈现的内容
对于新闻通讯刊期：谨慎使用图片——许多邮件客户端默认屏蔽图片。优先选择优质封面图，最多添加1-2张内联图片。对于网页帖子：图片渲染可靠——可更自由地使用（图表、示意图、截图）。
主动提出为每个建议图片生成Midjourney提示词。若用户同意，使用最新Midjourney模型规范撰写提示词。封面图和宽幅插图使用
--ar 16:9
或
--ar 3:1
（适配Substack页眉和社交分享），小型内联图片使用
--ar 3:2
。参考最新Midjourney文档获取当前提示词语法和参数。

Phase 7: Social distribution posts (optional — offer, don't auto-generate)

第7阶段：社交分发帖子（可选——主动提供，勿自动生成）

After the content is written, ask the user if they want social distribution posts. Do not generate them automatically. If accepted, write a LinkedIn post and/or a Twitter/X post to promote it. These are not summaries — they are standalone pieces of content that create enough curiosity or value to drive clicks.
Read 
references/social-distribution.md
for LinkedIn and Twitter/X post templates.
内容撰写完成后，询问用户是否需要社交分发帖子。请勿自动生成。若用户同意，撰写LinkedIn帖子和/或Twitter/X帖子用于推广。这些不是摘要——而是独立的内容，需足够吸引人或有价值以引导点击。
阅读
references/social-distribution.md
获取LinkedIn和Twitter/X帖子模板。

Output format

输出格式

Newsletter issue:
  • Subject line (chosen) + 2 alternatives
  • Preview text
  • Full issue in markdown, formatted for email readability
  • Image suggestions with placement notes (and Midjourney prompts if accepted)
  • A Notes teaser (2-3 sentences)
  • LinkedIn + Twitter/X distribution posts (only if the user accepted)
  • If ghostwriting: the voice guide used
Web post:
  • Title (chosen) + 2 alternatives
  • Subtitle / meta description
  • Suggested URL slug
  • Full post in markdown, formatted for web readability
  • Image suggestions with placement notes (and Midjourney prompts if accepted)
  • A Notes teaser (2-3 sentences)
  • LinkedIn + Twitter/X distribution posts (only if the user accepted)
  • If ghostwriting: the voice guide used
新闻通讯刊期：
  • 选定的主题行+2个备选
  • 预览文本
  • 符合邮件可读性的完整刊期markdown格式
  • 带位置说明的图片建议（若用户同意则包含Midjourney提示词）
  • Notes预告（2-3句话）
  • LinkedIn + Twitter/X分发帖子（仅当用户同意时）
  • 若为代笔：使用的风格指南
网页帖子：
  • 选定的标题+2个备选
  • 副标题/元描述
  • 建议的URL slug
  • 符合网页可读性的完整帖子markdown格式
  • 带位置说明的图片建议（若用户同意则包含Midjourney提示词）
  • Notes预告（2-3句话）
  • LinkedIn + Twitter/X分发帖子（仅当用户同意时）
  • 若为代笔：使用的风格指南

Adapting existing content

改编现有内容

When the user wants to convert a blog post, talk, or thread into Substack content:
  1. Choose the right format. Evergreen source material (reference, tutorial, deep dive) → web post. Timely source (commentary, announcement, reaction) → newsletter issue.
  2. Don't just copy-paste. Substack readers expect a different voice and format than blog readers.
  3. Add the personal layer. Substack is more personal than a blog. Add context: why you're sharing this, what prompted it, your take.
  4. Front-load the value. Blog posts can have a slow build. Substack content must hook in the first 2 sentences (the email preview or search snippet).
  5. Shorten for newsletters. Cut 30-50% of blog post length for newsletter issues — email tolerance for length is lower. Web posts can preserve more depth.
  6. Add the CTA. Blog posts can end quietly. Substack content should ask for something.
当用户希望将博客文章、演讲或推文串转换为Substack内容时：
  1. 选择合适的格式。常青素材（参考资料、教程、深度解析）→网页帖子。时效性素材（评论、公告、回应）→新闻通讯刊期。
  2. 不要直接复制粘贴。Substack读者期待的风格和格式与博客读者不同。
  3. 添加个人视角。Substack比博客更具个人化。添加上下文：为何分享此内容、是什么促成了分享、你的观点。
  4. 前置核心价值。博客文章可以慢慢铺垫。Substack内容必须在前2句话抓住读者（邮件预览或搜索片段）。
  5. 为新闻通讯缩短篇幅。将博客文章的篇幅削减30-50%用于新闻通讯刊期——邮件对篇幅的容忍度更低。网页帖子可保留更多深度内容。
  6. 添加CTA。博客文章可以平淡收尾。Substack内容应明确请求读者采取行动。

Reference files

参考文件

Read these for deeper platform knowledge:
  • references/voice-matching.md
    -- Detailed ghostwriting voice extraction process, interview techniques, voice guide templates, and iteration workflow. Read when ghostwriting.
  • references/email-formatting.md
    -- Email client rendering constraints, formatting rules, mobile optimization, and code block handling. Read during Phase 3 for newsletter issues.
  • references/web-post-formatting.md
    -- SEO optimization, web-first formatting rules, evergreen vs timely content strategy, sections/categories, and rich media usage. Read during Phase 3 for web posts.
  • references/substack-algorithm.md
    -- How the algorithm works (from Substack's ML lead), Notes ranking signals, Recommendations system, growth levers ranked by impact, and monetization math. Read during Phase 4 or for strategic planning.
阅读以下文件获取更深入的平台知识：
  • references/voice-matching.md
    -- 详细的代笔风格提取流程、访谈技巧、风格指南模板和迭代流程。代笔时阅读。
  • references/email-formatting.md
    -- 邮件客户端渲染限制、排版规则、移动端优化和代码块处理。撰写新闻通讯刊期的第3阶段阅读。
  • references/web-post-formatting.md
    -- SEO优化、网页优先排版规则、常青内容vs时效性内容策略、栏目分类和富媒体使用。撰写网页帖子的第3阶段阅读。
  • references/substack-algorithm.md
    -- 算法工作原理（来自Substack的机器学习负责人）、Notes排名信号、推荐系统、按影响力排序的增长杠杆以及变现计算。第4阶段或战略规划时阅读。