canada.com was the property in the network that didn’t fit the newsroom template, because canada.com didn’t have a newsroom.
It was a portal — aggregating coverage from the regional dailies up to the National Post at the top, surfacing the network’s strongest stories under a single national brand. That changes the build problem at the root. Each Postmedia property ran as its own child theme on a shared parent; canada.com’s child theme had to behave less like a newsroom and more like an aggregator on top of the same upstream code. Feed strategy, taxonomy normalization across papers, image-convention forgiveness — the portal child theme absorbed editorial mismatches that the individual newsroom children didn’t have to think about. Same parent, completely different child-theme posture.
In 2011-2012, when Postmedia moved its network of daily newspapers onto WordPress, canada.com landed on WordPress VIP alongside the rest of the rollout — at the time, one of a small handful of major Canadian news properties on the platform. VIP onboarding then required direct vetting from Automattic’s VIP team and a codebase review before the first deploy. The shared-parent model was what made that defensible: review the parent thoroughly, and the eleven children inherited that work.
That was the architecture story. The bet was that one well-maintained parent theme could carry eleven editorially distinct properties without fragmenting into eleven forks. It held. If you’re running a network site today and watching maintenance cost balloon as each property drifts from a common base, this is the pattern worth revisiting.
