Whenever I hear about a contribution to an open-source project, I always think it's a big deal. Earlier this year, I wanted to contribute to an open-source project, but I couldn't because I didn't know how to use my skills to contribute. I reached out to a senior developer for guidance, but I received a negative response. Two months ago, while scrolling through my Discord channels, I saw a message in the Technical Writing Mentorship Program channel about contributing to an open-source project. I knew this was my chance to showcase my skills, even though I didn't know how. I submitted my name and was added to a private channel for the project. A meeting date was set, and I joined the meeting. I asked questions about the project, and a task was assigned to me. Within three weeks, I submitted my contribution. Revisions and corrections were made, and to my great surprise, I was the first person whose contribution was merged. The feedback was mind-blowing for a newbie in open-source projects. Curious to know how I successfully contributed to this open-source project? This article is for you. You will learn how to contribute and make a pull request. As a bonus, you will also learn about open-source projects and platforms that pay for contributions. Steps to Take in Contributing to an Open-Source Project Understand the project: Before you start contributing, it's important to fully understand the project. Research the project. This will help you know how to contribute and see if the project matches your skills and welcomes contributions to its writing aspects.Not all open-source projects accommodate technical writing, but some welcome both developers and technical writers. Interact with Subject Matter Experts (SME): Most projects have a Discord or Telegram channel for interaction. Join these channels, and introduce yourself in the introduction section, stating your intention to contribute to the project. For example: Good day everyone, I’m Ileolami. I’m a technical writer and frontend developer. I would like to contribute to this project as a technical writer. Some of the SMEs, either ambassadors or other community members, will respond and guide you. Many of these projects already provide resources in their resources section. Find the problem: This is where the work begins. After studying the documentation, you may notice problems such as grammatical errors or poor information architecture (IA). Some projects might be missing a feature or component, like code-based examples or graphical illustrations. You can check for these by looking at the issues raised by users. Fix the issue: Once you have identified a problem, whether it's a grammatical error, poor information architecture (IA), or a missing feature like code-based examples or graphical illustrations, it's time to provide a solution. Start by thoroughly understanding the issue and how it impacts the overall documentation or user experience. If it's a grammatical error, correct it, and ensure the text flows smoothly. For issues related to information architecture, reorganize the content to make it more logical and easier to navigate. If the problem is a missing feature, create the necessary code examples or illustrations and integrate them into the documentation. Editing: After making your changes, double-check for accuracy and consistency. Ensure that your solution aligns with the project's style guide and standards. Once you are confident in your work, submit a pull request with a detailed explanation of the changes you made and why they were necessary. This will help the maintainers understand your contributions and approve them more quickly. Make a pull request: Making a Pull Request (PR) involves submitting your changes to the project's repository so that they can be reviewed and potentially merged into the main codebase. Fill out the PR form with a clear and concise title that summarizes your changes. In the description, provide a detailed explanation of what you did, why you did it, and how it improves the documentation or codebase. Mention any specific issues you addressed, and if applicable, link to the related issue tickets. Contribution Successfully: After submitting your PR, be prepared to engage with reviewers. They may ask questions, request further changes, or provide feedback. Respond promptly and courteously to their comments, making any necessary adjustments to your PR. Once all feedback has been addressed and the reviewers are satisfied, your PR will be merged into the main codebase, and your contributions will become part of the project. Practical Steps Now that you know the steps for contributing to an open-source project, let's put it into practice. This time, you will contribute to the Technical Writing Mentorship Program (TWMP) project by submitting a blog post. Prerequisite Code Editor such as Vscode Knowledge in Markdown Git and GitHub Jar of Water Fork and Clone the Repo Go to the TWMP repo. Click on Fork to fork the repo. Choose an owner, and create a fork. Select the a Clone button from the repository. Copy the clone command (either the HTTPS or SSH format) Change to the local directory where you want to clone the repository. Paste the copied command. HTTPS: https://github.com/Technical-writing-mentorship-program/Technicalwritingcourse.git SSH: git@github.com:Technical-writing-mentorship-program/Technicalwritingcourse.git GitHub CLI: gh repo clone Technical-writing-mentorship-program/Technicalwritingcourse Make Your Changes Open the cloned repository in your code editor (e.g., VSCode). Navigate to the file or section where you want to make your contribution. Create a new file under blog. Ensure your article aligns with the TWMP's style guide and standards. Create a New Branch Open your terminal, and navigate to the cloned repository directory. Create a new branch for your changes: git checkout -b your-branch-name Verify that you are on the new branch by running: git branch Make your changes or additions in this new branch. Commit and Push Your Changes After making your changes, open your terminal, and navigate to the cloned repository directory. Stage your changes by running: git add . Commit your changes with a meaningful message: git commit -m "A new article called "how to build a doc site" Push your changes to your forked repository: git push origin your-branch-name Open Source Projects that Pay For Contributing While many open-source projects rely on volunteer contributions, some offer financial incentives for contributions. Here are a few platforms and projects that pay for open-source contributions: Google Season of Docs: This program provides stipends to technical writers who work on open-source projects. Writers collaborate with open-source organizations to improve their documentation. Outreachy: Outreachy offers paid internships to work on open-source projects. It is aimed at underrepresented groups in tech, including women, trans people, and people of color. Gitcoin: Gitcoin is a platform that connects developers with open-source projects that offer bounties for completed tasks. While it primarily focuses on code contributions, some projects also seek technical writing help. Mozilla Open Source Support (MOSS): Mozilla offers grants to open-source projects that align with their mission. These grants can be used to pay contributors, including technical writers. OnlyDust: This is a platform that blockchain-based projects most especially Starknet projects and rewards every contributor. With this guide, I hope to see you throw your hat into the ring 👍🏽. Whenever I hear about a contribution to an open-source project, I always think it's a big deal. Earlier this year, I wanted to contribute to an open-source project, but I couldn't because I didn't know how to use my skills to contribute. I reached out to a senior developer for guidance, but I received a negative response. Two months ago, while scrolling through my Discord channels, I saw a message in the Technical Writing Mentorship Program channel about contributing to an open-source project. I knew this was my chance to showcase my skills, even though I didn't know how. I submitted my name and was added to a private channel for the project. A meeting date was set, and I joined the meeting. I asked questions about the project, and a task was assigned to me. Within three weeks, I submitted my contribution. Revisions and corrections were made, and to my great surprise, I was the first person whose contribution was merged. The feedback was mind-blowing for a newbie in open-source projects. Curious to know how I successfully contributed to this open-source project? This article is for you. You will learn how to contribute and make a pull request. As a bonus, you will also learn about open-source projects and platforms that pay for contributions. Steps to Take in Contributing to an Open-Source Project Understand the project: Before you start contributing, it's important to fully understand the project. Research the project. This will help you know how to contribute and see if the project matches your skills and welcomes contributions to its writing aspects.Not all open-source projects accommodate technical writing, but some welcome both developers and technical writers. Interact with Subject Matter Experts (SME): Most projects have a Discord or Telegram channel for interaction. Join these channels, and introduce yourself in the introduction section, stating your intention to contribute to the project. For example: Good day everyone, I’m Ileolami. I’m a technical writer and frontend developer. I would like to contribute to this project as a technical writer. Some of the SMEs, either ambassadors or other community members, will respond and guide you. Many of these projects already provide resources in their resources section. Find the problem: This is where the work begins. After studying the documentation, you may notice problems such as grammatical errors or poor information architecture (IA). Some projects might be missing a feature or component, like code-based examples or graphical illustrations. You can check for these by looking at the issues raised by users. Fix the issue: Once you have identified a problem, whether it's a grammatical error, poor information architecture (IA), or a missing feature like code-based examples or graphical illustrations, it's time to provide a solution. Start by thoroughly understanding the issue and how it impacts the overall documentation or user experience. If it's a grammatical error, correct it, and ensure the text flows smoothly. For issues related to information architecture, reorganize the content to make it more logical and easier to navigate. If the problem is a missing feature, create the necessary code examples or illustrations and integrate them into the documentation. Editing: After making your changes, double-check for accuracy and consistency. Ensure that your solution aligns with the project's style guide and standards. Once you are confident in your work, submit a pull request with a detailed explanation of the changes you made and why they were necessary. This will help the maintainers understand your contributions and approve them more quickly. Make a pull request: Making a Pull Request (PR) involves submitting your changes to the project's repository so that they can be reviewed and potentially merged into the main codebase. Fill out the PR form with a clear and concise title that summarizes your changes. In the description, provide a detailed explanation of what you did, why you did it, and how it improves the documentation or codebase. Mention any specific issues you addressed, and if applicable, link to the related issue tickets. Contribution Successfully: After submitting your PR, be prepared to engage with reviewers. They may ask questions, request further changes, or provide feedback. Respond promptly and courteously to their comments, making any necessary adjustments to your PR. Once all feedback has been addressed and the reviewers are satisfied, your PR will be merged into the main codebase, and your contributions will become part of the project. Understand the project: Before you start contributing, it's important to fully understand the project. Research the project. This will help you know how to contribute and see if the project matches your skills and welcomes contributions to its writing aspects. Not all open-source projects accommodate technical writing, but some welcome both developers and technical writers. Understand the project : Before you start contributing, it's important to fully understand the project. Understand the project Research the project. This will help you know how to contribute and see if the project matches your skills and welcomes contributions to its writing aspects. Not all open-source projects accommodate technical writing, but some welcome both developers and technical writers. Interact with Subject Matter Experts (SME): Most projects have a Discord or Telegram channel for interaction. Join these channels, and introduce yourself in the introduction section, stating your intention to contribute to the project. For example: Good day everyone, I’m Ileolami. I’m a technical writer and frontend developer. I would like to contribute to this project as a technical writer. Some of the SMEs, either ambassadors or other community members, will respond and guide you. Many of these projects already provide resources in their resources section. Interact with Subject Matter Experts (SME): Most projects have a Discord or Telegram channel for interaction. Interact with Subject Matter Experts (SME): Join these channels, and introduce yourself in the introduction section, stating your intention to contribute to the project. For example: Good day everyone, I’m Ileolami. I’m a technical writer and frontend developer. I would like to contribute to this project as a technical writer. Good day everyone, I’m Ileolami. I’m a technical writer and frontend developer. I would like to contribute to this project as a technical writer. Some of the SMEs, either ambassadors or other community members, will respond and guide you. Many of these projects already provide resources in their resources section. Find the problem: This is where the work begins. After studying the documentation, you may notice problems such as grammatical errors or poor information architecture (IA). Some projects might be missing a feature or component, like code-based examples or graphical illustrations. You can check for these by looking at the issues raised by users. Find the problem: This is where the work begins. After studying the documentation, you may notice problems such as grammatical errors or poor information architecture (IA). Find the problem: Some projects might be missing a feature or component, like code-based examples or graphical illustrations. You can check for these by looking at the issues raised by users. Fix the issue: Once you have identified a problem, whether it's a grammatical error, poor information architecture (IA), or a missing feature like code-based examples or graphical illustrations, it's time to provide a solution. Start by thoroughly understanding the issue and how it impacts the overall documentation or user experience. If it's a grammatical error, correct it, and ensure the text flows smoothly. For issues related to information architecture, reorganize the content to make it more logical and easier to navigate. If the problem is a missing feature, create the necessary code examples or illustrations and integrate them into the documentation. Fix the issue : Once you have identified a problem, whether it's a grammatical error, poor information architecture (IA), or a missing feature like code-based examples or graphical illustrations, it's time to provide a solution. Start by thoroughly understanding the issue and how it impacts the overall documentation or user experience. Fix the issue If it's a grammatical error, correct it, and ensure the text flows smoothly. For issues related to information architecture, reorganize the content to make it more logical and easier to navigate. If the problem is a missing feature, create the necessary code examples or illustrations and integrate them into the documentation. Editing: After making your changes, double-check for accuracy and consistency. Ensure that your solution aligns with the project's style guide and standards. Once you are confident in your work, submit a pull request with a detailed explanation of the changes you made and why they were necessary. This will help the maintainers understand your contributions and approve them more quickly. Editing : After making your changes, double-check for accuracy and consistency. Ensure that your solution aligns with the project's style guide and standards. Once you are confident in your work, submit a pull request with a detailed explanation of the changes you made and why they were necessary. This will help the maintainers understand your contributions and approve them more quickly. Editing Make a pull request: Making a Pull Request (PR) involves submitting your changes to the project's repository so that they can be reviewed and potentially merged into the main codebase. Fill out the PR form with a clear and concise title that summarizes your changes. In the description, provide a detailed explanation of what you did, why you did it, and how it improves the documentation or codebase. Mention any specific issues you addressed, and if applicable, link to the related issue tickets. Make a pull request : Making a Pull Request (PR) involves submitting your changes to the project's repository so that they can be reviewed and potentially merged into the main codebase. Make a pull request Fill out the PR form with a clear and concise title that summarizes your changes. In the description, provide a detailed explanation of what you did, why you did it, and how it improves the documentation or codebase. Mention any specific issues you addressed, and if applicable, link to the related issue tickets. Contribution Successfully: After submitting your PR, be prepared to engage with reviewers. They may ask questions, request further changes, or provide feedback. Respond promptly and courteously to their comments, making any necessary adjustments to your PR. Once all feedback has been addressed and the reviewers are satisfied, your PR will be merged into the main codebase, and your contributions will become part of the project. Contribution Successfully : After submitting your PR, be prepared to engage with reviewers. They may ask questions, request further changes, or provide feedback. Respond promptly and courteously to their comments, making any necessary adjustments to your PR. Once all feedback has been addressed and the reviewers are satisfied, your PR will be merged into the main codebase, and your contributions will become part of the project. Contribution Successfully Practical Steps Now that you know the steps for contributing to an open-source project, let's put it into practice. This time, you will contribute to the Technical Writing Mentorship Program (TWMP) project by submitting a blog post. Technical Writing Mentorship Program (TWMP) Prerequisite Code Editor such as Vscode Knowledge in Markdown Git and GitHub Jar of Water Code Editor such as Vscode Vscode Knowledge in Markdown Markdown Git and GitHub Git GitHub Jar of Water Fork and Clone the Repo Go to the TWMP repo. Click on Fork to fork the repo. Choose an owner, and create a fork. Select the a Clone button from the repository. Copy the clone command (either the HTTPS or SSH format) Change to the local directory where you want to clone the repository. Paste the copied command. HTTPS: https://github.com/Technical-writing-mentorship-program/Technicalwritingcourse.git SSH: git@github.com:Technical-writing-mentorship-program/Technicalwritingcourse.git GitHub CLI: gh repo clone Technical-writing-mentorship-program/Technicalwritingcourse Go to the TWMP repo. Go to the TWMP repo. TWMP Click on Fork to fork the repo. Click on Fork to fork the repo. Fork Choose an owner, and create a fork. Choose an owner, and create a fork. Select the a Clone button from the repository. Select the a Clone button from the repository. Clone Copy the clone command (either the HTTPS or SSH format) Copy the clone command (either the HTTPS or SSH format) Change to the local directory where you want to clone the repository. Change to the local directory where you want to clone the repository. Paste the copied command. HTTPS: https://github.com/Technical-writing-mentorship-program/Technicalwritingcourse.git SSH: git@github.com:Technical-writing-mentorship-program/Technicalwritingcourse.git GitHub CLI: gh repo clone Technical-writing-mentorship-program/Technicalwritingcourse Paste the copied command. HTTPS: HTTPS: https://github.com/Technical-writing-mentorship-program/Technicalwritingcourse.git https://github.com/Technical-writing-mentorship-program/Technicalwritingcourse.git SSH: SSH: git@github.com:Technical-writing-mentorship-program/Technicalwritingcourse.git git@github.com:Technical-writing-mentorship-program/Technicalwritingcourse.git GitHub CLI: GitHub CLI: gh repo clone Technical-writing-mentorship-program/Technicalwritingcourse gh repo clone Technical-writing-mentorship-program/Technicalwritingcourse Make Your Changes Make Your Changes Open the cloned repository in your code editor (e.g., VSCode). Navigate to the file or section where you want to make your contribution. Create a new file under blog. Ensure your article aligns with the TWMP's style guide and standards. Open the cloned repository in your code editor (e.g., VSCode). Open the cloned repository in your code editor (e.g., VSCode). Navigate to the file or section where you want to make your contribution. Navigate to the file or section where you want to make your contribution. Create a new file under blog. Ensure your article aligns with the TWMP's style guide and standards. Create a new file under blog . Ensure your article aligns with the TWMP's style guide and standards . blog TWMP's style guide and standards Create a New Branch Create a New Branch Open your terminal, and navigate to the cloned repository directory. Create a new branch for your changes: git checkout -b your-branch-name Verify that you are on the new branch by running: git branch Make your changes or additions in this new branch. Open your terminal, and navigate to the cloned repository directory. Open your terminal, and navigate to the cloned repository directory. Create a new branch for your changes: git checkout -b your-branch-name Create a new branch for your changes: git checkout -b your-branch-name git checkout -b your-branch-name Verify that you are on the new branch by running: git branch Verify that you are on the new branch by running: git branch git branch Make your changes or additions in this new branch. Make your changes or additions in this new branch. Commit and Push Your Changes Commit and Push Your Changes After making your changes, open your terminal, and navigate to the cloned repository directory. Stage your changes by running: git add . Commit your changes with a meaningful message: git commit -m "A new article called "how to build a doc site" Push your changes to your forked repository: git push origin your-branch-name After making your changes, open your terminal, and navigate to the cloned repository directory. After making your changes, open your terminal, and navigate to the cloned repository directory. Stage your changes by running: git add . Stage your changes by running: git add . git add . Commit your changes with a meaningful message: git commit -m "A new article called "how to build a doc site" Commit your changes with a meaningful message: git commit -m "A new article called "how to build a doc site" git commit -m "A new article called "how to build a doc site" Push your changes to your forked repository: git push origin your-branch-name Push your changes to your forked repository: git push origin your-branch-name git push origin your-branch-name Open Source Projects that Pay For Contributing While many open-source projects rely on volunteer contributions, some offer financial incentives for contributions. Here are a few platforms and projects that pay for open-source contributions: Google Season of Docs: This program provides stipends to technical writers who work on open-source projects. Writers collaborate with open-source organizations to improve their documentation. Outreachy: Outreachy offers paid internships to work on open-source projects. It is aimed at underrepresented groups in tech, including women, trans people, and people of color. Gitcoin: Gitcoin is a platform that connects developers with open-source projects that offer bounties for completed tasks. While it primarily focuses on code contributions, some projects also seek technical writing help. Mozilla Open Source Support (MOSS): Mozilla offers grants to open-source projects that align with their mission. These grants can be used to pay contributors, including technical writers. OnlyDust: This is a platform that blockchain-based projects most especially Starknet projects and rewards every contributor. Google Season of Docs: This program provides stipends to technical writers who work on open-source projects. Writers collaborate with open-source organizations to improve their documentation. Google Season of Docs : This program provides stipends to technical writers who work on open-source projects. Writers collaborate with open-source organizations to improve their documentation. Google Season of Docs Google Season of Docs Outreachy: Outreachy offers paid internships to work on open-source projects. It is aimed at underrepresented groups in tech, including women, trans people, and people of color. Outreachy : Outreachy offers paid internships to work on open-source projects. It is aimed at underrepresented groups in tech, including women, trans people, and people of color. Outreachy Outreachy Gitcoin: Gitcoin is a platform that connects developers with open-source projects that offer bounties for completed tasks. While it primarily focuses on code contributions, some projects also seek technical writing help. Gitcoin : Gitcoin is a platform that connects developers with open-source projects that offer bounties for completed tasks. While it primarily focuses on code contributions, some projects also seek technical writing help. Gitcoin Gitcoin : Mozilla Open Source Support (MOSS): Mozilla offers grants to open-source projects that align with their mission. These grants can be used to pay contributors, including technical writers. Mozilla Open Source Support (MOSS) : Mozilla offers grants to open-source projects that align with their mission. These grants can be used to pay contributors, including technical writers. Mozilla Open Source Support (MOSS) Mozilla Open Source Support (MOSS) OnlyDust: This is a platform that blockchain-based projects most especially Starknet projects and rewards every contributor. OnlyDust : This is a platform that blockchain-based projects most especially Starknet projects and rewards every contributor. OnlyDust OnlyDust With this guide, I hope to see you throw your hat into the ring 👍🏽.
