Description
Editors: @17cupsofcoffee, @AngelOnFira and @ozkriff
Another month has gone by, so it's time to put together the Rust Gamedev newsletter with March's news!
Note: I'm trialling a slightly updated template for the co-ordination issue this month - let me know if you have any feedback!
Current Schedule
The deadline for all section PRs is the 9th of April.
We may still accept PRs that are submitted later than this, as long as they're ready before the newsletter's release, but this isn't guaranteed. If you want your section to be included, don't leave it till the last minute!
How to Contribute
If you want to help writing the newsletter:
- Read CONTRIBUTING.md.
- Choose one or more of the "🆓 free" sections listed below, and leave a comment letting us know you want to work on them.
- The links in brackets (like "1, 2, 3") are suggestions of links to include in the section. Feel free to add more!
- The username listed next to the section (like "@ozkriff?") is a suggestion of who may want to pick up the work (usually the project's developer, or someone who has expressed interest in the past).
- You are not obligated to write a section if you're tagged or your project is listed! You're welcome to ask someone else to write the section, or to ask for your project to be excluded from this month's post.
- Extra sections not listed in the plan are welcomed - just leave a comment and open a PR!
- Write a short overview in the newsletter's Markdown file, making sure to follow the style guidelines (see below).
- Send a PR to the
source
branch (example: N15: A/B Street #336). - Mention this issue in your PR's description to link it all together.
Style Guidelines
The full style guide is in CONTRIBUTING.md, but here are the most important rules:
- Write in third-person perspective.
- Each line must be 80 characters or less, for ease of reviewing/diffing.
- Only one image per section is allowed.
- The maximum size is 300kb for static images and 2.5mb for GIFs.
- The image should come before the text, and must have alt text for accessibility.
- Prefer static images to GIFs, to keep the page load times down.
- Each section should be under 1000 characters, and under 6 paragraphs.
- This only applies to the rendered text, not the markup.
- Keep formatting minimal - no bold/italics/etc.
- Avoid long/nested bullet point lists - no changelogs!
Please use these templates as a starting point:
Games/apps/libraries:
### [Game name]

_optional image label_
[Game name] ([GitHub], [Discord], [Twitter]) by [@nickname]
is... {short project description in one sentence}.
{An overview of the recent updates with links to more details}.
_Discussions: [/r/rust_gamedev](link), [Twitter](link), [etc](link)_
[Game name]: http://example.com
Articles/blog posts/videos/etc:
### [Article name]

_optional image label_
[@nickname] published an [article] about...
{overview what the resource is about}.
_Discussions: [/r/rust_gamedev](link), [Twiter](link), [etc](link)_
[Article name]: http://example.com
Current Structure & Status
Below is our current planned structure for the newsletter, and the status of each PR (which we'll try to keep updated).
This is not an exhaustive list - if you have your own project that you want to write about, just make a comment on this issue and open a PR!
Rust Gamedev Meetup
- Details of this month's meetup - ✔️ done
Rust Gamedev Podcast
- A/B Street Interview (1) - ✔️ done
Game Updates
Learning Material Updates
- Making One Game Per Week (1) - 🆓 free (couldn't find username - let me know if this is your project!)
Engine Updates
Tooling Updates
Library Updates
Other News
- Bullet points of any interesting news that doesn't have its own section - 🆓 free (@17cupsofcoffee?)
Discussions
- Details of any gamedev-related discussion threads - 🆓 free (@17cupsofcoffee?)
Jobs
Publishing Steps
- Final review - by everyonePublish - by @17cupsofcoffeePost on /r/rust, /r/rust_gamedev, /r/gamedev, URLO, twitter.com/rust_gamedev - by @17cupsofcoffeePin thread on Twitter - by @ozkriffAdd comment links - by @17cupsofcoffeeAdd a draft of next month's newsletter - by @17cupsofcoffee
Activity
[-]Newsletter 32: March 2022[/-][+]Newsletter 32 - March 2022[/+]kettle11 commentedon Apr 1, 2022
I'll take
terrain_generator
andBloom3D
.A question: How do people usually edit their submissions? Using GitHub's markdown editor is nice and easy but there's no way to check the line-width (right?) which makes it a bit of a pain. Do most people
Clone
and use a code-editor that automatically wraps based on a configurable line-width?17cupsofcoffee commentedon Apr 1, 2022
@kettle11 - I agree it's mega awkward that GitHub doesn't expose this 😢
I generally just open a new file in VS Code, write my section there and then copy and paste it into the web editor.
henryksloan commentedon Apr 1, 2022
I'll take rust-nonogram.
nicopap commentedon Apr 2, 2022
I'd be more than happy to take the Warlock's Gambit section.
Enet4 commentedon Apr 2, 2022
Yup, I'm on it.
HackerFoo commentedon Apr 2, 2022
I'll do this section, thanks.
N32: Add Warlock's Gambit section
N32: Add Warlock's Gambit section
N32: Add Warlock's Gambit section
40 remaining items