[andrewmcwatters]

I will prioritize this immediately. I believe one should be able to understand all of the concepts the engine offers within short order, and clearly I need documentation to back that belief.

Everything is there to get started in just minutes, reducing any installation friction typically found with larger game engines, but I agree that documentation should be able to reduce the cognitive friction such that one can get started faster.

Thank you for pointing this out. If you're so inclined, sample game code comes with the engine for the time being to understand how it works. I realize this isn't completely ideal, but feedback like this is critical to the direction I take.

[mmlkrx]

If you're looking for inspiration on how to organize your docs, I found this resource really valuable: https://documentation.divio.com

You can see the documentation system in action in this project: https://www.brachiograph.art

Regarding Grid, personally I always like to look at example applications built with framework/library/engine so seeing a list of projects that utilize Grid would be nice.

[andrewmcwatters]

Thank you, mmlkrx. I'm focusing on this today and I appreciate your help! I will keep this feedback in mind and emphasize the points you have made.

[nightowl_games]

Thanks for taking my feedback.

I suggest for the Tutorial sectiona that you walk the reader through making the type of game that you think this engine excels at making.

Would also like to know more about the networking capabilities.