The current technology for delivering Tech News, as an example, is something we’re immensely grateful for (because doing this manually would take forever), but it’s a way to update a page that doesn’t lend itself to automatic updates. This makes it time-consuming, invites mistakes over hundreds of pages across many wikis – the fact that we see so few of those is because those who send out Tech News have years of experience handling MassMessage on a regular basis, but it makes it more difficult for others to get involved – and we run into delivery problems where people don’t get their newsletters on a regular basis.
Having said that, I’ve got a couple of concerns regarding dynamic content that I’d like to see solved before we embark on replacing the current workflows. Today, community pages are one of the most important arenas. As a Village Pump is structured, people tend to go to the bottom to see new things (unless it uses Flow). To be discoverable, it’d have to behave as expected, i.e. be found where new content is found.
If you follow community pages for updates like these, your notification is in the watchlist. Would it be visible there? (Also, would it be discoverable in recent changes feeds? If not, that’s hardly a dealbreaker, but it does mean it gets harder to discover.)
I’m also concerned about discoverability over time – the ability to easily find multiple issues if you’ve been away for, well, nine days or so and missed a week – which I think will diminish a fair bit if you have to go to an archive, but I’d happily trade that for a simpler and more reliable process.