Joining the project and getting started

Join to become a contributor

You must meet the following prerequisites before you are able to contribute to the docs. The following steps are specific to docs contributions. For more information about contributing to the Knative project, see the Knative contribution guidelines.

  1. If you don’t already have an account, you must create a new GitHub account.

  2. Become a Knative Member by subscribing to

    Learn more about community roles

  3. Read and follow the Knative Code of Conduct.

    By participating, you are expected to uphold this code. Please report all unacceptable behavior to

  4. Sign the contributor license agreements (CLA):

    Knative requires the Google CLA.

    Important: You must fill out the CLA with the same email address that you used to create your GitHub account. Also see the note about private accounts.

    Once you are CLA’ed, we’ll be able to accept your pull requests. This is necessary because you own the copyright to your changes, even after your contribution becomes part of this project. So this agreement simply gives us permission to use and redistribute your contributions as part of the project.

    Private accounts not supported: Your contributions are verified using the email address for which you use to sign the CLA. Therefore, setting your GitHub account to private is unsupported because all commits from private accounts are sent from the noreply email address.

Tips: Get involved

There are a couple of different ways to get started with contributing to the Knative documentation:

Get help from the community

Workflow overview

We expect most new content to be written by the subject matter expert (SME) which would be the contributor who actually worked on the feature or example.

When writing new content, focus mostly on technical correctness and thoroughness (it must include all the steps that are required by the target audience). Language should be roughly correct, but don’t need heavy review in this phase.

The goal of adding new content is to get technically correct documentation into the repo before it is lost. Tech Writers may provide some quick guidance on getting documentation into the correct location, but won’t be providing a detailed list of items to change.

Once the raw documentation has made it into the repo, tech writers and other communications experts will review and revise the documentation to make it easier to consume. This will be done as a second PR; it’s often easier for the tech writers to clean up or rewrite a section of prose than to teach an engineer what to do, and most engineers trust the wordsmithing the tech writers produce more than their own.

When revising the content, the tech writer will create a new PR and send it to the original author to ensure that the content is technically correct; they may also ask a few clarifying questions, or add details such as diagrams or notes if needed. It’s not necessarily expected that tech writers will actually execute the steps of a tutorial — it’s expected that the SME is responsible for a working tutorial or how-to.

What’s next