Long term and epic projects may benefit from individual, subscriber-based newsletters so that interested users can follow progress. See the many options at Newsletters.
This type of newsletter is typically created every 2-3 months and tends to be more in-depth than TechNews.
Office and Meta sandboxes
Gather information from relevant people and documentation;
Typical structure for a newsletter issue:
Links to read newsletter in other languages and to subscribe to multilingual delivery;
DYK ("Did You Know?) box at the right, to highlight the most recent or interesting change;
Short list of recent changes;
List of upcoming/future changes;
Call to action (upcoming testing, feedback, public meetings, documentation translations, signing up for newsletter's translations);
Ensure that the page has a "marker", a <section> tag which identifies it (see the top of any issue while in Edit mode; it’s currently VE-news for VisualEditor’s newsletter.);
Click the "mark for translation" link at the top of the page (only visible to translation administrators);
Try to translate something into any language to check formatting or if you need to fix something;
Mark the page for translation again - dummy edits sometimes help to propagate changes;
Last chance to review or add items, otherwise you'll waste translators' time and efforts.
Request translations support by emailing volunteers at email@example.com (and by MassMessage, if the team has a list of community members interested in translating that specific content);
Think twice before using the on-wiki notification system to notify volunteer translators; it pings translators who may not be interested in the product (It is not used for the VE newsletter);
Check all translations for red links. Fix any you find;
Update the page which hosts the code necessary for sending (such as VisualEditor's): after you click Edit, update the month’s name and change the codes for the languages with those you see at the top of your translated issue, regardless of their completion percentage, then save;
Search (command-F or ctrl-F in your browser) for any dollar signs ("$") to check for incorrectly formatted tvars: fix any you find, and make a null edit on the Sandbox page to update its contents.
Copy the whole wall of code you see on the page now (unclear);