bevy-website VS bevy-cheatbook

https://github.com/bevyengine/bevy-website/issues/1097 Yep, on our wishlist and will be added :)

We'd like to open the floodgates on Bevy Book development asap. This taking so long has largely been my fault ... I've been overly protective of the Bevy Book while also not giving it the attention it deserves. Here is our current plan: https://github.com/bevyengine/bevy-website/issues/623#issuec..., which I'd like to execute during the next cycle.

Latest Progress: https://github.com/bevyengine/bevy-website/pull/550/files

I do want previews though.

API docs, examples and the revised book: https://github.com/bevyengine/bevy-website/pulls?q=is%3Aopen...

Strongly agreed on the need for better introductory material; the existing book is extremely incomplete.

> I don't have this clear. Are 5/6 teams actually building commercial games with Bevy, or they just planning to do it in the future? This is a crucial distinction.

I know of 2 released commercial projects, the CAD team, a few indie devs who have started and 3 or so small studios who are looking to start. There's a little thread in the Discord where I've rounded folks up: [Bevy in production](https://discord.com/channels/691052431525675048/995713618526...).

We also do some real cleverness around split borrows in order to enable automatic system parallelism. This draft book page goes into more concrete details :)

Can do

I used the unofficial bevy cheatbook a lot to learn the ropes. Everyone on the discord is super friendly and helpful and the official documentation is being updated, you can check out the PRs on the book branch

If you're curious about the ECS side of things, that chapter is now ~approximately complete, and should make an excellent learning resource: https://github.com/bevyengine/bevy-website/pull/182

I've been using Bevy recently so here are some thoughts on this:

Firstly, the overall quality is high and seeing this attention being paid to the project's organization is another good sign.

Documentation is not great great. The Bevy book runs out of content very quickly. The "Cheat Book" has additional useful information: https://bevy-cheatbook.github.io/. With these plus the examples I've been able to figure out everything I need, but it's slow going.

I'm not 100% sold on ECS. It loses a lot of type safety and there doesn't seem to be any way to ensure cleanup of entities and their components.

This is quite helpful to cover the features of bevy with some code examples and explanations with links to git repositories as reference. Most of it appears to be from 0.9, but you can reference to the migration guide to see how to change from it. Ctrl-f is your friend to see which version changes what.

You can see working examples of nearly everything you asked about in the Bevy Cheatbook

The biggest source of wasted time for me was finding out that my shaders which were working on native didn’t work on webgl. For one of the more perplexing error messages, I opened this issue in the cheatbook a while ago.

wasm mostly works :) There's a nice PR open on the cheatbook that documents the process quite well that you can work off of.

Great! Are you okay if I submit this to the Unofficial Bevy Cheatbook? This question comes up pretty frequently and this is a great little snippet.