You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
eligible assets have an individual page that they can link to
to be eligible, assets must have a crates.io link
as a starting point, this is mostly the same page as the crates.io or lib.rs page for that crate
show the list of Bevy features it enables
add specific metadata to the Cargo.toml file, like a list of screenshots to display in a carousel
could show other things specific to Bevy, like list of components with direct links to docs.rs
build a filtered automatic showcase of assets
must be published on crates.io
must depend on the last version of Bevy
must have a compatible license
must have screenshots
must respect the CoC
(maybe) must have more than one maintainer
(maybe) limited to the top X crates of a category based on recent download
crates can be excluded at the maintainers discretion
The text was updated successfully, but these errors were encountered:
mockersf
added
C-Feature
A new feature, making something new possible
A-Assets
The collection of ecosystem crates found on the Bevy Assets page
labels
Jun 2, 2024
I'd change this to say "must depend on the latest or the previous version of Bevy" to account for the plugin migration period after a release. I know we have the RC workflow now, but plugin authors should not feel pressured to participate in order to not loose their showcase status.
I would like to propose as the next step for Bevy Assets https://bevyengine.org/assets/:
The text was updated successfully, but these errors were encountered: