@dom96 if you want people to voluntarily, out of their concern for the project, and goodness of their own `heart`, contribute to Nim, first you need to `check your attitude`, and learn how not to chase people away.
[https://medium.freecodecamp.org/how-to-attract-new-contributors-to-your-open-source-project-46f8b791d787](https://medium.freecodecamp.org/how-to-attract-new-contributors-to-your-open-source-project-46f8b791d787) [https://www.itworld.com/article/2768358/open-source-tools/how-to-attract-more-people-to-your-open-source-project.html](https://www.itworld.com/article/2768358/open-source-tools/how-to-attract-more-people-to-your-open-source-project.html) Writing better documentation has very little to do with how much money or people a project has. Like I (and all these links I've been providing) said `it's an ATTITUDE`. You took whatever time you took, with whatever resources you had, to create the documentation that exists now. Well, take at least the same time and resources to make them better, and stop making excuses. The most relevant thing you said was you think writing documentation is `boring`, and it shows! Instead of telling me what I should/could do you should do it yourself. `It ain't my project and I have no responsibility to make it better`. The fact that I (and others) take time to inform you all about errors and deficiencies in your project (and you've made it clear this isn't an `our` project) should be seen as a `gift`. You know, you can do what @bluenote has done and try to write some better, correct, and useful documentation. It's amazing how much you can accomplish if you just improved one function/page/module of documentation each day/week/month. And if you really, really, really want people to contribute to documentation don't require people to jump through the hoop of writing/submitting `pull requests`. I personally hate making pr's just for documentation, it so primitive. Instead, create a `wiki` (there's this little project called `wikipedia` you know), so people who are writers, or willing to write, can actually do documentation in a way that's more conducive to writing documentation versus code versioning. I know, I know, this would take too much `time and effort` to implement, and it's much easier taking `time and effort` to peruse the forums and tell people you won't take `time and effort` to create better documentation because its `too boring`.
