Define and implement a publishing process for assets. #23177
Description
Goal Description
Bevy today doesn't have an actual guide for what to do with assets when publishing. 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. In addition, users generally do not want to ship a loose pile of assets, and instead would prefer "packs" of assets. Therefore we could/should:
- Make asset processing more useful (e.g., implement one-to-many asset processing).
- Implement production-ready asset sources (a "packed" asset source, an asset source that includes a manifest file for web, etc).
- Provide a guide for what steps are needed to ship (maybe even provide a CLI tool?).
Goal Status
This is a potential Bevy Project Goal. Its state on the Project Goals Board 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