**Update:** Kevin provided [an answer][1], which, while adding something of value to the three related questions together (by naming the originating concern eventually), actually does not apply to the question at hand. So to further stress the issue I'd like to provide an alternate phrasing with his response in mind: Is it really worth to **police something prematurely**, which [hasn't been identified to be a problem yet][2], **for the sake of the policy itself**, thereby sacrificing the upmost motivation to improve API/library documentation (as well as the liberal [ongoing community self-regulation][3] regarding the exploration of proper API/library documentation)? ---------- Assuming for a moment that their really might be an argument important enough to [warrant moderator intervention][4] to consider [`dev-tip`][5] posts [to be reputation farming][6] at some point in the future and require them to be community wiki therefore immediately, would it really be worth to discourage **substantive illustrative guidance** of API/library usage nowadays already for the sake of a couple of reputation points in a distant future? ---------- **George Edison:** I have set up a small MediaWiki installation here: http://stackoverflow.quickmediasolutions.com/wiki/ Feel free to add / edit pages to document API usage. All the content on the site is CC licensed so you can copy (with attribution of course) the stuff in the existing `dev-tip` questions. [1]: #1432 [2]: https://stackapps.com/questions/1427/why-could-it-possibly-be-considered-reputation-farming-asking-for-solutions-to [3]: https://stackapps.com/questions/1426/why-have-recent-dev-tip-posts-been-forced-into-community-wiki-without-explanation [4]: https://stackapps.com/questions/1426/why-have-recent-dev-tip-posts-been-forced-into-community-wiki-without-explanation [5]: https://stackapps.com/questions/tagged/dev-tip [6]: https://stackapps.com/questions/1427/why-could-it-possibly-be-considered-reputation-farming-asking-for-solutions-to