I think a tip could be as a new to the open source community see anything that you could contribute. Specially document pages, spell checks or if examples and readme makes sense and etc. Usually the first open source contributions always start like those smaller fixes :)
Confident technical writer with frontend developer skills, marketing skills and developer relations skills.
I am also a very fun person to hang around with.
I have always wanted to find projects that I can contribute to their documentation, but I don't know how to find them/I have never found them.
The ones I see always require coding contributions.
How can I go about this?
Oooh good question @dumebii! :) I definitely recommend doing the following:
Look through the Readme file and contributing guides of projects and check for things like typos, and missing information (e.g. Code of Conduct, no license)
Check to see if a product's tutorial is missing important steps(I suggest contributing to the project first) or has outdated information
If you want to work on projects that are docs-centric, I mentioned a few of them here in my FreeCodeCamp article.
Confident technical writer with frontend developer skills, marketing skills and developer relations skills.
I am also a very fun person to hang around with.
I think a tip could be as a new to the open source community see anything that you could contribute. Specially document pages, spell checks or if examples and readme makes sense and etc. Usually the first open source contributions always start like those smaller fixes :)
I have always wanted to find projects that I can contribute to their documentation, but I don't know how to find them/I have never found them.
The ones I see always require coding contributions.
How can I go about this?
Oooh good question @dumebii! :) I definitely recommend doing the following:
Oh! Okay. I'd do these then. Thanks so much!