The National Post is the youngest of Canada’s two national newspapers, founded in 1998 by Conrad Black as a deliberate national-daily competitor to the Globe and Mail. By the time the platform migration that this engagement was part of arrived in 2011-2012, the Post was a centre-right voice on a different cadence than its older national rival, with a column-driven editorial identity and a publishing rhythm that mixed national breaking news, Ottawa political reporting, business coverage from the Financial Post side of the building, and the kind of long-form opinion writing that built the paper’s audience. The work was a WordPress® theme engagement on WordPress® VIP, part of Postmedia’s network-scale platform consolidation.
The flagship of the migration
Postmedia had taken ownership of the Canwest newspaper chain in 2010, and the WordPress platform migration that followed was a network-scale move: eleven daily papers, a national portal, and the editorial blog networks that sat alongside each. The architectural decision was a single shared parent theme with eleven distinct child themes — same upstream codebase, per-paper brand and editorial controls held in the child. When the parent earned a fix, every property inherited it on the next deploy.
That model only works if the parent theme is hardened against the most demanding property first. The Post was that property. Front page traffic patterns on a national daily are different than on a regional paper — breaking news from anywhere in the country can land at any hour, columnist posts pull audience independently of the homepage curation, and the article template has to absorb both four-paragraph wire updates and four-thousand-word weekend essays without forking the layout. Once the parent was right against the Post’s reality, the rest of the network’s child themes became economical to maintain.
WordPress VIP in 2012 was a contested question
It is hard to convey now, after a decade of WordPress carrying every shape of publisher from indie newsletters to the New York Times Cooking, how unsettled the question was in 2012 whether the platform could be trusted with a major national daily. WordPress VIP — Automattic’s hosted enterprise tier — was already running some serious publishers, but onboarding then required direct vetting from the VIP team, a full codebase review before the first deploy, and ongoing engineering discipline that wasn’t part of the standard WordPress build conversation. Putting the National Post on it, and then canada.com beside it, was part of the body of work that settled the question in production. Most of the rest of the network followed.
The customization decisions on the Post 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, the discipline of comment moderation at flagship scale — those drove the brief. Theme engineering on a national daily is not styling. It is making sure publishing rhythm holds up under load on the day a story breaks at 10 PM Eastern and the homepage editor is asleep.
- The work: Theme engineering on the network’s flagship daily during the 2011-2012 Postmedia WordPress VIP migration
- Architecture: Single shared parent theme + eleven child themes across the Postmedia network
- Client: Postmedia Network Inc.
- Period: 2011-2012
The pattern this work calibrated still informs every multi-property publishing engagement I take on. Harden the parent against the hardest property first. Hold the editorial identity in the child. Make sure the platform’s production posture is settled before the first regional paper inherits it.
Product names referenced on this page — including WordPress — are trademarks or registered trademarks of their respective owners. Training offered here is independent and is not affiliated with, endorsed by, or sponsored by any of these companies.