I think a good parallel is OWASP for web app security. The content is free and open for the internet. OWASP doesn't directly focus on curating the content and it is left up to the community. The content grows old and stale, errors do not get corrected, and the writing is often what I would call draft quality even when its published.<p>There are always a lot more consumers than creators of content on any platform. Most people going to use a resource are not the same who can write about it, not everyone on YouTube has something to share or make a video. And why give it away for free when you can make a paid course, give a talk, charge consulting fees, sell a solution to a problem?<p>You need to align incentives. Again, why contribute to something and possibly deal with the pain of moderation for free (costs instead of gain). Should we blindly trust the wisdom of the crowds? The other cost of free, is that the community may not be capable or not interested in sufficient moderation - this leads to low quality content which chases people away, even if there is good content right next to it.<p>OWASP's incentives and objectives have never been 100% clear to me. There are some big security players involved, but it seems more interested in research, community, grants, etc versus content. When you look at MDN, Mozilla has a clear incentive to document these things so developers build more "standard" vs "Chrome-focused" web apps, which helps keep users on FireFox since all of their favorite sites are less likely to break without FireFox simply copying decision made by Chrome. By documenting expected action and quirks, it forces Google et al. to try to move back towards agreed upon standards.<p>In security, I am generally more reliant upon vendor write ups and content from people with a reputation. Security has a much smaller population than web dev. Also, for web dev a lot of people pick it up and feel comfortable writing publicly even when they are just starting out (See Dev.To). I am not sure if companies pump millions of dollars into commercial web tools beyond graphics and CMS type stuff, so I wonder if a more decentralized collection of guidance is practical for the web, not to mention that there is a lot of nuance between browsers and even recent versions.