Thanks :) For the first point, yeah I agree, though I would still keep standard API documentation separated. And it gets "worse" when you add the 4th site: htt

Thanks :) For the first point, yeah I agree, though I would still keep standard API documentation separated. And it gets "worse" when you add the 4th site: https://code.haxe.org https://code.haxe.org which helps with 4th point (partly?). Tricky thing with guides like "how to make a game" is that it's not a haxe-specific thing; it's a haxe framework specific thing which they handle on their own: https://haxeflixel.com/documentation/ https://haxeflixel.com/documentation/, https://heaps.io/documentation/home.html https://heaps.io/documentation/home.html, https://github.com/Kode/Kha/wiki https://github.com/Kode/Kha/wiki (is there a better link for kha?), etc. There are links in https://haxe.org/use-cases/games/ https://haxe.org/use-cases/games/ but discoverability could likely be much better and include a generic "how to make a game" start point which points to either framework depending on your needs (2D/3D, mobile/desktop/console/web, etc.). Indeed Haxelib isn't visible :x Now that you mention it, we had a few haxe newcomers that didn't know about it. We need to do something about that (even if it might get a replacement in the near-ish future https://github.com/HaxeFoundation/haxe/issues/9135 https://github.com/HaxeFoundation/haxe/issues/9135) Good point about std lib docs too! Some, maybe including MainLoop, are harder for community to document but we should ask help from core compiler devs.