Add smaller and more frequent news posts

### Observation

The current release posts are very valuable, but they are usually very long and mostly centered around a version number.

These articles are useful for existing Bevy users who want to know everything that changed in a release. However, for people who do not know Bevy yet, they can be hard to approach.

I do not often see news articles structured this way on other game engine websites: one very large article summarizing an entire year of development.

These long release posts should absolutely continue to exist, but they could coexist with smaller and more frequent news posts.

#### Related discussions

Proposal: Bevy Guest Lectures #1903

### Suggestion

The website could include shorter official news posts on a more regular basis.

For example:
- previews of features coming in the next release;
- short posts about new rendering, UI, ECS, tooling, or editor-related progress;
- game jam announcements;
- game jam results;
- highlights of games made with Bevy;
- interviews or short spotlights on community projects;
- statistics about Bevy usage or community growth;
- ecosystem updates;
- “what is new this month” style posts.

These posts would not need to be as complete as release notes. Their goal would be different: to make Bevy feel active, alive, and easier to follow.

### Examples from other engines

Examples of smaller news posts from Godot:
- [HDR output arrives in Godot 4.7](https://godotengine.org/article/hdr-output-arrives-in-godot-4-7/)
- [Godot usage and engine growth](https://godotengine.org/article/godot-growth-stats-2026/)

These kinds of articles are easier to read for people who are still discovering the engine or comparing it with other solutions.

### Expected impact

More frequent and accessible official content could help:
- provide more entry points for newcomers;
- make Bevy’s development feel more active;
- improve discoverability of specific features;
- help people understand what Bevy is capable of;
- reduce bounce rate for visitors who are still in the comparison phase;
- support adoption by giving people more confidence in the project’s momentum.

### Possible implementation direction

Keep the existing long release posts, but add a second type of news content: shorter, more regular posts focused on one topic at a time.

This could make the website more accessible without losing the depth of the current release articles.

The issue identifies no files, tests, or implementation entry points. Start by reviewing how the website currently publishes long release posts; done would require a decided, implemented approach for shorter, more frequent news content alongside those posts.

Written by the indexing model from the issue text.