tracking issue: migration to Bevy Assets

[mockersf]

Bevy Website repo

• Generate Zola pages from Bevy Assets repo
  • First pass with minimal fields - add Bevy awesome to website #156
  • Crate can generate the website - add Bevy awesome to website #156
  • Setup CI - add Bevy awesome to website #156
  • Crate can validate the input - Asset validation #163
• Remove other references to Awesome Bevy - clone new repo bevy-assets & remove reference to awesome bevy #165
• Metadata of assets
  • Image support - Asset validation #163
  • Agree on complete format and additional fields we want
  • Enrich with crates.io data (license, Bevy version, ...) - https://github.com/alyti/populate-crate-metadata
  • Enrich with github data (stars? not sure it's possible without hitting GitHub api limits)
  • Enrich with other potential sources (gitlab? our own database for ❤️?)
• Website views
  • Basic list view - add Bevy awesome to website #156
  • Add a text explanation on what it is and how to add your own stuff, and link to Bevy Assets repo
  • Add a page view per asset - Figma design ideas
  • Asset search
  • Prettier small cards in list view
  • Assets can have one primary tag and several secondary tags, can filter on tag

Bevy Assets repo

• Updated the readme to help with automatic migration:
  • Changed headers - Migration to bevy-assets bevy-assets#102
  • Remove markdown links - Migration to bevy-assets bevy-assets#102
  • Script for automatic migration - add Bevy awesome to website #156
  • Automatic migration - Migration to bevy-assets bevy-assets#102
• Repo setup for new Bevy Assets:
  • Setup order for some items - Migration to bevy-assets bevy-assets#102
  • Setup CI to validate new files added in a PR - Validation, CI and new README for assets bevy-assets#105
  • Setup CI to trigger bevy-website publish - Validation, CI and new README for assets bevy-assets#105
  • Update the readme (specify new way, describe format, link to Bevy Assets) - Validation, CI and new README for assets bevy-assets#105
  • Update migrations with Assets added since branch creation - Update branch bevy-asset with latest additions bevy-assets#108
  • Switch branch
  • Rename the repo - clone new repo bevy-assets & remove reference to awesome bevy #165
• Enrich initial repo
  • Fix assets for new constraints (description without markdown and 100 chars limit) - Validation, CI and new README for assets bevy-assets#105
  • Ask for contributors to add pictures, new metadata, ...

[mockersf]

close enough to be done for that step - I will try to open a new tracking issue soon for the next step