In 2011-2012, when Postmedia moved its network of daily newspapers onto WordPress, the National Post landed on WordPress VIP — at the time, one of a small handful of major Canadian news properties on the platform. I worked on the build as part of that migration. WP VIP in that era was not a commodity purchase: onboarding required direct vetting from Automattic’s VIP team and a codebase review before the first deploy.
The Post was the flagship the rest of the network had to clear behind. That meant the parent theme had to ship production-ready against the most demanding property first. The eleven Postmedia papers each ran as a distinct child theme on a single shared parent — same upstream codebase, brand and editorial controls held in the child. When the parent earned a fix, all eleven properties inherited it on the next deploy. That was the operational ROI for the publisher; for the engineering side it meant the National Post’s performance ceiling effectively set the ceiling for everything downstream.
The customization decisions tracked the newsroom, not the design system. Homepage curation cycles, breaking-news cache behaviour, ad-load budgets, the speed of getting a column from CMS to reader — those drove the brief. Theme engineering on a flagship daily isn’t styling; it’s making sure publishing rhythm holds up under load.
Doing this on VIP, in 2011-2012, was the part that’s hard to fully convey now that VIP is a more familiar option. At the time the question of whether WordPress could carry a national daily was still contested. Putting the Post on it — and then canada.com beside it — answered that question in production. Most of the rest of the network followed.