[Edited completely] Sorry I don't get it. People blog about stuff they use, they always have, always will. The fact that blogs are inconsistent is just the sym

[Edited completely] Sorry I don't get it. People blog about stuff they use, they always have, always will. The fact that blogs are inconsistent is just the symptom, warning sign even, one that reflects more on the state of AngularJS documentation and APIs than those who blog about it. The problem to me seems to be both with the official documentation (or lack thereof) as well as inconsistencies in the design of Angular's APIs themselves which I find tend to lead people towards many different interpretations and implementations in practice. The truth is part of this is simply the maturity of the project which is perhaps unavoidable but some part of it is that the Angular core team just does not seem to be taking documentation or at least clearly defining best practices as a very high priority. However I would argue it should be. At least equal to core development itself. If you don't first clearly define how you expect people to use your APIs then how can you really expect to design them in a way that is easy to understand and use? The state of the Angular docs are unacceptable at the present time, and I just don't think crowdsourced solutions like those presented here are a sufficient solution. I can't think of (help me out here) any other examples where a high-quality open source project gets it's documentation completely from crowd sourced, after-the-fact, community edits. Good documentation has to be set as a standard. Sure lean on the community but please don't just expect to "build it and the community will write the docs" is going to work out.