You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Something we've done for years is create a monthly update video going over commits and changes to the project in the previous month. This video normally launches on the last day of the month.
As part of the transition to being backed by the non-profit, we'd like to pair the update video with an update newsletter.
Here's some high-level feature requirements for this:
Newsletter posts are given a clearly delineated place on the homepage, distinct from the blog posts
To enable collaborative iteration on the newsletter throughout the month, some kind of standardized 'staging' area that shows up in dev builds but not in prod
Accommodations for embedding screenshots of visible features, and associating them with specific commits
A way to associate the newsletter with a 'series' that includes all previous blog posts.
Something we've done for years is create a monthly update video going over commits and changes to the project in the previous month. This video normally launches on the last day of the month.
As part of the transition to being backed by the non-profit, we'd like to pair the update video with an update newsletter.
Here's some high-level feature requirements for this:
Newsletter posts are given a clearly delineated place on the homepage, distinct from the blog posts
To enable collaborative iteration on the newsletter throughout the month, some kind of standardized 'staging' area that shows up in dev builds but not in prod
Accommodations for embedding screenshots of visible features, and associating them with specific commits
A way to associate the newsletter with a 'series' that includes all previous blog posts.
Some inspiration:
https://servo.org/blog/2024/06/28/input-text-emoji-devtools/
https://dolphin-emu.org/blog/2024/02/10/dolphin-progress-report-november-and-december-2023-january-2024/
The text was updated successfully, but these errors were encountered: