Document the current asset lifecycle and design the ideal asset lifecycle.

## Goal Description

Today, we don't have a clear guide on how assets go from their editor (e.g., Blender) all the way to published (e.g., running on itch.io). We have an asset processing system that ostensibly can be used to do actions like compressing images, but this system hasn't been fleshed out with real production implementations.

We need to explain how users are expected to "import" their assets, use them in their games/apps, and finally package them for their final "published" app. As part of this, we should document the gaps in our system: is creating the final package difficult to do? Is our asset processing system enough? Are we explaining the asset processing system thoroughly enough for users? Do our processors even work?

## Goal Status

This is a potential [Bevy Project Goal](https://bevy.org/learn/contribute/project-information/project-goals/). Its state on the [Project Goals Board](https://github.com/orgs/bevyengine/projects/23/views/1) determines if it is Proposed, Postponed, Blocked (Approved), Inactive (Approved), Active (Approved), Completed, or Declined.

- **Staffing SMEs**: Not yet staffed
- **Working Group Link**: Working Group not yet formed
- **Design Documents**: Design documents not yet written