[Merged by Bors] - Basic documentation for Entities, Components and Systems

[alice-i-cecile]

These are largely targeted at beginners, as Entity, Component and System are the most obvious terms to search when first getting introduced to Bevy.

[Ratysz]

I've got a bit carried away during reveiw. You don't have to agree with any of these changes; I'll list my reasons for them anyway.

Component doc reads as subjective: "in a straightforward and efficient fashion", "is very simple", "commonly", "is known as"...

Components are not what stores - they are what is stored.

I understand the desire to use "if and only if", but "X is Trait + OtherTrait" is unambiguous, more popular in Rust docs, and allows for some seriously concise sentences.

It's not necessary to mention Rust. The users do, presumably, know what language they're working with.

I'm partial to dry and impersonal style - this is technical documentation, it should be as to the point as possible. It does have the unfortunate tendency to start all sentences the same way, though.

Trimmed lines to 100 symbols - this is what rustfmt usually targets for code; maintaining that for comments and docs is not required, but I like it for consistency (and it removes the horizontal scrollbar in my IDE).

[alice-i-cecile]

I liked your changes a lot @Ratysz, and you're likely correct about tone, even if it's a bit drier than is perhaps ideal for certain audiences. We can save a more approachable tone for examples and the book.

Very good idea to include a link to the docs on how to order systems in the System docs.

I had expected rustfmt to trim the doc comments to the appropriate length automatically 😅

[cart]

Looks good to me!

[cart]

bors r+

[bors]

Pull request successfully merged into main.

Build succeeded:

• build-android
• build (nightly, ubuntu-latest)
• build (stable, macos-latest)
• build (stable, ubuntu-latest)
• build (stable, windows-latest)
• build-wasm (nightly, ubuntu-latest)
• build-wasm (stable, ubuntu-latest)
• markdownlint