You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It'd be nice if documentation that was incorrect or just extremely thin, as can be the case in some parts, could be reported/flagged/highlighted.
APIDock has (had?) comments that helped somewhat with this, as additional explanations could be provided, but some kind of basic flagging tool could at least help collect data that could inform what parts of the documentation need more attention.
The text was updated successfully, but these errors were encountered:
I would like to see something added that addresses this, thanks for opening an issue about this.
In the past I've thought about having a button/form that people can submit that indicates that some piece of documentation is laking somehow, and have some tooling that ultimately is actionable for someone to help contribute documentation back to ruby-src. I think it would be a huge win if we can make it easy, and celebrate/promote people.
If there was just a tumbleweed button you could click if the documentation left you feeling hopeless and alone, even if it didn't do anything, that'd be a win in my book.
It'd be nice if documentation that was incorrect or just extremely thin, as can be the case in some parts, could be reported/flagged/highlighted.
APIDock has (had?) comments that helped somewhat with this, as additional explanations could be provided, but some kind of basic flagging tool could at least help collect data that could inform what parts of the documentation need more attention.
The text was updated successfully, but these errors were encountered: