Screen shot on the home page uses obsolete for-each system syntax about bevy-website HOT 5 CLOSED

yup good call! ill see which one fits the image best.

(also its Query<(Entity, Component)>)

from bevy-website.

simple reproducible workflow

I just used inkscape to generate the svg:

1. add the text using the text tool
2. convert the text to a "path" using "Path -> Object To Path"
3. assign the colors to the appropriate places
4. resize the document to the context using "File -> Document Properties -> Resize page to content"

I prefer that over carbon because:

1. The SVG carbon exports uses "svg text", which means the browser controls the font / falls back when a font doesn't exist. The current approach "bakes" the font into curves to avoid this problem.
2. I'd want more control over the layout / spacing / color / margins than it provides.

Based on discussion in #documentation, the rough consensus was that the following example captured the spirit of Bevy's syntax well while being more approachable to beginners who don't know ECS jargon.

The point of the image was to quickly and minimally anchor ECS jargon into Bevy's syntax, not to introduce people to all of bevy's ecs features (ex: resources and query iteration). My preference would be for something more like this:

struct Component;
fn system(
  query: Query<(Entity, &Component)>
) {
}

from bevy-website.

@cart do you have any preference/requirement for what font should be used for the image?

I'd like to make a PR, but just want to confirm any requirements for the visual aesthetic / appearence first.

from bevy-website.

Awesome! I'd like it to be as similar to the current one as possible (ex: same colors and same font). I believe the font is Fira Mono

from bevy-website.

Based on discussion in #documentation, the rough consensus was that the following example captured the spirit of Bevy's syntax well while being more approachable to beginners who don't know ECS jargon.

fn system(
  players: Query<&Player>,
  game: Res<Game>
) {    
    for player in players.iter() {
        play(player, game);
    }
}

We could do this, a rough adaptation of the existing code, as proposed in the first bit of this issue, or something in between. That's your judgement call though @cart.

If we end up wanting lots of this sort of thing or a simple reproducible workflow, it was mentioned that swapping to a tool like carbon.now.sh might be a good choice.

from bevy-website.