Skip to content

Latest commit

 

History

History
58 lines (42 loc) · 5.12 KB

blog-guidelines.md

File metadata and controls

58 lines (42 loc) · 5.12 KB
Raw

CNCF Blog Guidelines

CNCF Blog Overview

The Cloud Native Computing Foundation (CNCF) blog serves as a channel for CNCF members, project maintainers of graduated and incubating projects, CNCF Technical Advisory Groups (TAGs), ambassadors to share content with the cloud native community.

The content on our blog consists of:

  • Articles about graduated or incubating CNCF projects
  • Technical content and how-to’s
  • Stories about cloud native and CNCF project deployments
  • Use cases and success stories
  • Industry insight into cloud native adoption
  • Reports from CNCF events

Other topics are welcome, but it needs to have a direct link to the CNCF community.

We accept content from CNCF members, project maintainers of graduated and incubating projects, CNCF TAGs, CNCF ambassadors. The content needs to be originally published within the last 2 months.

Please note that we do not accept AI-generated posts.

Blog type definitions:

  • Project blog: Any blog post on a graduated or incubating project. This is written by or on behalf of the project. If written by a member about a project, this blog is classified as a Project blog. An example is a Harbor blog written by the VMware team. The blog is classified as a Project blog.
  • Member blog: Any blog post written by a member. The blog must comply with the blog guidelines. A member can write about any open source project, including a CNCF Sandbox project. If a CNCF member writes solely about a CNCF graduated or incubating project and on behalf of the project, it is classified as a Project blog. If the blog contains information about a CNCF graduated or incubating project and includes information on how to do something with that project, it is classified as a Member blog.
  • Technical Advisory Group (TAG) blog: A blog written by a TAG team member(s) is classified as a TAG blog. If a CNCF member writes a blog on behalf of the TAG, it is classified as a TAG blog. If a member writes a blog about a TAG, it is classified as a Member blog.
  • Ambassador blog: This is a blog written by one of the CNCF Ambassadors.
  • CNCF Staff: This is a blog written by a CNCF staff member. If the staff member is writing a blog on behalf of a project or a TAG, it is classified as a Project or TAG blog.
  • Project internships and scholarship recipients: This is a blog that is written about a scholarship or internship related to a CNCF event or project.

Content

The CNCF blog audience is developers, IT operators, and cloud native and open source enthusiasts. Keep this in mind as you develop your blog content.

Some things to think about:

  • Posts from members must be vendor-neutral. The post may mention a vendor’s name as it relates to specific open source projects, project deployments, adoption paths, their hosting of an in-person event or speaking at an event, or other indications of meaningful participation in the community, but it shouldn’t feel like an advertisement for your services or company. We do not accept announcements or press releases to the CNCF blog.

  • The most interesting posts are how-to blogs, blogs with technical content, and those that teach or show how to do something in a way others may not have thought of.

  • Blog posts that show hurdles that were encountered and explain how they were overcome often do very well as the community is looking to learn.

  • Content on how to choose between different technologies and how to accommodate different legacy issues and cloud platforms is a good way to highlight your learnings and share with the community.

  • When showing upstreaming of a patch fixing an issue for others, link back to the Github issue, so readers can follow along.

  • Critical commentary or broad issues must be approached with sensitivity, professionalism, and tact in a way that is beneficial and positive for the community.

  • Your post must be your content, but can be published elsewhere with a right to republish. All content should have an author and be published Creative Commons with Attribution.

Members can add 1-2 sentences at the end of their blog with a link to an external site such as their website or a gated asset. Examples for best practices:

  • Share contact info of speaker - twitter, slack, email
  • Links to company websites
  • Links to projects websites or Github
  • Can advertise if they are hiring and who to contact if interested

Note: This is not a link to a CNCF website or form on the CNCF website.

CNCF will review the statement, as we do for the content for the blog, to approve the content. If changes are needed, we will provide suggested changes.

Promotion

Please feel free to share the blog on Twitter and reach out to blog@cncf.io if you would like to request CNCF's handle RTs.

How to submit for consideration

Please submit a brief summary and the topic of the post to blog@cncf.io for consideration. Or you can supply the blog for review. We will respond with a proposed date of publication or if it’s not suitable for the CNCF blog, we will provide feedback and direction.

If you are submitting an article or presentation that already exists, please send it in its entirety with a note on the expressed permission from the owner of the content.