|
| 1 | +--- |
| 2 | +title: 博客指南 |
| 3 | +content_type: concept |
| 4 | +weight: 40 |
| 5 | +--- |
| 6 | +<!-- |
| 7 | +title: Blog guidelines |
| 8 | +content_type: concept |
| 9 | +weight: 40 |
| 10 | +--> |
| 11 | + |
| 12 | +<!-- overview --> |
| 13 | + |
| 14 | +<!-- |
| 15 | +These guidelines cover the main Kubernetes blog and the Kubernetes |
| 16 | +contributor blog. |
| 17 | +
|
| 18 | +All blog content must also adhere to the overall policy in the |
| 19 | +[content guide](/docs/contribute/style/content-guide/). |
| 20 | +--> |
| 21 | +这些指南涵盖了 Kubernetes 主博客和 Kubernetes 贡献者博客。 |
| 22 | + |
| 23 | +所有博客内容还必须遵循[内容指南](/zh-cn/docs/contribute/style/content-guide/)中的总体政策。 |
| 24 | + |
| 25 | +# {{% heading "prerequisites" %}} |
| 26 | + |
| 27 | +<!-- |
| 28 | +Make sure you are familiar with the introduction sections of |
| 29 | +[contributing to Kubernetes blogs](/docs/contribute/blog/), not just to learn about |
| 30 | +the two official blogs and the differences between them, but also to get an overview |
| 31 | +of the process. |
| 32 | +--> |
| 33 | +确保你熟悉[为 Kubernetes 博客贡献内容](/zh-cn/docs/contribute/blog/)的介绍部分， |
| 34 | +不仅是为了了解两个官方博客及其之间的区别，也是为了对整个过程有一个概览。 |
| 35 | + |
| 36 | +<!-- |
| 37 | +## Original content |
| 38 | +
|
| 39 | +The Kubernetes project accepts **original content only**, in English. |
| 40 | +--> |
| 41 | +Kubernetes 项目仅接受**原创内容**，且必须为英文。 |
| 42 | + |
| 43 | +{{< note >}} |
| 44 | +<!-- |
| 45 | +The Kubernetes project cannot accept content for the blog if it has already been submitted |
| 46 | +or published outside of the Kubernetes project. |
| 47 | +
|
| 48 | +The official blogs are not available as a medium to repurpose existing content from any third |
| 49 | +party as new content. |
| 50 | +--> |
| 51 | +如果内容已经提交或在 Kubernetes 项目之外发布， |
| 52 | +Kubernetes 项目则不能接受该内容用于博客。 |
| 53 | + |
| 54 | +官方博客不作为第三方重新利用已有内容并将其作为新内容发布的媒介。 |
| 55 | +{{< /note >}} |
| 56 | + |
| 57 | +<!-- |
| 58 | +This restriction even carries across to promoting other Linux Foundation and CNCF projects. |
| 59 | +Many CNCF projects have their own blog. These are often a better choice for posts about a specific |
| 60 | +project, even if that other project is designed specifically to work with Kubernetes (or with Linux, |
| 61 | +etc). |
| 62 | +--> |
| 63 | +这一限制甚至延伸至推广其他 Linux 基金会和 CNCF 项目。 |
| 64 | +许多 CNCF 项目都有自己的博客。对于特定项目的帖子，这些博客通常是更好的选择， |
| 65 | +即使那个其他项目是专门为与 Kubernetes （或与 Linux 等）协同工作而设计的。 |
| 66 | + |
| 67 | +<!-- |
| 68 | +## Relevant content |
| 69 | +
|
| 70 | +Articles must contain content that applies broadly to the Kubernetes community. For example, a |
| 71 | +submission should focus on upstream Kubernetes as opposed to vendor-specific configurations. |
| 72 | +For articles submitted to the main blog that are not |
| 73 | +[mirror articles](/docs/contribute/blog/mirroring/), hyperlinks in the article should commonly |
| 74 | +be to the official Kubernetes documentation. When making external references, links should be |
| 75 | +diverse - for example, a submission shouldn't contain only links back to a single company's blog. |
| 76 | +--> |
| 77 | +## 相关内容 |
| 78 | + |
| 79 | +文章必须包含适用于整个 Kubernetes 社区的内容。例如，投稿应侧重于上游 |
| 80 | +Kubernetes，而不是特定供应商的配置。 |
| 81 | +对于提交到主博客且不是[镜像文章](/zh-cn/docs/contribute/blog/mirroring/)的文章， |
| 82 | +文章中的超链接应通常指向官方 Kubernetes 文档。 |
| 83 | +在进行外部引用时，链接应该是多样的 - 例如，投稿不应只包含返回单个公司博客的链接。 |
| 84 | + |
| 85 | +<!-- |
| 86 | +The official Kubernetes blogs are **not** the place for vendor pitches or for articles that promote |
| 87 | +a specific solution from outside Kubernetes. |
| 88 | +
|
| 89 | +Sometimes this is a delicate balance. You can ask in Slack ([#sig-docs-blog](http://kubernetes.slack.com/archives/CJDHVD54J)) |
| 90 | +for guidance on whether a post is appropriate for the Kubernetes blog and / or contributor blog - |
| 91 | +don't hesitate to reach out. |
| 92 | +
|
| 93 | +The [content guide](/docs/contribute/style/content-guide/) applies unconditionally to blog articles |
| 94 | +and the PRs that add them. Bear in mind that some restrictions in the guide state that they are only relevant to documentation; those marked restrictions don't apply to blog articles. |
| 95 | +--> |
| 96 | +官方 Kubernetes 博客**不**是进行供应商宣传或推广 Kubernetes 外部特定解决方案的地方。 |
| 97 | + |
| 98 | +有时，这之间的平衡很微妙。你可以在 Slack （[#sig-docs-blog](http://kubernetes.slack.com/archives/CJDHVD54J)） |
| 99 | +上询问某篇文章是否适合发布在 Kubernetes 博客和/或贡献者博客 - 不要犹豫，随时联系。 |
| 100 | + |
| 101 | +[内容指南](/zh-cn/docs/contribute/style/content-guide/)无条件适用于博客文章及其添加的 PR。 |
| 102 | +请记住，指南中的一些限制仅与文档相关；那些标记的限制不适用于博客文章。 |
| 103 | + |
| 104 | +<!-- |
| 105 | +## Localization |
| 106 | +
|
| 107 | +The website is localized into many languages; English is the “upstream” for all the other |
| 108 | +localizations. Even if you speak another language and would be happy to provide a localization, |
| 109 | +that should be in a separate pull request (see [languages per PR](/docs/contribute/new-content/#languages-per-pr)). |
| 110 | +--> |
| 111 | +## 本地化 |
| 112 | + |
| 113 | +网站已被本地化为多种语言；英文是所有其他本地化的“上游”。即使你懂另一种语言并愿意提供本地化， |
| 114 | +这也应该是一个单独的 PR（参见[每个 PR 的语言](/zh-cn/docs/contribute/new-content/#languages-per-pr)）。 |
| 115 | + |
| 116 | +<!-- |
| 117 | +## Copyright and reuse |
| 118 | +
|
| 119 | +You must write [original content](#original-content) and you must have permission to license |
| 120 | +that content to the Cloud Native Computing Foundation (so that the Kubernetes project can |
| 121 | +legally publish it). |
| 122 | +This means that not only is direct plagiarism forbidden, you cannot write a blog article if |
| 123 | +you don't have permission to meet the CNCF copyright license conditions (for example, if your |
| 124 | +employer has a policy about intellectual property that restricts what you are allowed to do). |
| 125 | +
|
| 126 | +The [license](http://github.com/kubernetes/website/blob/main/LICENSE) for the blog allows |
| 127 | +commercial use of the content for commercial purposes, but not the other way around. |
| 128 | +--> |
| 129 | +## 版权和重用 |
| 130 | + |
| 131 | +你必须编写[原创内容](#original-content)， |
| 132 | +并且你必须拥有将该内容授权给云原生计算基金会（Cloud Native Computing Foundation） |
| 133 | +的权限（这样 Kubernetes 项目才能合法发布它）。 |
| 134 | +这意味着不仅直接抄袭是被禁止的，如果你没有权限满足 CNCF 版权许可条件 |
| 135 | +（例如，如果你的雇主有关于知识产权的政策限制了你能做的事情）， |
| 136 | +你也不能撰写博客文章。 |
| 137 | + |
| 138 | +[license](http://github.com/kubernetes/website/blob/main/LICENSE) |
| 139 | +允许将博客的内容用于商业目的，但反之则不然。 |
| 140 | + |
| 141 | +<!-- |
| 142 | +## Special interest groups and working groups |
| 143 | +
|
| 144 | +Topics related to participation in or results of Kubernetes SIG activities are always on |
| 145 | +topic (see the work in the [Contributor Comms Team](http://github.com/kubernetes/community/blob/master/communication/contributor-comms/blogging-resources/blog-guidelines.md#contributor-comms-blog-guidelines) |
| 146 | +for support on these posts). |
| 147 | +
|
| 148 | +The project typically [mirrors](/docs/contribute/blog/mirroring/) these articles to both blogs. |
| 149 | +--> |
| 150 | +## 特别兴趣小组和工作组 |
| 151 | + |
| 152 | +与参与 Kubernetes SIG 活动或其成果相关的主题总是合适的 |
| 153 | +（参见[贡献者通讯团队](http://github.com/kubernetes/community/blob/master/communication/contributor-comms/blogging-resources/blog-guidelines.md#contributor-comms-blog-guidelines)中的工作以获得这些帖子的支持）。 |
| 154 | + |
| 155 | +该项目通常会将这些文章[镜像](/zh-cn/docs/contribute/blog/mirroring/)到两个博客上。 |
| 156 | + |
| 157 | +<!-- |
| 158 | +## National restrictions on content |
| 159 | +
|
| 160 | +The Kubernetes website has an Internet Content Provider (ICP) licence from the government of China. Although it's unlikely to be a problem, Kubernetes cannot publish articles that would be blocked by the Chinese government's official filtering of internet content. |
| 161 | +--> |
| 162 | +## 国家对内容的限制 |
| 163 | + |
| 164 | +Kubernetes 网站拥有中国政府颁发的互联网内容提供者（ICP）许可证。 |
| 165 | +Kubernetes 不能发布那些会被中国政府官方网络内容过滤系统阻止的文章 |
| 166 | +（尽管这种情况不太可能发生）。 |
| 167 | + |
| 168 | +<!-- |
| 169 | +## Blog-specific content guidance {#what-we-publish} |
| 170 | +
|
| 171 | +As well as the general [style guide](/docs/contribute/style/style-guide/), blog articles should (not must) align to |
| 172 | +the [blog-specific style recommendations](/docs/contribute/blog/article-submission/#article-content). |
| 173 | +
|
| 174 | +The remainder of this page is additional guidance; these are not strict rules that articles |
| 175 | +must follow, but reviewers are likely to (and should) ask for edits to articles that are |
| 176 | +obviously not aligned with the recommendations here. |
| 177 | +--> |
| 178 | +## 博客特定内容指南 {#what-we-publish} |
| 179 | + |
| 180 | +除了通用的[风格指南](/zh-cn/docs/contribute/style/style-guide/)外， |
| 181 | +博客文章应该（但不是必须）遵循 |
| 182 | +[博客特定风格建议](/zh-cn/docs/contribute/blog/article-submission/#article-content)。 |
| 183 | + |
| 184 | +本页面其余部分为附加指南；这些并不是文章必须遵守的严格规则，但如果文章明显不符合这里的建议， |
| 185 | +审稿人可能会（也应该）要求对文章进行编辑。 |
| 186 | + |
| 187 | +<!-- |
| 188 | +### Diagrams and illustrations {#illustrations} |
| 189 | +
|
| 190 | +For [illustrations](/docs/contribute/blog/article-submission/#illustrations) - including diagrams or charts - use the [figure shortcode](http://gohugo.io/content-management/shortcodes/#figure) |
| 191 | +where feasible. You should set an `alt` attribute for accessibility. |
| 192 | +--> |
| 193 | +### 图表和插图 {#illustrations} |
| 194 | + |
| 195 | +对于[插图](/zh-cn/docs/contribute/blog/article-submission/#illustrations) |
| 196 | +—— 包括图表或图形 |
| 197 | +—— 在可行的情况下，使用[图形简码](http://gohugo.io/content-management/shortcodes/#figure)。 |
| 198 | +你应该设置一个`alt`属性以提高可访问性。 |
| 199 | + |
| 200 | +<!-- |
| 201 | +Use vector images for illustrations, technical diagrams and similar graphics; SVG format is recommended as a strong preference. |
| 202 | +
|
| 203 | +Articles that use raster images for illustrations are more difficult to maintain and in some |
| 204 | +cases the blog team may ask authors to revise the article before it could be published. |
| 205 | +--> |
| 206 | +使用矢量图像进行插图、技术图表和类似图形；强烈建议使用 SVG 格式。 |
| 207 | + |
| 208 | +使用光栅图像进行插图的文章更难以维护，在某些情况下， |
| 209 | +博客团队可能会要求作者在文章可以发布之前进行修改。 |
| 210 | + |
| 211 | +<!-- |
| 212 | +### Timelessness |
| 213 | +
|
| 214 | +Blog posts should aim to be future proof |
| 215 | +
|
| 216 | +- Given the development velocity of the project, SIG Docs prefers _timeless_ writing: content that |
| 217 | + won't require updates to stay accurate for the reader. |
| 218 | +- It can be a better choice to add a tutorial or update official documentation than to write a |
| 219 | + high level overview as a blog post. |
| 220 | +- Consider concentrating the long technical content as a call to action of the blog post, and |
| 221 | + focus on the problem space or why readers should care. |
| 222 | +--> |
| 223 | +### 时效性 |
| 224 | + |
| 225 | +博客文章应力求面向未来： |
| 226 | + |
| 227 | +- 鉴于项目的开发速度，SIG Docs 倾向于 **timeless** 写作：即不需要更新就能保持准确的内容。 |
| 228 | +- 相较于撰写高层次概述的博客文章，添加教程或更新官方文档可能是更好的选择。 |
| 229 | +- 考虑将长技术内容集中在博客文章的呼吁行动中，并关注问题空间或为什么读者应该关心。 |
| 230 | + |
| 231 | +<!-- |
| 232 | +### Content examples |
| 233 | +
|
| 234 | +Here are some examples of content that is appropriate for the |
| 235 | +[main Kubernetes blog](/docs/contribute/blog/#main-blog): |
| 236 | +--> |
| 237 | +### 内容示例 |
| 238 | + |
| 239 | +以下是一些适合 |
| 240 | +[主 Kubernetes 博客](/zh-cn/docs/contribute/blog/#main-blog)的内容示例： |
| 241 | + |
| 242 | +<!-- |
| 243 | +* Announcements about new Kubernetes capabilities |
| 244 | +* Explanations of how to achieve an outcome using Kubernetes; for example, tell us about your |
| 245 | + low-toil improvement on the basic idea of a rolling deploy |
| 246 | +* Comparisons of several different software options that have a link to Kubernetes and cloud native. It's |
| 247 | + OK to have a link to one of these options so long as you fully disclose your conflict of |
| 248 | + interest / relationship. |
| 249 | +* Stories about problems or incidents, and how you resolved them |
| 250 | +* Articles discussing building a cloud native platform for specific use cases |
| 251 | +* Your opinion about the good or bad points about Kubernetes |
| 252 | +--> |
| 253 | +* 关于 Kubernetes 新功能的公告 |
| 254 | +* 解释如何使用 Kubernetes 实现某个目标；例如，告诉我们你在基本滚动更新想法上的低操作改进 |
| 255 | +* 比较几个与 Kubernetes 和云原生有关的不同软件选项。可以提及其中一个选项的链接，但必须充分披露你的利益冲突/关系。 |
| 256 | +* 讲述问题或事件的故事，以及你是如何解决它们的 |
| 257 | +* 讨论构建针对特定用例的云原生平台的文章 |
| 258 | +* 你对 Kubernetes 的优缺点的看法 |
| 259 | +<!-- |
| 260 | +* Announcements and stories about non-core Kubernetes, such as the Gateway API |
| 261 | +* [Post-release announcements and updates](#post-release-comms) |
| 262 | +* Messages about important Kubernetes security vulnerabilities |
| 263 | +* Kubernetes projects updates |
| 264 | +* Tutorials and walkthroughs |
| 265 | +* Thought leadership around Kubernetes and cloud native |
| 266 | +* The components of Kubernetes are purposely modular, so writing about existing integration |
| 267 | + points like CNI and CSI are on topic. Provided you don't write a vendor pitch, you can also write |
| 268 | + about what is on the other end of these integrations. |
| 269 | +--> |
| 270 | +* 关于非核心 Kubernetes 的公告和故事，例如 Gateway API |
| 271 | +* [发布后公告和更新](#post-release-comms) |
| 272 | +* 关于重要的 Kubernetes 安全漏洞的消息 |
| 273 | +* Kubernetes 项目更新 |
| 274 | +* 教程和操作指南 |
| 275 | +* 围绕 Kubernetes 和云原生的思想领导力 |
| 276 | +* Kubernetes 的组件是故意设计成模块化的，因此撰写关于现有集成点的文章 |
| 277 | + （如 CNI 和 CSI）是相关的。只要你不是在写供应商宣传，你也可以写这些集成的另一端是什么。 |
| 278 | + |
| 279 | +<!-- |
| 280 | +Here are some examples of content that is appropriate for the Kubernetes |
| 281 | +[contributor blog](/docs/contribute/blog/#contributor-blog): |
| 282 | +
|
| 283 | +* articles about how to test your change to Kubernetes code |
| 284 | +* content around non-code contribution |
| 285 | +* discussions about alpha features where the design is still under discussion |
| 286 | +* "Meet the team" articles about working groups, special interest groups, etc. |
| 287 | +* a guide about how to write secure code that will become part of Kubernetes itself |
| 288 | +* articles about maintainer summits and the outcome of those summits |
| 289 | +--> |
| 290 | +这里有一些适合 Kubernetes [贡献者博客](/zh-cn/docs/contribute/blog/#contributor-blog)的内容示例： |
| 291 | + |
| 292 | +* 关于如何测试你对 Kubernetes 代码的更改的文章 |
| 293 | +* 围绕非代码贡献的内容 |
| 294 | +* 讨论设计仍在讨论中的 alpha 特性的文章 |
| 295 | +* “认识团队”文章，介绍工作组、特别兴趣小组等 |
| 296 | +* 关于如何编写将成为 Kubernetes 一部分的安全代码的指南 |
| 297 | +* 关于维护者峰会及其成果的文章 |
| 298 | + |
| 299 | +<!-- |
| 300 | +### Examples of content that wouldn't be accepted {#what-we-do-not-publish} |
| 301 | +
|
| 302 | +However, the project will not publish: |
| 303 | +--> |
| 304 | +### 不会被接受的内容示例 {#what-we-do-not-publish} |
| 305 | + |
| 306 | +然而，项目不会发布： |
| 307 | + |
| 308 | +<!-- |
| 309 | +* vendor pitches |
| 310 | +* an article you've published elsewhere, even if only to your own low-traffic blog |
| 311 | +* large chunks of example source code with only a minimal explanation |
| 312 | +* updates about an external project that works with our relies on Kubernetes (put those on |
| 313 | + the external project's own blog) |
| 314 | +* articles about using Kubernetes with a specific cloud provider |
| 315 | +* articles that criticise specific people, groups of people, or businesses |
| 316 | +* articles that have important technical mistakes or misleading details (for example: if you |
| 317 | + recommend turning off an important security control in production clusters, because it can |
| 318 | + be inconvenient, the Kubernetes project is likely to reject the article). |
| 319 | +--> |
| 320 | +* 供应商宣传 |
| 321 | +* 你在其他地方已发布过的文章，即使是发布在你自己的低流量博客上 |
| 322 | +* 仅有少量解释的大段示例源代码 |
| 323 | +* 关于外部项目的更新，如果该项目依赖于 Kubernetes（请将这些内容发布在外项目自己的博客上） |
| 324 | +* 关于与特定云提供商一起使用 Kubernetes 的文章 |
| 325 | +* 批评特定人士、人群或企业的文章 |
| 326 | +* 包含重要技术错误或误导性细节的文章（例如： |
| 327 | + 如果你建议在生产集群中关闭一个重要安全控制，因为其可能带来不便， |
| 328 | + Kubernetes 项目可能会拒绝该文章） |
0 commit comments