🗒 Update Developer Documentation

[zicklag]

With the Bevy rewrite, most of the technical documentation has become out-of-date. We'll need some major documentation updates including:

• An update to the book
  • We may want to remove most of the guide-level explanations initially, until we get a better handle on what the modding will look like.
• An update to the developer-facing architecture docs
  • I think I want to leverage Rustdoc to as the center for most of our architecture documentation. That will make it easier to give in-depth, but contextual information on different game modules and how they fit together.
  • This will be the number-one place for you to learn about how the game is designed and what code you'll need to change to add/modify different features.
  • I'll want a large emphasis on well-documented modules and types so that it will really explain how the game is put together.
  • While this is absolutely still a work-in-progress game, we want to be able to point people to the source and it's documentation for what a "production ready" Rust game can look like in Bevy.

[erlend-sh]

Let’s rename the old book ff-legacy or whatever and leave it as it is. The new book at learn.fishfolk.org will incorporate your changes.

[zicklag]

Progress update: ~11 days ago I got a lot of docs done for jumpy_core, though there's still more in there to flesh out.

If my time and health allows I'm going to try and finish this off soon-ish, trying to cover most of the modules and types with at least basic explanations.