Tell the project team how you are using cert-manager Take this short anonymous survey

Improve the Navigation and Structure of the cert-manager Website

Project Updates

5 May 2022: Announcing Mehak Saeed as Technical Writer

We are delighted to announce that Mehak Saeed will be the technical writer working on this project. We were extremely impressed with Mehak's presentation during her interview and impressed with her detailed preparations and planning. We look forward to working with her.

Thank you to all the other technical writers who applied for this project.

14 April 2022: Project Accepted

This project was accepted on 14 April 2022.

24 March 2022: Project Registered

We have registered our interest to participate in Google Season of Docs 2022, and have submitted a single project proposal detailed in the remaining of this page.

You have until 27 April 2022 18:00 UTC to apply for the technical writer role.

We will be sharing the name of the selected candidate on Wed 4 May 2022 at 15:00 London Time (14:00 UTC) on Slack in the channel #cert-manager-dev.

To apply as a technical writer, please let us know by one of the two ways below:

  • e-mail us at with the prefix GSoD2022: in the e-mail subject.
  • or open an issue on cert-manager/website with the prefix GSoD2022: in the issue title.

You can join our open standup (every day at 10:30 UK time), and join the Kubernetes Slack channel #cert-manager-dev to know more about this project proposal.

About cert-manager

cert-manager (current version 1.8.0, first release in October 2017) is an Apache-2.0 licensed Kubernetes add-on to automate the management and issuance of TLS certificates.

Our typical contributors are Go developers from around the world with experience of the Kubernetes ecosystem with experience contributing to core Kubernetes components and Kubernetes operators.

Our users are often developers and system administrators who are trying to automate the rotation of TLS certificates for applications running in their Kubernetes clusters.

Our largest users have cert-manager installed on multiple Kubernetes clusters and managing many thousands of TLS certificates.

Project Overview

Right now the content is not designed with our target audiences in mind. For example a new user will not easily find a guide explaining how to install cert-manager on AWS and configure it for Let’s Encrypt. Nor will a Cluster Administrator easily find information about how to optimize cert-manager for a large cluster with many Certificates. The information exists but is spread across multiple pages and is often not at the obvious page.

As a visual example, a user looking for a guide on how the Certificate resource can be used may feel helpless when realizing that the "Certificate" page exists twice: once under the "Usage" section, and once under the "Concepts" section.

Screenshot of the website with Usage and Concepts visible in the menu

(NB: This screenshot is from our old site design but the text and layout are broadly the same)

We would like a technical writer:

  1. to help us identify our target audiences, and
  2. to identify the key tasks of each of these audiences, and
  3. re-structure the website with this in mind.

For example, we have discussed the following audiences and tasks: Beginner, Cluster Administrator, User, Integrator, New Contributor and each of these people will be interested in a different set of tasks. We would like them to quickly and easily find the information they need.

By making it easier for each group to find the information they need we aim to reduce the number of support queries.


The scope of this project is as follows:

  1. Identify and describe three target audiences.
  2. Identify three key top tasks for each of these audiences.
  3. Audit the existing documentation and create a friction log of the current documentation.
  4. Using the friction log as a baseline, re-organize the documentation to minimize friction for three top tasks.
  5. Incorporate feedback from documentation testers (volunteers in the project) and the wider cert-manager community.
  6. Work with the cert-manager team to publish the documentation on
  7. Create documentation for website contributors explaining how we structure our content around audiences and tasks.

Measuring success

After the technical writer has helped us identify the 3 key tasks for each audience we will measure a baseline number of clicks required to achieve the task and we will aim to minimize the number of clicks for each task.


DatesAction Items
May / JuneIdentify audiences and tasks
May / JuneAudit and friction log
JuneRestructuring tasks
June / JulyIncorporating feedback
June / JulyPublish to
JulyFinish writing guidance for website contributors
JulyProject Completion


Budget itemAmount ($)Running Total ($)Notes
Technical writer audit and restructuring of the documentation12,00012,000
Volunteer stipends1,50013,5003 volunteer stipends x 500 each

Regarding the amount of $12,000, we assume that it will be enough to fund one experienced technical writer part-time (for example, they could work half day from Tuesday to Friday, for a total of 24 days, for 3 months at a daily rate of $500).

We will give the "volunteer stipend" to contributors who can show they have one PR within the project time frame (from 1st May to 30th July) in which a re-write of one page or a set of pages. Before starting the rewriting, the volunteer will suggest which page they wish to work on either on Slack (Kubernetes Slack, channel #cert-manager-dev), or in an issue on GitHub, and make sure by asking the team whether it makes sense to rework this page. As long as at least one positive reaction, the volunteer can start working. For the stipend to be validated, the PR needs to be reviewed and merged.