ickk

With the help & input from @alterae, @BlackPhlox, @cart, @DJMcNab, @mockersf, @neo97x, @TheRawMeatball, @Weasy666, we iterated on this design for asset cards:  I think the big useful feature that...

I thought about the license thing a bit; I think from both a UX perspective and from a 'what opinion does bevy want to have', and I think just having...

~~Additionally, I'm slightly biased against warning for 'bad' licenses. Licenses can be extremely controversial, and I think positive reinforcement for our preference is good, but negative reinforcement can potentially leave...

In that case we should just have 2 categories: "mit, zlib, Apache, unlicense, et c." and everything else should be warned against since either it's not free enough or we...

This is a good idea. I think it makes more sense to serve it under something like `docs.bevyengine.org` rather than `api`. In fact, it might make more sense to host...

Sorry to revive a seemingly dead rfc, but I hit this and it bothers me. Frankly bit-wise operations should only ever operate *bit wise* on each *bit corresponding to its...

Regarding implicit installs, as a user it seems obvious to me that commands that I expect be purely informational wouldn't modify my system under any circumstances: `rustup show` `rustup check`...

> this used to be in the book, but it was removed to keep only the file in the git repo because they weren't updated in sync. Maybe we could...

Some of these documents really require being kept in sync with `main` (cargo-features for instance), and the website just needs a checkpoint of what's on `latest`, so I'm not sure...

Checking the blame for the relevant line shows this field was intentionally made private to fix another issue, so it does not seem to be a trivial fix unfortunately. -...