< Tech‎ | News
This page documents the publishing process for the weekly Tech News newsletter. It provides guidelines based on our experience in creating this particular newsletter, but might also be used as a guide for other Wikimedia publications that are delivered to multiple wikis.

The following notes are intended to serve as guidelines for the process of publishing the Tech/News weekly newsletter and as a place to gather experiences and best practices learned from the publication and delivery of the newsletter's previous issues. There are more details about deadlines and inclusion criteria for editors who want to contribute or translate.

Writing guidelinesEdit

Brief version: Tech/News#contribute
You can check your writing in the Hemingway app and the Up-Goer 6 tools that will highlight complex sentences and rare words.
There are a few guides to writing in plain English.
For more specific guidelines, you can try the English Wikipedia Signpost's style guide as well as the more general Manual of Style. Consider using prepositions liberally and avoiding grouping long phrasal groups composed of many nouns.
Be careful with links to wikis other than, Commons, Wikidata, and Wikispecies. If you want the links to always work in the same way, always use m:Example to link to anything on Meta-Wiki; always use w:en:Example to link to anything on English Wikipedia; always use q:de:Beispiel to link to anything on German Wikiquote.
All visible MediaWiki or HTML tags should be wrapped in <code><nowiki>...</nowiki></code>;
Add the direction of LTR blocks, for RTL languages compatibility. For instance, <code dir=ltr>.mw-ui-constructive</code> will be rendered as a LTR text in a RTL translation.
A fully bi-directional code-snippet might look like this:
<tvar name="ltr-code"><bdi lang="zxx" dir="ltr"><code><nowiki> ... the code snippet ... </nowiki></code></bdi></tvar>
  • Whenever issues contain text similar to one that had already been published, use the same <tvar name="name"> to reduce amount of work required of translators and take advantage of translation memory.
  • Inline links that are not supposed to be translated should be put inside <tvar> to simplify translations and direct all users to the same page, for example: [[c:somelink|description]];
    • For recurring items, use the same tvar, so that translators can use translation memory more easily. link, link2, link3 etc. are good generic tvar labels.
    • When you put displayed text inside a tvar, add directionality markers so it displays properly on RTL wikis (and ideally also the language): <span class="mw-content-ltr" lang="en" dir="ltr">your content</span>
  • &rlm; can solve some RTL problems. Example.
  • Reference links (e.g. to Phabricator tickets) should be at the end of an item, outside the <translate> tags. External links are preferred (even if an interwiki link is possible) because they're automatically numbered.
  • Interface messages (button names, etc.) should be internationalized using {{int:...}}. See mw:Help:Magic words#Localization for details. Append ?uselang=qqx (or &uselang=qqx) to a URL, to show the interface message's variable name. Example.
  • Here are some standardized lines we occasionally have to use:
    • There is no new MediaWiki version this week.
    • MediaWiki <tvar name="mwversion">1.36.0-wmf.1</tvar> was scheduled to be deployed on some wikis last week. The deployment was delayed because of unexpected problems.
    • You will be able to read but not edit [[<tvar name="somewikis">phab:T1111111</tvar>|some wikis]] for a few minutes on {{#time:<tvar name="defaultformat">j xg</tvar>|<tvar name="date2">2020-01-01</tvar>|<tvar name="format_language_code">{{TRANSLATIONLANGUAGE}}</tvar>}}. This will happen around [<tvar name="time"></tvar> 05:00 UTC]. This is for database maintenance.
    • [[<tvar name="switch">m:Special:MyLanguage/Tech/Server switch</tvar>|All wikis will be read-only]] for a few minutes on 14 September. This is planned at [<tvar name="time"></tvar> 14:00 UTC].
  • Search the Tech/News/Archives for any other previous mentions of specific or related topics.
  • You can add the "Recurring item" and "Advanced item" icons to the start of entries (before the entry's own <translate> marker), by copying these lines:
  • [[File:Octicons-sync.svg|12px|link=|<translate>Recurrent item</translate>]]
  • [[File:Octicons-tools.svg|15px|link=|<translate>Advanced item</translate>]]

Publication scheduleEdit

See also: Tech/News/For contributors#When is the work done?

The current distribution date for the newsletter is Monday, at around 3:00 pm (UTC). This deadline is linked to from the upcoming issue.


See an overview of the process in this 2014 blog post

The distribution generally happens on Monday between 15:00–19:00 (UTC). If you change that time, update the deadline linked to from the upcoming issue.

  1. Purge this page to fix the "week numbers" below.
  2. Open the edition and do the final change and checks
    1. Remove the "deadline" template, and mark for translation.
    2. Open all translations on Meta and check for these problems in case there was an error during the translation:
      • red links
      • broken tvars
      • random linebreaks
  3. Test the message – Make a test delivery using a small test distribution list; the process is the same as for the actual delivery (described further below), except for the target list.
    1. Open Special:MassMessage in another tab or window
    2. In "Page or category containing list of pages to leave a message on": use the page-name of your test distribution list (examples by Guillaume, Johan, Quiddity, Trizek)
      • Test distribution list: A good rule of thumb is to check:
        • on the English Wikipedia
        • on another language with an existing translation
        • on another language without a translation (defaulting to English)
        • on an RTL wiki
        • on a multilingual wiki (e.g. mediawikiwiki, commons, wikidata, etc)
        • on a Flow talk page
        • and on a community page in a localized namespace.
    3. In "Subject of the message (also used as the edit summary)":
      • [[m:Special:MyLanguage/Tech/News/2021/48|Tech News: 2021-48]]
      • ↑ Check this week number is correct ↑
    4. In "Page to be sent as a message", add the page name of the issue you are delivering. Example:
      • Tech/News/2021/48
      • ↑ Check this week number is correct ↑
    5. Click on the Preview button
    6. Go to "Section of the page" and choose "tech-newsletter-content".
    7. Add the timestamp in "Body of the message" using 5 tildes: ~~~~~
    8. Preview again
    9. If everything looks good, click the Send button on the page.
      • Test it exactly like you plan to send it, including the subject of the message.
      • Open each of the pages in your test distribution list, to check if they arrived properly.
        • (Pay attention to any new bluelinks or redlinks, which might indicate a problem)
      • If you see a mistake, test it again after you fixed the mistake.
  4. Launch the actual delivery
    1. Go through the same process as when testing, except in Step #2 replace the target delivery list with the actual one:
      • "Page or category containing list of pages to leave a message on":
        • Global message delivery/Targets/Tech ambassadors
    2. [...]
    3. Do a final check, and if everything looks good, click on the Send button on the page
  5. Wrap up
    1. Thank the translators on their mailing list at
    2. Send the English edition to the Tech ambassadors at in an HTML e-mail (topic: Tech News 2021, week 48). Copy the text of the newsletter from the desktop site. You may have to copy the language bar into a text document and copy it again to get the right amount of formatting.
    3. Publish it on Diff (m:Diff (blog))
      1. Create a new blog post,
      2. copy & paste the content from the edition into the blog-post body,
      3. add a header as Tech/News/2021/48,
      4. categorize it with technical news and technology,
      5. tag it with tech-news,
      6. click "Publish" and "Submit for review".

Structural components of Tech/NewsEdit