If you look around at the github pages of a lot of the successful open-source projects, you'll noticed that there's emerged this pattern of well-written readmes

If you look around at the github pages of a lot of the successful open-source projects, you'll noticed that there's emerged this pattern of well-written readmes that give you a great overview of the intent of the project and then how to get started using it. Especially for newer projects, the lack of such a page can be a death sentence. And then such developers start to write deep technical blogs that everyone starts sharing and following. And then they start going to conferences and giving in-depth talks. All it is to say, lots of people work on open source, but if you want to become known for your work, you must become good at technical writing.