Finally published this on what my team have been doing at @thetimes for the past two years: fixing a ton of backend, and building a new frontend for journalists to construct our homepage.

We call it Edition Builder. Because I can't stand obscure naming. https://medium.com/digital-times/building-editions-at-the-times-2c634ec0912b
From a prototype that @chrishutchinson and I came up with years ago, to today's edition live in the system.

This is super niche, but also super important imo, because as a publisher you need to own as much of your publishing stack as possible (because y'know, its your business)
This is especially true if you come up with anything remotely innovative, like the concept of serialised or edition-based publishing, like we did at The Times and Sunday Times, and then based it on a system that made it difficult to do for years.
Your journalists will only be able to do as much as you enable them to do, and a lot of that nowadays is in what your system gives them in terms of ease of use, augmented production and process, and extensibility.

This is a tenet that we forgot when we moved to digital media.
We'll do a few more pieces in the coming weeks (when I get back from 🇲🇾 for CNY) that focus on the engineering challenges, and the cultural barriers we had to overcome. Good lessons I hope for many media orgs.

Fav this and I'll make sure you don't miss them 😄
And to those that signed up for the second post and never heard back, sorry!😢

Thank you and a fresh 👋 to @jonhew @jshield @gdoppelese @Adriana_Lacy @risj_oxford @webcurtpsu @benwhitelaw @MrJonty @germaineasa @aendrew hope you're all doing great
You can follow @MattieTK.
Tip: mention @twtextapp on a Twitter thread with the keyword “unroll” to get a link to it.

Latest Threads Unrolled: