Add Workspace Based Development to the Upcoming Bevy Book.

[mholiv]

How can Bevy's documentation be improved?

This issue is my submitting the idea of adding a workspace based workflow guide to the upcoming bevy book. Based on personal experience and those who have reached out to me I think this would be valuable.

If there is interest I would volunteer to write the section.

The section would roughly contain/recomend:

• Games start out as a single crate with a strong focus on bevy plugin hygiene.
• When compile times get annoying, then you break the game out into workspace crates along the lines of bevy plugins.
• General advice on how to handle Components or resources that may be used across plugins in a workspace based workflow.
• How to architect the workspace crates so maximal parallel compilation is achieved.

[swoobie]

I've toyed with this a little myself and like the idea of workspace based development, but haven't really found anything that's made it worth the effort just yet. Likely because I haven't made enough projects to know what's worth reusing yet.

Anyways, some random thoughts on it:

• Hotpatching (the Dioxus based one, not hot reloading assets) only works on the main binary crate. Part of managing compile times with splitting crates will have implications on what's able to be hotpatched.
• Workspaces support an [[example]] tag that makes it trivial to add new, one off prototype concepts (plus its actual usage of, yknow, showcasing examples lol). I tried to make this work for a bit because of how trivial it is to add a new, separate prototype idea without worrying about it breaking any of the existing code. Working with pure code-base bevy prototypes worked well for this, but there's some quirks with getting it to find assets in the right location that I never got around to understanding, but it made loading assets a bit tedious. Additionally, the examples workflow also has similar hotpatching limitations as separating library/binary crates.

With that said, most of the time I find myself overengineering things by having it setup as a workspace. Almost like I'm trying to rebuild a familiar workflow instead of just writing the logic needed for whatever particular case I'm working on at the time.

I'd help review and test the guidance for this, see what other edge cases there might be.