A modest proposal to offer users a modified delivery method as an option to receive the message collapsed, or just a link to it. I am interested in the tech newsletter content, but I don't wish to have the whole message 1) occupying vertical space, or 2) substed onto my page. My preference would be to receive a message with the same header you currently offer, but containing the transcluded (not substed) content, and collapsed by default via {{collapse top}} & bottom, {{hidden}}, or similar. Doable? If not, instead of a collapsed transclusion, just a one-sentence message with a link to the content. I suppose your archiving means the original transclusion or link would no longer work at some point, but that is not a problem for me. If this were available I would opt in. Thanks,Mathglot (talk)21:16, 8 November 2025 (UTC)Reply

Transclusion is not really possible, as the newsletter is delivered on many wikis, and cross-wiki transclusion is not possible. (The titles of the issues remain the same forever from the moment they get drafted, so that wouldn’t be a problem.) A one-sentence message with a link would technically be possible, although it’d mean extra administration for the people who manage the newsletter (they’d need to send the two variants separately), so I don’t want to make promises in their names. —Tacsipacsi (talk)00:20, 9 November 2025 (UTC)Reply

+1 to Tacsipacsi's explanation (thanks!). Also, on some wikis there is a local page setup that enables transluding the entire latest version into the location of your choice, which might enable what you're after, or something close-enough to it; seew:en:Template:Latest tech news for example. HTH.Quiddity (WMF) (talk)01:38, 9 November 2025 (UTC)Reply

The link tohttps://meta.wikimedia.org/wiki/Talk_pages_project/Feature_summary#Usability_improvements in the first item of Tech News 2025-46 leads to a page that does not exist. You might want to put a redirect there that takes people to the intended destination, and put checking every link in Mass Messages onto your checklist.Jonesey95 (talk)20:41, 10 November 2025 (UTC)Reply

Thank you @Jonesey95 ––STei (WMF) (talk)21:34, 11 November 2025 (UTC)Reply

Rephab:T58362#11364637, how come the#User-notice tag was removed from that task? In my experience previously, it seems like it's been okay for tasks to just sit in the 'Not ready to announce' column until they're ready (at which point someone usually moves the task on the workboard). One potential benefit of this is that it doesn't then need someone to remember to re-add the tag in the future :)

To confirm, has something changed in how the tag should be used?(I'm asking here rather than on the task itself as I guess my question is slightly broader than that specific action, and also to avoid potentially cluttering up that task's history!) [cc @STei (WMF)] Best,‍—‍a smart kitten_[meow]20:38, 11 November 2025 (UTC)Reply

@A smart kitten, for a task to remain in the “Not Ready to Announce” column on the workboard, it should show signs of active progress. When a task, even with a user-notice tag hasn’t been updated for a while, it automatically stops appearing on the board. Unfortunately, even minor updates such asproject changes can cause these inactive tasks to reappear on the workboard, even when no real progress has been made. This adds workload, as we then need to review and verify each recently updated card for actual announcement readiness. ––STei (WMF) (talk)21:34, 11 November 2025 (UTC)Reply

Thanks for the reply, @STei (WMF)!we then need to review and verify each recently updated card for actual announcement readiness. I guess my next question is probably - how come?_/gen Please forgive me if e.g. there's a reason why this wouldn't work, but how come the devs working on each task in the 'Not ready to announce' column couldn't be relied on to move the task to the 'Announce in next Tech/News' column at the point when it's ready to be announced? Best,‍—‍a smart kitten_[meow]21:41, 11 November 2025 (UTC)Reply

@A smart kitten in my experience so far, the Tech News team mostly handles moving tickets around on the usernotice workboard, fewer external contributors take on this responsibility. However I will put the tags back so devs and community don't have the burden to remember to add it back when work picks up. ––STei (WMF) (talk)20:54, 13 November 2025 (UTC)Reply

@STei (WMF) Thank you :)

in my experience so far, the Tech News team mostly handles moving tickets around on the usernotice workboard, fewer external contributors take on this responsibility. Thinking out loud -- perhaps it might be worth an email towikitech-l to ask if folks could do this more often? As I'd probably assume that the people working on each task might hopefully have a good idea of when it'd be ready to be announced (and this would hopefully save the Tech News team some time that might otherwise be spent on trying to assess the announcement readiness of each task, as youreferred to).Apologies for the delayed reply! Best,‍—‍a smart kitten_[meow]21:37, 22 November 2025 (UTC)Reply