The documentation of an open source project provides an avenue for users to understand the project and contribute to it. Surveys have even shown that good documentation saves as a sign of an open source project's healthiness.
Yet, few open-source projects can claim they are well documented, and many others struggle to keep their documentation up to date.
As important as open source projects' documentation may seem, most technical writers shy away from contributing to open source projects because they don't know how to or they are influenced by the stereotype that only software engineers can contribute to open source.
This article aims to provide an introductory guide for technical writers who want to contribute to open source projects. It will cover how to get started, best practices, benefits, and insightful resources for further learning.