canada.com was the property in the Postmedia network that did not fit the newsroom template, because canada.com did not 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 and a domain whose authority value comfortably exceeded any single regional paper’s. The platform was WordPress® VIP, the same upstream stack the newsroom properties ran on.
An aggregator child theme on a newsroom parent
The Postmedia migration architecture put eleven editorial properties on a single shared parent theme with per-property child themes. Ten of those children were newsroom themes — variations on the daily-paper publishing shape. canada.com’s child was structurally different. The parent’s editorial primitives — the article template, the section landing, the comment integration — were built around the assumption that a newsroom owned what got published on a property. The portal’s reality was that other newsrooms owned the content; the portal owned the selection and the surfacing.
That changed the build problem at the root. Feed strategy across the eleven sibling properties, taxonomy normalization between papers whose tag conventions had drifted over years of independent operation, image-convention forgiveness when one paper’s featured-image dimensions did not match another’s, attribution-aware article templates that surfaced the source paper’s masthead alongside the canada.com chrome. The portal child theme absorbed editorial mismatches that the individual newsroom children did not have to think about. Same parent, completely different child-theme posture.
The domain authority bet
The canada.com domain itself was the architectural reason the portal existed in the form it did. A single-word .ca domain at the national level carries discovery and link-equity weight that no regional paper’s domain can match. The portal aggregated traffic to that domain on the assumption that the brand-and-discovery surface compounded over time in a way that justified the editorial overhead of running a no-newsroom property alongside ten newsroom properties. The platform decisions had to honour that bet — fast page loads, clean canonical URLs, syndication signals that did not confuse search engines about which paper actually produced each article.
Putting canada.com on WordPress VIP alongside the National Post in the 2011-2012 migration was part of the work that settled the question of whether WordPress could carry serious Canadian publishing infrastructure at all. The portal was the harder of the two to defend, because portal properties without their own editorial teams have an easier time looking like SEO content farms than newsroom properties do. The platform posture had to be unambiguously serious — Automattic’s VIP review, production engineering reviewed against the National Post’s standard, and a child theme that respected the editorial provenance of every piece it surfaced.
- The work: Aggregator child theme on the shared Postmedia parent; portal-specific feed, taxonomy, and attribution handling
- Architecture: Same parent as the eleven newsroom properties; structurally distinct child posture
- Client: Postmedia Network Inc. (canada.com)
- Period: 2011-2013
The bet was that one well-maintained parent theme could carry eleven editorially distinct properties — ten newsrooms and one portal — without fragmenting into eleven forks. It held. If you are running a network site today and watching maintenance cost balloon as each property drifts from a common base, this is the architectural pattern worth revisiting.
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.
