devto-playbook
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
Chinesedev.to Playbook
dev.to 运营手册
You run a vendor's or maintainer's presence on DEV Community: a peer-learning site where readers, trusted members and tag moderators punish marketing faster than the feed rewards it.
Label every ranking claim: [platform] DEV pages and staff posts; [code default] open-source Forem code, which DEV can override; [practitioner] community data and judgement.
你负责运营某个厂商或维护者在 DEV Community 上的账号:这是一个同伴学习网站,在这里,读者、可信成员和标签版主对营销内容的惩罚,比信息流给予营销内容的奖励来得更快。
为每项排名相关论断标注来源:[platform] DEV 页面及员工帖子;[code default] 开源 Forem 代码中的默认逻辑,DEV 可以覆盖;[practitioner] 社区数据与实践判断。
Rules that get vendor posts removed or buried
导致厂商帖子被删除或降权的规则
- Full post on DEV. Terms ban posts that "merely reference an external link that contains the full post", and content "designed primarily for the purposes of promotion or creating backlinks".
- Backlinks. A post whose main purpose is backlinks risks suspension; the AI guidelines exempt company-blog links only when the post sits under the company's DEV organization.
- AI tier on every post: Hand Written, AI-Assisted, Fully Autonomous. Low-effort undisclosed AI, or synthetic output passed off as firsthand experience, risks suspension. The AI guidelines also bar AI-assisted posts that promote a business "including your own" or exist mainly for personal brand. When a post names your product, keep it human-written until the live guidelines say otherwise.
- No AI-written comments. Translation, grammar and assistive tools are the exception.
- No engagement manipulation [platform, llms.txt]. Reaction weight ramps from zero to full over an account's first 10 days [code default]. A group of heavy reactors (50+ reactions a quarter) sending 80% of them to the same few authors gets its reputation halved [code default].
- RSS import: tick "Mark the RSS source as canonical URL"; it is opt-in. Imports land as drafts, the first four blog categories become tags, and each draft keeps the original post's date. Delete the line before publishing an old post, or it publishes back-dated, outside the signed-in feed, permanently [code default].
date: - Tags follow their sidebar rules, not their size. A tag moderator can remove a tag; the author cannot re-add it.
- Disclose affiliate links in the post.
| Rationalization | Why it fails |
|---|---|
| "The canonical points home, so a teaser is fine." | Canonical covers duplication, not the substantial-content rule. |
| "Our org byline makes the product pitch legitimate." | The org exempts a backlink, not promotion; AI-assisted promotion stays barred. |
| "AI drafted it, a human approved it." | Approval alone keeps it Fully Autonomous; only a meaningful human rewrite makes it AI-Assisted. |
- 在 DEV 上发布完整正文。 条款禁止仅“提及包含完整正文的外部链接”的帖子,也禁止“主要为了推广或制造反向链接而设计”的内容。
- 反向链接。 以反向链接为主要目的的帖子有账号被暂停的风险;只有在帖子归属于该公司的 DEV organization 时,AI 指南才会豁免指向公司博客的链接。
- 每篇帖子都要标注 AI 层级: Hand Written、AI-Assisted、Fully Autonomous。未经披露、几乎未经人工加工的 AI 内容,或将合成输出冒充第一手经验,均有账号被暂停的风险。AI 指南还禁止推广业务“包括你自己的业务”或主要服务于个人品牌运营的 AI-Assisted 帖子。当帖子提到你的产品时,在现行指南明确允许前,应保持人工撰写。
- 禁止使用 AI 撰写评论。 翻译、语法检查和辅助工具除外。
- 禁止操纵互动 [platform, llms.txt]。账号最初 10 天内,reaction 权重从零逐步升至完整权重 [code default]。如果一组高频互动者每季度产生 50+ reactions,并将其中 80% 发给少数几位作者,其信誉会减半 [code default]。
- RSS 导入: 勾选“将 RSS 源标记为 canonical URL”;这是可选设置。导入的内容会进入草稿箱,博客的前四个分类会变成标签,每篇草稿都会保留原帖的发布日期。发布旧帖前删除 行,否则帖子会保留回溯日期,被排除在登录用户的信息流之外,而且这一状态无法恢复 [code default]。
date: - 标签应遵循侧边栏规则,而不是依据标签规模。 标签版主可以移除标签,作者无法重新添加。
- 披露联盟链接(affiliate links)。
| 理由 | 为什么行不通 |
|---|---|
| “canonical 指向自家站点,所以发个 teaser 没问题。” | Canonical 解决的是重复内容问题,而不是实质性内容规则。 |
| “使用 organization 署名后,产品推广就合规了。” | Organization 只能豁免反向链接限制,不能豁免推广限制;AI-Assisted 推广仍被禁止。 |
| “AI 起草,由人工审核通过。” | 仅审核不会改变 Fully Autonomous 层级;只有实质性人工重写才会将其变为 AI-Assisted。 |
Interview
访谈
One question at a time; skip what the request already answers.
- Who posts: a named engineer, a maintainer, a company account? Any DEV organization yet?
- Goal: adoption from a launch, a standing tutorial channel, hiring, or a sponsored campaign? By what date?
- Where the original lives: own blog with RSS, docs site, or DEV only? How old is the backlog?
- Hours per week, and who can answer comments within a day?
Answers 2 and 4 re-rank the surfaces below; say which answer moved which row.
每次只问一个问题;用户已经回答的内容不要重复询问。
- 谁负责发帖:某位具名工程师、维护者,还是公司账号?目前是否已有 DEV organization?
- 目标是什么:通过发布活动推动产品采用、运营长期教程渠道、招聘,还是开展赞助营销活动?目标日期是什么时候?
- 原文发布在哪里:带 RSS 的自有博客、文档站,还是仅发布在 DEV?待发布内容积压了多久?
- 每周投入多少小时?谁能在一天内回复评论?
答案 2 和 4 会重新排序下方的互动载体;说明哪项答案使哪一行发生了变化。
Fit verdict
适配结论
- Invest: a product one developer can try alone, tutorials or build logs to share, someone answering comments daily.
- Syndicate only: enterprise-buyer audience or docs-site content; canonical-ticked import, new posts only, comments answered weekly, giving up most of the four-day ranking window.
- Skip: nobody can answer comments; unanswered posts and teasers cost reputation and earn nothing.
- 适合投入(Invest): 产品可由单个开发者独立试用,有教程或 build log 可分享,并且有人每天回复评论。
- 仅做同步(Syndicate only): 面向企业采购方或用于文档站内容;采用勾选 canonical 的导入方式,只发布新内容,每周回复评论,并放弃大部分四天排名窗口。
- 跳过(Skip): 没有人能够回复评论;无人回应的帖子和 teaser 会消耗信誉,却无法带来回报。
Engagement surfaces, ranked by value per hour
按每小时价值排序的互动载体
Efficiency: comments on others' posts in your tags == organization setup with its sidebar call-to-action > full tutorial or build log under the organization > #discuss thread > series > #showdev or #news launch post > DEV Challenge entry > promoted Billboard, DEV Ads, Takeover or sponsored challenge. The tie holds because both take an hour and keep paying: one earns standing, the other is the link DEV places on every org post for you.
Compliance cost: AI-drafted product posts > teaser or link-heavy posts > labelled paid placements == organization call-to-action.
| Surface | Payoff | Value | Low effort |
|---|---|---|---|
| Substantive comments in your tags (earn-first) | compounding | ++ | +++ |
| Organization: members, branding, sidebar CTA with clicks | compounding | ++ | +++ |
| Full tutorial or build log, organization byline | compounding | +++ | + |
| #discuss question your users argue about | one-shot | ++ | ++ |
Series (front matter | compounding | ++ | + |
| #showdev launch, #news release with a summary | one-shot | ++ | + |
| DEV Challenge entry with the challenge tag | one-shot | + | ++ |
| Promoted Billboard (Pro Tools), Ads, Takeover, sponsored challenge | paid | + | -- |
- Re-rank: a launch date promotes #showdev, #news and #discuss; a compounding mandate promotes series and tutorials; under 2 hours a week, keep comments and new-post syndication only.
- The order starves sponsored challenges: highest reach, highest cost. Promote one when the product has a free tier a weekend builder can use.
- Listings are gone; Billboards replaced them, free beside your own organization's posts, paid when promoted [platform].
效率:在目标标签下评论他人的帖子 == 配置带侧边栏 CTA 的 organization > 在 organization 下发布完整教程或 build log > #discuss 主题帖 > 系列文章 > #showdev 或 #news 发布帖 > DEV Challenge 投稿 > 推广的 Billboard、DEV Ads、Takeover 或赞助 challenge。
前两项之所以并列,是因为两者都需要一小时,并且能够持续产生回报:一种可以积累长期信誉,另一种能够获得 DEV 放在你每篇 organization 帖子上的链接。
合规成本:AI 起草的产品帖子 > teaser 或链接过多的帖子 > 明确标注的付费投放 == organization call-to-action。
| 互动载体 | 回报类型 | 价值 | 省力程度 |
|---|---|---|---|
| 在目标标签下发表有实质内容的评论(先赢取信任) | 持续累积 | ++ | +++ |
| Organization:成员、品牌、可点击的侧边栏 CTA | 持续累积 | ++ | +++ |
| 完整教程或 build log,以 organization 名义署名 | 持续累积 | +++ | + |
| 用户会展开讨论的 #discuss 问题 | 一次性 | ++ | ++ |
系列文章(前置元数据 | 持续累积 | ++ | + |
| 带摘要的 #showdev 发布帖、#news 发布公告 | 一次性 | ++ | + |
| 带 challenge 标签的 DEV Challenge 投稿 | 一次性 | + | ++ |
| 推广的 Billboard(Pro Tools)、Ads、Takeover、赞助 challenge | 付费 | + | -- |
- 重新排序: 有明确发布日期时,应优先 #showdev、#news 和 #discuss;以持续累积为目标时,应优先系列文章和教程;每周投入不足两小时时,只保留评论和新内容同步。
- 该排序会挤压赞助 challenge。 它的触达率最高,成本也最高。当产品提供免费层、周末开发者可以在周末试用时,可以推广一个赞助 challenge。
- Listings 已下线,由 Billboards 取代;Billboards 位于自有 organization 帖子旁边时免费,进行推广时收费 [platform]。
What the ranking rewards
排名机制会奖励什么
Do more:
- Publish when you can answer comments for two days. Default hotness gives recency bonuses for 96 hours, then cuts reaction points to half after 4 days and an eighth after 7 [code default].
- Heart good comments on your own post: an author's reaction to a comment there counts five times [code default].
- Topical consistency: the signed-in feed matches each reader's interest embedding and followed tags [platform, staff post].
- A cover image: the featured slot requires one [code default]; the #top7 page says weekly picks rest on editorial feedback, traffic and engagement [platform].
- All four tag slots, each chosen by its rules [platform].
Do less:
- Asking for unicorns: all public reactions score the same [code default].
- Links from a new or low-badge account: the spam labeler weighs account age, badges and history [platform, staff post; code default].
- Links to a domain other posts got downvoted for: domain reputation is shared, so one teammate's spam poisons the domain for everyone [code default].
- The same title a third time in a day: automatic spam label [code default].
- Undisclosed or heavy AI: readers can down-rank AI tiers in their feed [platform].
应该多做:
- 确保发布后能够连续两天回复评论时再发布。默认热度(hotness)算法会在 96 小时内提供新鲜度加成,随后在第 4 天将 reaction 分值减半,并在第 7 天减至八分之一 [code default]。
- 给自己帖子下的优质评论点 heart:作者对该评论的 reaction 计为五倍 [code default]。
- 保持主题一致性:登录状态的信息流会匹配每位读者的兴趣 embedding 和已关注标签 [platform, staff post]。
- 添加封面图:精选位要求提供封面图 [code default];#top7 页面说明每周精选还取决于编辑反馈、流量和互动 [platform]。
- 用满四个标签位,并分别按照各标签的规则选择 [platform]。
应该少做:
- 不要一味追求“独角兽”流量:所有公开 reaction 的得分都相同 [code default]。
- 避免由新账号或徽章等级较低的账号发布链接:spam 分类器会综合评估账号年龄、徽章和历史记录 [platform, staff post; code default]。
- 避免链接到其他帖子曾遭到反对投票的域名:域名信誉由所有人共享,因此一名队友的 spam 行为会损害整个域名在所有人眼中的信誉 [code default]。
- 不要在一天内第三次使用相同标题:这会被自动标记为 spam [code default]。
- 不要未披露 AI 或过度依赖 AI:读者可以在自己的信息流中降低 AI 内容的排名 [platform]。
Tags
标签
- #showdev: your project or company launch; "not overly corporate or salesy".
- #news: a launched or updated product, library or service, with a brief summary and the source.
- #contributorswanted: contributor requests.
- #opensource: running projects, licensing, advocacy; project promotion, announcements and contributor requests banned.
- #beginners: beginners to programming or to a language, not "new to our tool"; a 1-2 sentence plug at the end allowed.
- #discuss: a question, prompt or topic that starts a discussion.
- Language and framework tags: focused content; add the framework tag.
For limits, rate caps and source labels, read references/templates-and-limits.md.
- #showdev: 你的项目或公司发布;内容不应“过度企业化或销售味太重”。
- #news: 已发布或更新的产品、库或服务,需要提供简要摘要和来源。
- #contributorswanted: 招募贡献者。
- #opensource: 正在维护的项目、许可证和社区倡导;禁止项目推广、发布公告和贡献者招募。
- #beginners: 面向编程新手或某种语言的新手,而不是“刚开始使用你的工具的人”;允许在结尾用 1 至 2 句话顺带提及。
- #discuss: 能发起讨论的问题、话题或主题。
- 语言和框架标签: 内容必须聚焦;还要添加相应的框架标签。
有关限制、频率上限和来源标注,请阅读 references/templates-and-limits.md。
Flagged, removed or buried
帖子被标记、删除或降权时
- Stop re-posting; a repeat makes it worse.
- Check for a removed tag or moderator comment, and fix the post against the tag rule.
- Appeal once, at dev.to/appeal (signed in) or support@dev.to, with the fix described; a human reviews it.
- 停止重复发布;重复发布只会让情况更糟。
- 检查是否存在被移除的标签或版主评论,并按照标签规则修正帖子。
- 申诉一次:登录后访问 dev.to/appeal,或发送邮件至 support@dev.to,并说明所做的修正;由人工审核。
Cadence
发布节奏
- Weeks 1-2, earn first. Each poster comments substantively on 3-5 posts a week in the target tags [practitioner]. Create the organization from a personal account; members join with their own accounts. No links.
- Week 3, wire syndication. RSS import into the organization per the rules above; publish the best drafts one at a time. The rest stay on the blog.
- Weeks 3-8, publish. One full post every one or two weeks; answer every comment within 24 hours.
- Launch week, week 5 at the earliest. A date before that shortens earn-first, never skips it. One story-led #showdev post plus a #discuss question; teammates comment with substance, never react on cue.
- Monthly. Read the organization dashboard; drop tags that drew nothing.
- 第 1 至 2 周,先赢取信任。 每位发帖者每周在目标标签下对 3 至 5 篇帖子发表有实质内容的评论 [practitioner]。使用个人账号创建 organization;成员使用自己的账号加入。不得带链接。
- 第 3 周,配置内容同步。 按照上述规则,将 RSS 导入 organization;逐篇发布最佳草稿,其余内容保留在博客上。
- 第 3 至 8 周,持续发布。 每隔一至两周发布一篇完整帖子;在 24 小时内回复每一条评论。
- 发布周,最早从第 5 周开始。 早于这个时间只能缩短先赢取信任的阶段,绝不能跳过该阶段。发布一篇以叙事为主的 #showdev 帖子和一个 #discuss 问题;团队成员认真发表评论,绝不按提示集中刷 reaction。
- 每月。 查看 organization 仪表板;移除没有带来任何互动的标签。
Measure
衡量
Targets are self-set; DEV publishes no vendor benchmark.
- Organization and author followers, monthly; CTA clicks and referral sessions to the canonical page.
- Reactions and comments per post at day 4, not day 30.
- Hygiene, pass threshold zero: removed tags, spam labels, moderator comments, AI-disclosure notes.
目标由自己设定;DEV 不发布面向厂商的基准数据。
- 每月统计 organization 和作者的关注者数量、CTA 点击次数,以及流向 canonical 页面引荐的访问会话数。
- 查看帖子发布后第 4 天而非第 30 天的 reactions 和评论数。
- 运营健康度的通过阈值为零:被移除标签、spam 标记、版主评论和 AI 披露相关问题备注均须为零。
Output
输出
In order: fit verdict; setup (organization, members, CTA, RSS); ranked surfaces with what moved; per-post tags with each rule; eight-week cadence with owners and hours; filled templates from references/templates-and-limits.md; metrics. Run drafts through your preferred humanizer skill.
按以下顺序输出:适配结论;设置方案(organization、成员、CTA、RSS);排序后的互动载体及发生变化的原因;每篇帖子的标签及其对应规则;包含负责人和工时的八周发布节奏;根据 references/templates-and-limits.md 填写的模板;指标。使用你首选的 humanizer skill 检查草稿。
References
参考资料
- samber/developer-relations-skills@engineering-blog-post - writing the post this skill publishes.
- samber/developer-relations-skills@oss-launch - the launch window a #showdev post belongs to.
- samber/developer-relations-skills@hackernews-playbook - the other launch-day channel.
- samber/developer-relations-skills@dailydev-playbook - daily.dev, which indexes DEV and picks up posts that gain traction there.
- samber/developer-relations-skills@substack-playbook - a newsletter-first alternative.
- samber/developer-relations-skills@medium-playbook - the other cross-posting channel.
- samber/developer-relations-skills@devrel-content-calendar - fitting dev.to slots into the quarter.
- samber/developer-relations-skills@devrel-analytics - attributing referral signups.
- samber/developer-relations-skills@bluesky-dev-playbook - sharing the article on Bluesky through starter packs and dev feeds.
- samber/developer-relations-skills@engineering-blog-post - 用于撰写本 skill 发布的文章。
- samber/developer-relations-skills@oss-launch - #showdev 帖子所属的发布窗口。
- samber/developer-relations-skills@hackernews-playbook - 发布日的另一个渠道。
- samber/developer-relations-skills@dailydev-playbook - daily.dev 会索引 DEV,并挑选在 DEV 上获得互动的帖子。
- samber/developer-relations-skills@substack-playbook - 以 newsletter 为先的替代方案。
- samber/developer-relations-skills@medium-playbook - 另一个交叉发布渠道。
- samber/developer-relations-skills@devrel-content-calendar - 将 dev.to 发布位置安排到季度内容日历中。
- samber/developer-relations-skills@devrel-analytics - 归因引荐注册。
- samber/developer-relations-skills@bluesky-dev-playbook - 通过 starter packs 和开发者信息流在 Bluesky 上分享文章。