Add guide to blog contributions

content/en/docs/contribute/_index.md

@@ -14,16 +14,18 @@ card:
 <!-- overview -->
 
 There are lots of ways to contribute to Kubernetes. You can work on designs for new features,
-you can document the code we already have, you can write for our [blog](/blog). There's more:
-you can implement those new features or fix bugs. You can help people join our contributor
-community, or support existing contributors.
+you can document the code we already have, you can [write for our blogs](/docs/contribute/blog/).
+There's more: you can implement those new features or fix bugs. You can help people join our
+contributor community, or support existing contributors.
 
 With all these different ways to make a difference to the project, we - Kubernetes - have made
 a dedicated website: https://k8s.dev/. You can go there to learn more about
 contributing to Kubernetes.
 
-If you specifically want to learn about contributing to _this_ documentation, read
-[Contribute to Kubernetes documentation](/docs/contribute/docs/).
+If you specifically want to learn about contributing to the documentation or
+other parts of _this_ website, read [Contribute to Kubernetes documentation](/docs/contribute/docs/).
+If you specifically want to help with the official Kubernetes blogs, read
+[Contributing to Kubernetes blogs](/docs/contribute/blog/).
 
 You can also read the
 {{< glossary_tooltip text="CNCF" term_id="cncf" >}}

content/en/docs/contribute/blog/_index.md

@@ -0,0 +1,66 @@
+---
+title: Contributing to Kubernetes blogs
+slug: blog-contribution
+content_type: concept
+weight: 15
+simple_list: true
+---
+
+<!-- overview -->
+
+There are two official Kubernetes blogs, and the CNCF has [its own blog](https://www.cncf.io/blog/) where you can cover Kubernetes too.
+For the main Kubernetes blog, we (the Kubernetes project) like to publish articles with different perspectives and special focuses, that have a link to Kubernetes.
+
+With only a few special case exceptions, we only publish content that hasn't been submitted or published anywhere else.
+
+Read the [blog guidelines](/docs/contribute/blog/guidelines/#what-we-publish) for more about that aspect.
+
+## Official Kubernetes blogs
+
+### Main blog
+
+The main [Kubernetes blog](/blog/) is used by the project to communicate new features, community reports, and any
+news that might be relevant to the Kubernetes community. This includes end users and developers.
+Most of the blog's content is about things happening in the core project, but Kubernetes
+as a project encourages you to submit about things happening elsewhere in the ecosystem too!
+
+Anyone can write a blog post and submit it for publication. With only a few special case exceptions, we only publish content that hasn't been submitted or published anywhere else.
+
+### Contributor blog
+
+The [Kubernetes contributor blog](https://k8s.dev/blog/) is aimed at an audience of people who
+work **on** Kubernetes more than people who work **with** Kubernetes. The Kubernetes project
+deliberately publishes some articles to both blogs.
+
+Anyone can write a blog post and submit it for review.
+
+## Article updates and maintenance {#maintenance}
+
+The Kubernetes project does not maintain older articles for its blogs. This means that any
+published article more than one year old will normally **not** be eligible for issues or pull
+requests that ask for changes. To avoid establishing precedent, even technically correct pull
+requests are likely to be rejected.
+
+However, there are exceptions like the following:
+
+* (updates to) articles marked as [evergreen](#maintenance-evergreen)
+* removing or correcting articles giving advice that is now wrong and dangerous to follow
+* fixes to ensure that an existing article still renders correctly
+
+For any article that is over a year old and not marked as _evergreen_, the website automatically
+displays a notice that the content may be stale.
+
+### Evergreen articles {#maintenance-evergreen}
+
+You can mark an article as evergreen by setting `evergreen: true` in the front matter.
+
+We only mark blog articles as maintained (`evergreen: true` in front matter) if the Kubernetes project
+can commit to maintaining them indefinitely. Some blog articles absolutely merit this; for example, the release comms team always marks official release announcements as evergreen.
+
+## {{% heading "whatsnext" %}}
+
+* Discover the official blogs:
+  * [Kubernetes blog](/blog/)
+  * [Kubernetes contributor blog](https://k8s.dev/blog/)
+
+* Read about [reviewing blog pull requests](/docs/contribute/review/reviewing-prs/#blog)

content/en/docs/contribute/blog/buddying.md

@@ -0,0 +1,109 @@
+---
+title: Helping as a blog writing buddy
+slug: writing-buddy
+content_type: concept
+weight: 70
+---
+
+<!-- overview -->
+
+There are two official Kubernetes blogs, and the CNCF has its own blog where you can cover Kubernetes too.
+Read [contributing to Kubernetes blogs](/docs/contribute/blog/) to learn about these two blogs.
+
+When people contributor to either blog as an author, the Kubernetes project pairs up authors
+as _writing buddies_. This page explains how to fulfil the buddy role.
+
+You should make sure that you have at least read an outline of [article submission](/docs/contribute/blog/submission/)
+before you read on within this page.
+
+<!-- body -->
+
+## Buddy responsibilities
+
+As a writing buddy, you:
+
+* help the blog team get articles ready to merge and to publish
+* support your buddy to produce content that is good to merge
+* provide a review on the article that your buddy has written
+
+
+When the team pairs you up with another author, the idea is that you both support each other by
+reviewing the other author's draft article.
+Most people reading articles on the Kubernetes blog are not experts; the content should
+try to make sense for that audience, or at least to support non-expert readers appropriately.
+
+The blog team are also there to help you both along the journey from draft to publication.
+They will either be directly able to approve your article for publication, or can arrange for
+the approval to happen.
+
+## Supporting the blog team
+
+Your main responsibility here is to communicate about your capacity, availability and progress
+in a reasonable timeline. If many weeks go by and your buddy hasn't heard from you, it makes
+the overall work take more time.
+
+## Supporting your buddy
+
+There are two parts to the process
+
+{{< tabs name="buddy_support" >}}
+{{% tab name="Collaborative editing" %}}
+**(This is the recommended option)**
+
+The blog team recommend that the main author for the article sets up collaborative editing
+using either a Google Doc or HackMD (their choice). The main author then shares that document
+with the following people:
+
+ * Any co-authors
+ * You (their writing buddy)
+ * Ideally, with a nominated
+person from the blog team.
+
+As a writing buddy, you then read the draft text and either directly make suggestions or provide
+feedback in a different way. The author of the blog is very commonly also **your** writing buddy in turn, so they will provide the
+same kind of feedback on the draft for your blog article.
+
+Your role here is to recommend the smallest set of changes that will get the article look good
+for publication. If there's a diagram that really doesn't make sense, or the writing is really
+unclear: provide feedback. If you have a slight different of opinion about wording or punctuation,
+skip it. Let the article author(s) write in their own style, provided that they align to
+the [blog guidelines](/docs/contribute/blog/guidelines/).
+
+After this is ready, the lead author will open a pull request and use Markdown to submit the
+article. You then provide a [review](#pull-request-review).
+{{% /tab %}}
+{{% tab name="Markdown / Git editing" %}}
+Some authors prefer to start with
+[collaborative editing](#buddy-support-0); others like to go straight into
+GitHub.
+
+Whichever route they take, your role is to provide feedback that lets the blog team provide
+a simple signoff and confirm that the article can merge as a draft. See
+[submitting articles to Kubernetes blogs](/docs/contribute/blog/submission/) for what the authors
+need to do.
+
+Use GitHub suggestions to point out any required changes.
+
+Once the Markdown and other content (such as images) look right, you provide a
+formal [review](#pull-request-review).
+{{% /tab %}}
+{{< /tabs >}}
+
+
+## Pull request review
+
+Follow the [blog](/docs/contribute/review/reviewing-prs/#blog) section of _Reviewing pull requests_.
+
+When you think that the open blog pull request is good enough to merge, add the `/lgtm` comment to the pull request.
+
+This indicates to the repository automation tooling (Prow) that the content "looks good to me". Prow moves things forward. The `/lgtm` command lets you add your opinion to the record whether or not you are formally a member of the Kubernetes project.
+
+Either you or the article author(s) should let the blog team know that there is an article
+ready for signoff. It should already be marked as `draft: true` in the front matter, as
+explained in the submission guidance.
+
+## Subsequent steps
+
+For you as a writing buddy, **there is no step four**. Once the pull request is good to merge,
+the blog team (or, for the contributor site, the contributor comms team) take things from there.
+It's possible that you'll need to return to an earlier step based on feedback, but you can usually expect that your work as a buddy is done.

content/en/docs/contribute/blog/guidelines.md

@@ -0,0 +1,169 @@
+---
+title: Blog guidelines
+content_type: concept
+weight: 40
+---
+
+<!-- overview -->
+
+These guidelines cover the main Kubernetes blog and the Kubernetes
+contributor blog.
+
+All blog content must also adhere to the overall policy in the
+[content guide](/docs/contribute/style/content-guide/).
+
+# {{% heading "prerequisites" %}}
+
+Make sure you are familiar with the introduction sections of
+[contributing to Kubernetes blogs](/docs/contribute/blog/), not just to learn about
+the two official blogs and the differences between them, but also to get an overview
+of the process.
+
+## Original content
+
+The Kubernetes project accepts **original content only**, in English.
+
+{{< note >}}
+The Kubernetes project cannot accept content for the blog if it has already been submitted
+or published outside of the Kubernetes project.
+
+The official blogs are not available as a medium to repurpose existing content from any third
+party as new content.
+{{< /note >}}
+
+This restriction even carries across to promoting other Linux Foundation and CNCF projects.
+Many CNCF projects have their own blog. These are often a better choice for posts about a specific
+project, even if that other project is designed specifically to work with Kubernetes (or with Linux,
+etc).
+
+## Relevant content
+
+Articles must contain content that applies broadly to the Kubernetes community. For example, a
+submission should focus on upstream Kubernetes as opposed to vendor-specific configurations.
+For articles submitted to the main blog that are not
+[mirror articles](/docs/contribute/blog/mirroring/), hyperlinks in the article should commonly
+be to the official Kubernetes documentation. When making external references, links should be
+diverse - for example, a submission shouldn't contain only links back to a single company's blog.
+
+The official Kubernetes blogs are **not** the place for vendor pitches or for articles that promote
+a specific solution from outside Kubernetes.
+
+Sometimes this is a delicate balance. You can ask in Slack ([#sig-docs-blog](https://kubernetes.slack.com/archives/CJDHVD54J))
+for guidance on whether a post is appropriate for the Kubernetes blog and / or contributor blog -
+don't hesitate to reach out.
+
+The [content guide](/docs/contribute/style/content-guide/) applies unconditionally to blog articles
+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.
+
+## Localization
+
+The website is localized into many languages; English is the “upstream” for all the other
+localizations. Even if you speak another language and would be happy to provide a localization,
+that should be in a separate pull request (see [languages per PR](/docs/contribute/new-content/#languages-per-pr)).
+
+## Copyright and reuse
+
+You must write [original content](#original-content) and you must have permission to license
+that content to the Cloud Native Computing Foundation (so that the Kubernetes project can
+legally publish it).
+This means that not only is direct plagiarism forbidden, you cannot write a blog article if
+you don't have permission to meet the CNCF copyright license conditions (for example, if your
+employer has a policy about intellectual property that restricts what you are allowed to do).
+
+The [license](https://github.com/kubernetes/website/blob/main/LICENSE) for the blog allows
+commercial use of the content for commercial purposes, but not the other way around.
+
+## Special interest groups and working groups
+
+Topics related to participation in or results of Kubernetes SIG activities are always on
+topic (see the work in the [Contributor Comms Team](https://github.com/kubernetes/community/blob/master/communication/contributor-comms/blogging-resources/blog-guidelines.md#contributor-comms-blog-guidelines)
+for support on these posts).
+
+The project typically [mirrors](/docs/contribute/blog/mirroring/) these articles to both blogs.
+
+
+## National restrictions on content
+
+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.
+
+## Blog-specific content guidance {#what-we-publish}
+
+As well as the general [style guide](/docs/contribute/style/style-guide/), blog articles should (not must) align to
+the [blog-specific style recommendations](/docs/contribute/blog/article-submission/#article-content).
+
+The remainder of this page is additional guidance; these are not strict rules that articles
+must follow, but reviewers are likely to (and should) ask for edits to articles that are
+obviously not aligned with the recommendations here.
+
+### Diagrams and illustrations {#illustrations}
+
+For [illustrations](/docs/contribute/blog/article-submission/#illustrations) - including diagrams or charts - use the [figure shortcode](https://gohugo.io/content-management/shortcodes/#figure)
+where feasible. You should set an `alt` attribute for accessibility.
+
+Use vector images for illustrations, technical diagrams and similar graphics; SVG format is recommended as a strong preference.
+
+Articles that use raster images for illustrations are more difficult to maintain and in some
+cases the blog team may ask authors to revise the article before it could be published.
+
+### Timelessness
+
+Blog posts should aim to be future proof
+
+- Given the development velocity of the project, SIG Docs prefers _timeless_ writing: content that
+  won't require updates to stay accurate for the reader.
+- It can be a better choice to add a tutorial or update official documentation than to write a
+  high level overview as a blog post.
+- Consider concentrating the long technical content as a call to action of the blog post, and
+  focus on the problem space or why readers should care.
+
+
+### Content examples
+
+Here are some examples of content that is appropriate for the
+[main Kubernetes blog](/docs/contribute/blog/#main-blog):
+
+* Announcements about new Kubernetes capabilities
+* Explanations of how to achieve an outcome using Kubernetes; for example, tell us about your
+  low-toil improvement on the basic idea of a rolling deploy
+* Comparisons of several different software options that have a link to Kubernetes and cloud native. It's
+  OK to have a link to one of these options so long as you fully disclose your conflict of
+  interest / relationship.
+* Stories about problems or incidents, and how you resolved them
+* Articles discussing building a cloud native platform for specific use cases
+* Your opinion about the good or bad points about Kubernetes
+* Announcements and stories about non-core Kubernetes, such as the Gateway API
+* [Post-release announcements and updates](#post-release-comms)
+* Messages about important Kubernetes security vulnerabilities
+* Kubernetes projects updates
+* Tutorials and walkthroughs
+* Thought leadership around Kubernetes and cloud native
+* The components of Kubernetes are purposely modular, so writing about existing integration
+  points like CNI and CSI are on topic. Provided you don't write a vendor pitch, you can also write
+  about what is on the other end of these integrations.
+
+
+Here are some examples of content that is appropriate for the Kubernetes
+[contributor blog](/docs/contribute/blog/#contributor-blog):
+
+* articles about how to test your change to Kubernetes code
+* content around non-code contribution
+* discussions about alpha features where the design is still under discussion
+* "Meet the team" articles about working groups, special interest groups, etc.
+* a guide about how to write secure code that will become part of Kubernetes itself
+* articles about maintainer summits and the outcome of those summits
+
+### Examples of content that wouldn't be accepted {#what-we-do-not-publish}
+
+However, the project will not publish:
+
+* vendor pitches
+* an article you've published elsewhere, even if only to your own low-traffic blog
+* large chunks of example source code with only a minimal explanation
+* updates about an external project that works with our relies on Kubernetes (put those on
+  the external project's own blog)
+* articles about using Kubernetes with a specific cloud provider
+* articles that criticise specific people, groups of people, or businesses
+* articles that have important technical mistakes or misleading details (for example: if you
+  recommend turning off an important security control in production clusters, because it can
+  be inconvenient, the Kubernetes project is likely to reject the article).
+