bevyengine / bevyengine/bevy-website

Gather all examples from blog posts

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

Description

Repost of [this issue](https://github.com/bevyengine/bevy/issues/7935) since it belongs here instead of the bevy repo :)

## What problem does this solve or what need does it fill?
First of, I'm only writing about the 0.10 and up coming releases, everything else is unrealistic
Me and I think a lot of other users often remember a cool example from the blog posts they want to reproduce/study.
Currently, there is almost no way to find the source besides asking around.
I think we all are aware that making a new release is stressful enough and no one has the time nor the extra motivation to collect and document these examples.
However, I would argue that a big part of the problem is that no infrastructure exists to collect the examples.

## What solution would you like?
A list of all examples with links to there repositories or creators.
It should be clear to the reader that the examples were not written for educational reason but to show this specific feature,
therefore the code quality doesn't have to be perfect. If someone wants to take a look it is on their own risk.

This list could be inside a small external repository which the blog post links to.
Alternatively, it could also be another subside of the website similar to the migration guide

## What alternative(s) have you considered?
To let the external repository contain the examples.
Would have the advantage that the example owner couldn't just change or delete his example
How ever I like the thought that some time after the release the example owner could still cleanup the example if wanted.

Additional context
I also think it would be a nice way to honor the people doing the examples.

Contributor guide

Open the contributing guide

Research direction

Start by reviewing the linked Bevy issue, the Bevy 0.10-and-later blog posts, and the website's migration guide to determine where this catalog belongs. Done means providing a maintained list of the relevant examples with links to their repositories or creators and clear context that they are showcase code rather than educational examples.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
documentation
Issue type
Documentation
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.