2 ms·
> The unglamorous answer is that this might be just a documentation problem. MDN is pretty good, even though Mozilla increasingly concerns me as a steward of th
by amadeuspagel 10mo ago
> The unglamorous answer is that this might be just a documentation problem. MDN is pretty good, even though Mozilla increasingly concerns me as a steward of the open web. What if it were just a little better?
What if it had a comment section where people could discuss these issues, like the PHP docs? What if it had a wiki, where people could collaborate on fixing them, like ArchWiki?
- graypegg 10mo agoThe example that comes to my mind is apidock for Ruby! https://apidock.com/ruby/String/split https://apidock.com/ruby/String/split Though, considering how much information tends to get centralized in these comments, I think the wiki-like direction is the way to go. (I know anyone can edit MDN, but it's via github PRs rather than being able to make quick edits on the site.)
- DebugDruid 10mo agoI don’t see a problem with the github PR workflow for updating documentation. Yes, it’s one step more, but it’s nothing special when you use github’s online editor. PS: MDN and MSDN are my favorite documentation sites.
- extra88 10mo agoMDN is on GitHub, every page ends with "View this page on GitHub • Report a problem with this content" links. I've pointed out errors a couple of times and they were corrected pretty quickly.
- qingcharles 10mo agoI've found them responsive to errors too. When I pointed out some bugs on Microsoft's docs they just basically replied "hurry up and fix them then!" which annoyed me at first, but they actually poked me until I stopped being lazy and submitted a PR, wherein I actually learned some new things.