diff --git a/content/en/docs/contribute/advanced.md b/content/en/docs/contribute/advanced.md
index 12392be5bcac9..f77dea8dee347 100644
--- a/content/en/docs/contribute/advanced.md
+++ b/content/en/docs/contribute/advanced.md
@@ -151,5 +151,80 @@ When they submit their membership application, reply to the application with a
 "+1" and include details about why you think the applicant is a good fit for
 membership in the Kubernetes organization.
 
-{{% /capture %}}
+## Serve as a SIG Co-chair
+
+SIG Docs [approvers](/docs/contribute/participating/#approvers) can serve a term as a co-chair of SIG Docs.
+
+### Prerequisites
+
+Approvers must meet the following requirements to be a co-chair:
+
+- Have been a SIG Docs approver for at least 6 months
+- Have [led a Kubernetes docs release][coordinate-docs-for-a-kubernetes-release] or shadowed two releases
+- Understand SIG Docs workflows and tooling: git, Hugo, localization, blog subproject
+- Understand how other Kubernetes SIGs and repositories affect the SIG Docs workflow, including: [teams in k/org](https://github.com/kubernetes/org/blob/master/config/kubernetes/sig-docs/teams.yaml), [process in k/community](https://github.com/kubernetes/community/tree/master/sig-docs), plugins in [k/test-infra](https://github.com/kubernetes/test-infra/), and the role of [SIG Architecture](https://github.com/kubernetes/community/tree/master/sig-architecture). 
+- Commit at least 5 hours per week (and often more) to the role for a minimum of 6 months
+
+### Responsibilities
+
+The role of co-chair is primarily one of service: co-chairs handle process and policy, schedule and run meetings, schedule PR wranglers, and generally do the things that no one else wants to do in order to build contributor capacity. 
+
+Responsibilities include:
+
+- Keep SIG Docs focused on maximizing developer happiness through excellent documentation
+- Exemplify the [community code of conduct](https://github.com/cncf/foundation/blob/master/code-of-conduct.md) and hold SIG members accountable to it
+- Learn and set best practices for the SIG by updating contribution guidelines
+- Schedule and run SIG meetings: weekly status updates, quarterly retro/planning sessions, and others as needed
+- Schedule and run doc sprints at KubeCon events and other conferences
+- - Recruit for and advocate on behalf of SIG Docs with the CNCF and its platinum partners, including Google, Oracle, Azure, IBM, and Huawei
+- Keep the SIG running smoothly
+
+### Running effective meetings
+
+To schedule and run effective meetings, these guidelines show what to do, how to do it, and why.
+
+**Uphold the [community code of conduct](https://github.com/cncf/foundation/blob/master/code-of-conduct.md)**:
+
+- Hold respectful, inclusive discussions with respectful, inclusive language.
+
+**Set a clear agenda**:
+
+- Set a clear agenda of topics
+- Publish the agenda in advance 
+
+For weekly meetings, copypaste the previous week's notes into the "Past meetings" section of the notes
 
+**Collaborate on accurate notes**:
+
+- Record the meeting's discussion
+- Consider delegating the role of note-taker
+
+**Assign action items clearly and accurately**:
+
+- Record the action item, who is assigned to it, and the expected completion date
+
+**Moderate as needed**:
+
+- If discussion strays from the agenda, refocus participants on the current topic
+- Make room for different discussion styles while keeping the discussion focused and honoring folks' time
+
+**Honor folks' time**:
+
+- Begin and end meetings punctually 
+
+**Use Zoom effectively**:
+
+- Familiarize yourself with [Zoom guidelines for Kubernetes](https://github.com/kubernetes/community/blob/master/communication/zoom-guidelines.md)
+- Claim the host role when you log in by entering the host key
+
+<img src="/images/docs/contribute/claim-host.png" width="75%" alt="Claiming the host role in Zoom" />
+
+### Recording meetings on Zoom
+
+When you’re ready to start the recording, click Record to Cloud.
+    
+When you’re ready to stop recording, click Stop.
+
+The video uploads automatically to YouTube.
+
+{{% /capture %}}
diff --git a/static/images/docs/contribute/claim-host.png b/static/images/docs/contribute/claim-host.png
new file mode 100644
index 0000000000000..1e1180a1f4a9e
Binary files /dev/null and b/static/images/docs/contribute/claim-host.png differ