|
| 1 | +--- |
| 2 | +title: "Newsletter {{ env.NEWSLETTER_COUNTER}}: {{ env.NEWSLETTER_MONTH }} {{ env.NEWSLETTER_YEAR }}" |
| 3 | +labels: coordination, help wanted |
| 4 | +assignees: janhohenheim |
| 5 | +--- |
| 6 | + |
| 7 | +###### tags: `newsletter` |
| 8 | + |
| 9 | +**Editors:** |
| 10 | + |
| 11 | +Another month has gone by, so it's time to put together the Rust Gamedev |
| 12 | +newsletter with {{ env.NEWSLETTER_MONTH }}'s news! |
| 13 | + |
| 14 | +## Current Schedule |
| 15 | + |
| 16 | +The deadline for all section PRs is the **03.{{ env.NEWSLETTER_DEADLINE }}** |
| 17 | + |
| 18 | +We _may_ still accept PRs that are submitted later than this, as long as they're |
| 19 | +ready before the newsletter's release, but this isn't guaranteed. |
| 20 | +If you want your section to be included, don't leave it till the last minute! |
| 21 | + |
| 22 | +## Current Structure & Status |
| 23 | + |
| 24 | +Below is our current planned structure for the newsletter, |
| 25 | +and the status of each PR (which we'll try to keep updated). |
| 26 | + |
| 27 | +This is **not** an exhaustive list - if you have your own project that you want |
| 28 | +to write about, just make a comment on this issue and open a PR! |
| 29 | + |
| 30 | +### Game Updates |
| 31 | + |
| 32 | +- TODO |
| 33 | + |
| 34 | +### Learning Material Updates |
| 35 | + |
| 36 | +- TODO |
| 37 | + |
| 38 | +### Engine Updates |
| 39 | + |
| 40 | +- TODO |
| 41 | + |
| 42 | +### Tooling Updates |
| 43 | + |
| 44 | +- TODO |
| 45 | + |
| 46 | +### Library Updates |
| 47 | + |
| 48 | +- TODO |
| 49 | + |
| 50 | +### Other News |
| 51 | + |
| 52 | +- TODO |
| 53 | + |
| 54 | +### Discussions |
| 55 | + |
| 56 | +- TODO |
| 57 | + |
| 58 | +## Publishing Steps |
| 59 | + |
| 60 | +- [ ] Final review - by everyone |
| 61 | +- [ ] Publish - by @janhohenheim |
| 62 | +- [ ] Post on /r/rust, /r/rust_gamedev, /r/gamedev, URLO - by @janhohenheim |
| 63 | +- [ ] Pin thread on Twitter - by @AngelOnFira |
| 64 | +- [ ] Add comment links - by @AngelOnFira |
| 65 | + |
| 66 | +## How to Contribute |
| 67 | + |
| 68 | +If you want to help writing the newsletter: |
| 69 | + |
| 70 | +- **Read [CONTRIBUTING.md](https://github.com/rust-gamedev/rust-gamedev.github.io/blob/source/CONTRIBUTING.md?rgh-link-date=2023-09-12T16%3A17%3A34Z).** |
| 71 | +- Choose one or more of the "🆓 **free**" sections listed below, and leave a |
| 72 | +comment letting us know you want to work on them. |
| 73 | + - The links in brackets (like `[1](#), [2](#), [3](#)`) are suggestions of |
| 74 | + links to include in the section. Feel free to add more! |
| 75 | + - The username listed next to the section (like `@janhohenheim?`) is a |
| 76 | + suggestion of who may want to pick up the work (usually the project's |
| 77 | + developer, or someone who has expressed interest in the past). |
| 78 | + - You are not obligated to write a section if you're tagged or your project |
| 79 | + is listed! You're welcome to ask someone else to write the section, |
| 80 | + or to ask for your project to be excluded from this month's post. |
| 81 | + - Extra sections not listed in the plan are welcomed - |
| 82 | + just leave a comment and open a PR! |
| 83 | +- Write a short overview in the newsletter's Markdown file, |
| 84 | +making sure to follow the style guidelines (see below). |
| 85 | +- Send a PR _to the `source` branch_ (example: [N15: A/B Street #336](https://github.com/rust-gamedev/rust-gamedev.github.io/pull/336)). |
| 86 | +- Mention this issue in your PR's description to link it all together. |
| 87 | + |
| 88 | +## Style Guidelines |
| 89 | + |
| 90 | +The full style guide is in [CONTRIBUTING.md](https://github.com/rust-gamedev/rust-gamedev.github.io/blob/source/CONTRIBUTING.md?rgh-link-date=2023-09-12T16%3A17%3A34Z), |
| 91 | +but here are the most important rules: |
| 92 | + |
| 93 | +- Write in third-person perspective. |
| 94 | +- Each line must be 80 characters or less, for ease of reviewing/diffing. |
| 95 | +- Only one image per section is allowed. |
| 96 | + - The maximum size is 300kb for static images and 2.5mb for GIFs. |
| 97 | + - The image should come before the text, and must have alt text for accessibility. |
| 98 | + - Prefer static images to GIFs, to keep the page load times down. |
| 99 | +- Each section should be under 1000 characters, and under 6 paragraphs. |
| 100 | + - This only applies to the rendered text, not the markup. |
| 101 | +- Keep formatting minimal - no bold/italics/etc. |
| 102 | +- Avoid long/nested bullet point lists - no changelogs! |
| 103 | + |
| 104 | +Please use these templates as a starting point: |
| 105 | + |
| 106 | +**Games/apps/libraries:** |
| 107 | + |
| 108 | +```md |
| 109 | +### [Game name] |
| 110 | + |
| 111 | + |
| 112 | +_optional image label_ |
| 113 | + |
| 114 | +[Game name] ([GitHub], [Discord], [Twitter]) by [@nickname] |
| 115 | +is... {short project description in one sentence}. |
| 116 | + |
| 117 | +{An overview of the recent updates with links to more details}. |
| 118 | + |
| 119 | +_Discussions: [/r/rust_gamedev](link), [Twitter](link), [etc](link)_ |
| 120 | + |
| 121 | +[Game name]: http://example.com |
| 122 | +``` |
| 123 | + |
| 124 | +**Articles/blog posts/videos/etc:** |
| 125 | + |
| 126 | +```md |
| 127 | +### [Article name] |
| 128 | + |
| 129 | + |
| 130 | +_optional image label_ |
| 131 | + |
| 132 | +[@nickname] published an [article] about... |
| 133 | +{overview what the resource is about}. |
| 134 | + |
| 135 | +_Discussions: [/r/rust_gamedev](link), [Twiter](link), [etc](link)_ |
| 136 | + |
| 137 | +[Article name]: http://example.com |
| 138 | +``` |
0 commit comments