newsletter-creator

Newsletter Creator

用于创建引人入胜的内部和外部通讯的结构化框架，确保质量稳定、内容策划有效，并采用适合受众的语气。

通讯结构

标准通讯版块

NEWSLETTER LAYOUT:

1. HEADER
   - Newsletter name / brand
   - Edition number and date
   - Tagline or theme for this edition

2. TL;DR / HIGHLIGHTS (above the fold)
   - 3-5 bullet summary of key items
   - Designed for scanners who won't read the full email
   - Each bullet links to the corresponding section

3. FEATURED STORY (1 item)
   - Primary content piece
   - 150-250 words with a clear takeaway
   - Supporting image or graphic
   - CTA: read more, watch, try

4. NEWS & UPDATES (3-5 items)
   - Brief summaries (50-100 words each)
   - Consistent format: headline, summary, link
   - Categorized if applicable

5. CURATED CONTENT (3-5 items)
   - Third-party articles, tools, or resources
   - Brief annotation explaining relevance
   - Source attribution

6. SPOTLIGHT SECTION (1 item, rotating)
   - Team member spotlight, customer story, tool tip
   - Rotates theme each edition
   - Personal and engaging

7. UPCOMING EVENTS / DATES
   - Relevant events, webinars, deadlines
   - Calendar format or simple list

8. FOOTER
   - Unsubscribe / manage preferences
   - Social media links
   - Feedback prompt ("Reply with your thoughts")
   - Archives link

内部与外部通讯的区别

要素	内部通讯	外部通讯
语气	轻松、透明、面向团队	专业、注重价值
内容	公司动态、成果、文化	行业洞察、产品动态
频率	每周或每两周	每周、每两周或每月
长度	500-800 字	300-600 字
CTA	参与、表彰、反馈	了解更多、试用功能、注册
指标	打开率、问卷反馈	打开率、点击率、转化率
个性化	按团队或部门	按细分群体或兴趣

内容策划方法

策划工作流

WEEKLY CURATION PROCESS:

COLLECT (ongoing throughout week):
- Save articles to curation tool (Pocket, Raindrop, Notion)
- Tag with categories and relevance score
- Note key quotes or takeaways
- Track sources for diversity

EVALUATE (1 day before send):
- Review all saved items
- Score each on: relevance, timeliness, quality, uniqueness
- Select top items per section
- Verify links still work
- Check for duplicates from prior editions

CURATE (writing day):
- Write brief annotations for each item (why it matters)
- Arrange in priority order
- Write featured story and transitions
- Add editorial perspective where appropriate

REVIEW (before send):
- Proofread all copy
- Test all links
- Preview in email client (desktop + mobile)
- Check accessibility (alt text, contrast)
- Send test to 2-3 reviewers

内容评分矩阵

标准	权重	5（纳入）	3（可考虑）	1（跳过）
相关性	30%	直接适用	间接相关	偏离主题
时效性	25%	本周 / 突发新闻	本月	过时消息
质量	20%	专家来源、有数据支撑	不错但较笼统	清单类文章 / 内容空泛
独特性	15%	读者不太可能看过	传播范围一般	爆红 / 随处可见
可操作性	10%	有明确要点或行动	提供信息	抽象 / 理论性

THRESHOLD:
  3.5+: Definite include
  2.5-3.4: Include if space permits
  < 2.5: Skip unless slow news week

语气和风格指南

按受众划分的风格框架

INTERNAL NEWSLETTER VOICE:

Personality: Friendly colleague who's well-informed
Tone: Warm, transparent, sometimes playful
Language: First-person plural ("we"), casual contractions
Avoid: Corporate jargon, overly formal language, spin

EXAMPLE:
"Big week for the product team — they shipped the new
dashboard that's been in the works since Q3. If you haven't
tried it yet, you're missing out. Here's a quick walkthrough."

──────────────────────────────────────────────────────

EXTERNAL NEWSLETTER VOICE:

Personality: Trusted industry insider
Tone: Authoritative but approachable, value-focused
Language: Second-person ("you"), professional but not stiff
Avoid: Self-promotion overload, clickbait, assumptions

EXAMPLE:
"This week, three major shifts in the data infrastructure
space caught our attention. Here's what they mean for your
stack — and what to do about it."

注释风格指南

CONTENT ANNOTATION FORMULA:

[HEADLINE] (linked)
[1-2 sentence summary of what it covers]
[1 sentence on why it matters to your audience]

EXAMPLE:
"The State of Developer Experience 2025" (link)
GitHub's annual report surveying 12,000 developers on tooling,
AI adoption, and workflow satisfaction. Worth reading for the
data on how teams are actually using AI coding assistants —
the gap between hype and reality is illuminating.

BAD ANNOTATION:
"The State of Developer Experience 2025" (link)
Check out this report from GitHub.

(No context, no why-it-matters, no reason to click)

布局和格式最佳实践

电子邮件设计原则

FORMATTING RULES:

WIDTH:
- Max content width: 600px
- Single column preferred (reliable rendering)
- 2-column only for desktop-specific sections

TYPOGRAPHY:
- Body: 16px minimum (mobile readability)
- Headlines: 20-24px
- Line height: 1.5-1.6
- Font: System fonts or web-safe (Arial, Georgia, Helvetica)

IMAGES:
- Width: 100% of container (responsive)
- Alt text on every image
- File size: < 200KB per image
- Use sparingly — many clients block images by default

SPACING:
- Section dividers between major sections
- Generous padding (20px+) between items
- White space > cramped content

MOBILE:
- Test on iOS Mail, Gmail app, Outlook app
- Buttons: minimum 44x44px touch target
- Text should be readable without zooming
- Stack columns vertically on mobile

模板结构（HTML）

EMAIL TEMPLATE SKELETON:




[HEADER: Logo + Edition Info]

[TL;DR BOX: 3-5 bullet highlights]

[DIVIDER]

[FEATURED STORY: Image + Text + CTA Button]

[DIVIDER]

[NEWS SECTION: 3-5 items, consistent format]

[DIVIDER]

[CURATED LINKS: 3-5 external items with annotations]

[DIVIDER]

[SPOTLIGHT: Rotating section]

[DIVIDER]

[EVENTS: Simple list or calendar]

[FOOTER: Unsubscribe, social, feedback]

优化主题行

主题行公式

PROVEN FORMATS:

CURIOSITY: "The one metric most teams get wrong"
NUMBER:    "5 things we learned shipping v3.0"
QUESTION:  "Is your CI pipeline costing you hours?"
NEWS:      "Big changes coming to [product] this quarter"
PERSONAL:  "[Name], your weekly engineering digest"
EMOJI:     "This week in product" (use sparingly, max 1)

CHARACTER LIMITS:
- Ideal: 30-50 characters
- Max: 60 characters (mobile truncation)
- Preheader: extend subject with 40-90 chars of context

A/B TEST PAIRS:
- Short vs. long
- Question vs. statement
- With emoji vs. without
- Specific vs. vague
- Personalized vs. generic

主题行反模式

AVOID:
- ALL CAPS (looks like spam)
- Excessive punctuation (!!!)
- Misleading or clickbait subjects
- "Newsletter #47" (boring, no reason to open)
- Repeating the same format every week
- Overly long subjects that get truncated

指标与效果追踪

关键指标

指标	良好	一般	需要改进	行动
打开率	> 40%	25-40%	< 25%	改进主题行、发送时间
点击率	> 5%	2-5%	< 2%	优化 CTA，提供更相关的内容
点击打开率	> 15%	8-15%	< 8%	改进内容质量、布局
退订率	< 0.1%	0.1-0.3%	> 0.3%	检查发送频率和相关性
回复率	> 1%	0.5-1%	< 0.5%	添加回复提示和问题

效果评估模板

MONTHLY NEWSLETTER REVIEW:

Edition Stats:
| Edition | Date | Open % | Click % | Unsub % | Top Link |
|---------|------|--------|---------|---------|----------|
| #47     |      |        |         |         |          |
| #48     |      |        |         |         |          |
| #49     |      |        |         |         |          |
| #50     |      |        |         |         |          |

Trends:
- Open rate trend: [up/down/flat]
- Best-performing content type: [___]
- Worst-performing content type: [___]
- Optimal send time (from data): [___]

Actions for Next Month:
- [ ] [specific improvement based on data]
- [ ] [content type to add or remove]
- [ ] [send time or frequency adjustment]

整合内容日历

编辑日历模板

MONTHLY CONTENT CALENDAR:

Week 1: [Theme / Focus]
- Featured: [topic]
- Curated: [2-3 planned sources]
- Spotlight: [team member / customer / tool]

Week 2: [Theme / Focus]
- Featured: [topic]
- Curated: [2-3 planned sources]
- Spotlight: [rotating section type]

Week 3: [Theme / Focus]
- Featured: [topic]
- Curated: [2-3 planned sources]
- Spotlight: [rotating section type]

Week 4: [Theme / Focus]
- Featured: [topic]
- Curated: [2-3 planned sources]
- Spotlight: [rotating section type]

RECURRING SECTIONS:
- Monthly: Industry roundup, metrics review
- Quarterly: Retrospective, reader survey
- Annual: Year in review, predictions

频率和发送时间建议

受众	建议频率	最佳发送日期	最佳发送时间
内部（全公司）	每周	周一或周五	当地时间上午 9-10 点
内部（团队）	每周	周一	当地时间上午 9 点
外部（B2B）	每周或每两周	周二至周四	美国东部时间上午 10 点
外部（B2C）	每周	周二或周六	上午 10 点或晚上 8 点
高管摘要	每月	第一个周一	当地时间上午 8 点

通讯质量检查清单

检查项	状态
主题行引人注目且少于 60 个字符	[ ]
预标题文本补充了背景信息（而非重复主题行）	[ ]
TL;DR 版块概括了重点内容	[ ]
所有链接均已测试且有效	[ ]
图片均有替代文本	[ ]
已测试移动端显示效果	[ ]
语气符合目标受众	[ ]
内容经过策划（而非单纯汇总）	[ ]
每项内容都清楚说明了“为何重要”	[ ]
退订链接存在且有效	[ ]
发送时间针对受众进行了优化	[ ]
至少由另一人校对	[ ]

另请参阅

• 营销
• anthropic-skills:docx（Anthropic 文档技能）
• 电子邮件系统
• 产品管理