François Mockers

> Is there a good way to specify custom per-example metadata in Cargo.toml? It's possible to add any field we want in the `Cargo.toml` file: ```toml [[example]] name = "3d_scene"...

I posted https://internals.rust-lang.org/t/cargo-manifest-and-unused-manifest-key-allow-other-tools-to-extend-the-manifest/16333 as that would be the best solution if only there was a way to remove that warning

I would love for this to work: ```toml [[example]] name = "3d_scene" path = "examples/3d/3d_scene.rs" [example.metadata] display_name = "3D Scene" description = "Simple 3D scene with basic shapes and lighting"...

to use https://github.com/bevyengine/bevy/pull/4726 on the website we will need to update some things on this side

I'm not sure hosting the website in dev is a good idea, or that it brings enough value to offset the complications from keeping it up and redirecting people to...

Limiting this in scope to links to `https://docs.rs` should be possible and more stable

> IMO this means that we need a "docs for main" site up ASAP https://github.com/bevyengine/bevy/pull/3535 > along with some way to substitute the URLs. Have you met our lord and...

No opposition from me to relicensing! But I still like Apache2/MIT...

I guess you're right. But if someone cares for license, we can't leave the template itself without one. Maybe a written permission in the template to relicense as the user...

the number is for tracking, and it's the PR number