I completely agree with you that we could have some better documentation so that we can onboard developers coming with different needs! You might have seeded a good idea here 
.
Haxe is like a swiss knife and the world is full of problems that a swiss knife can handle, but a mapping of /what tool/ and /how to use it/ versus /what real world problem/ could be very handy!
Perhaps this could be something that is part of the Haxe Code Cookbook ( https://code.haxe.org/ ) , an area of the Haxe ecosystem where I feel I can contribute.
For example, I’m trying to get Haxe off the ground with some unit testing tools. Couldn’t get munit off the ground yet, but I managed to do it with buddy. I’m thinking to contribute an article regarding this path. I’m also experimenting with two targets at once (Flash, because it was easy to get my prototype going there and JS, my long-term goal).
Later edit: and regarding what I said about VS Code, it just happens that in the space of a couple of hours @ablum came out to announce this: