Detailed description
Due having a ton of entries, it seems like a lot of the entries have no explanation accompanying them, leaving them vague and confusing to say the least! So now obviously, it's not easy to write documentation for the same, with people being more interested in writing code (which is understandable). But I was suggesting if we could maybe promote this repository (not in a bad sense) to the people who are contributing to other repositories of this organisation to maybe also spend some time helping out on this portion of the organisation to revive the explanations to make the site actually helpful, instead of being a place to just get code of algorithms from, kinda.
Context
Context provided in description
Possible implementation
The way we could promote or so on the top of my mind are:
- Drawing attention to this repository on the website, by adding some non-intrusive pop-ups and urging interested users to contribute
- Promoting contribution to this repository during Hacktoberfest, since it is not that difficult to really add one page of documentation for the swathes of PRs this organisation gets anyways
Additional information
Please note that these aren't all possible ways to promote the repo, so you (the person reading this) should also probably try to come up with some other ways.
Some possible issues with the promotion of repository:
- Our entries aren't that... organised to say the least. They are indeed a mess, I'll admit, and it can cause a few issues and confusion
- If we promote the repo during Hacktoberfest, then we'll definitely get tons of useless PRs with a bunch of single lines filled in, or improper formatting, which may bog down the few maintainers we have for this repository, who may also be dealing with swathes of spam PRs in other repositories for Hacktoberfest, which will be insane for the maintainers.
These are atleast some of the things we'll need to consider while trying to promote this repo, along with some other things which didn't cross my mind while typing this issue out. I'd like to have a proper discussion for this here. But regardless, we definitely are in dire need of more documentation for the site.