bevyengine / bevyengine/bevy-website

Make an "Are We Bevy Yet" Section

Open
#114 2 comments 3 reactions 0 assignees View on GitHub
A-Home C-Feature
Dominant language
JavaScript
Stars
249
Forks
450
Avg merge
16h 20m
Merged PRs (30d)
6

Description

## What problem does this solve or what need does it fill?

This would be a nice easy to use tracker for the big game engine areas assets, ui, editor, rendering stuff.
## What solution would you like?

We could buy the website arewebevyyet.org and make that similar to arewegameyet.rs
## What alternative(s) have you considered?

I guess this could also just be a section on the bevy website.
## Additional context

The main reason I thought this was a good issue is that not every wants to dig into a github page to learn stuff about a project. Most people who get into bevy will probably look at its website, not at the github issues/discussions.

Project board and issues tends to be updated with development, this should be updated for released versions.

Some examples: https://arewegameyet.rs/
https://www.arewewebyet.org/

Contributor guide

Open the contributing guide

Research direction

The issue does not name any files, tests, or entry points. Start by reviewing the bevy-website structure and the linked arewegameyet.rs example, then determine how a tracker for assets, UI, editor, and rendering would fit the site. Done means a released-version tracker is available on the Bevy website or a dedicated site.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
frontend, web-dev
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.