BD103

This is good to have, but I would prefer #13279 and #13187 to be merged first since they majorly refactor the `ci` tool.

@mockersf would you mind reviewing this?

That's an interesting idea.a For this issue specifically, I was more thinking of building the migration guide from `latest...main` nightly, so you could view all breaking changes as they were...

Closing as not planned. The dev-docs are more geared toward engine developers than actual users, especially since stable Bevy is mature enough that it covers most use-cases. If anything dev-docs...

To add on to this, this feature should at least be documented if it is intended to be used by others.

Some ideas: - Name - Logo - Year / last updated - Maybe also shortened commit hash? - GitHub link - Getting started link - Donate link - Book link...

Turns out "abledbody" is not styled with a color at all, so it uses the browser's default. I believe it is because the link is not within a `.media-content` class....

CI appeared to be failing because `typos` thought the commit number was a typo. I've excluded patch files from this check for the future.

Marking this as trivial :)

What if in the [example metadata](https://github.com/bevyengine/bevy/blob/e0778bf407631f9ae0f1e7326bb63e98d0e6fe87/Cargo.toml#L336-L340), you could specify a list of important related files that should also be shown on the website? ```toml [package.metadata.example.shader_material] name = "Shader Material" #...