In 2011-2012, when Postmedia moved its network of daily newspapers onto WordPress, the Ottawa Citizen landed on WordPress VIP — at the time, one of a small handful of major Canadian news properties on the platform. WP VIP in that era was not a commodity purchase: onboarding required Automattic’s direct vetting and a codebase review before the first deploy. For a paper whose readership includes a meaningful chunk of Parliament Hill staff and federal public servants, that production posture was load-bearing in a way it isn’t at a general-readership daily.
The Citizen’s reader checks the references. A federal-policy beat reader is, often professionally, going to follow a link to a tabled document, an Order Paper item, or an Auditor General report — and if that link is dead, or rewritten, or pointed at a stale URL, the trust hit lands harder than it would on a civic story. VIP-grade SLAs and the production discipline that came with them mattered for exactly this reason.
The customization work on the Citizen reflected the same realities. The Citizen ran as its own child theme on the shared Postmedia parent; the parent carried performance and infrastructure across the network, and the Citizen’s child carried the editorial weight that a federal-politics front page demands. Section landings for federal politics, public service, and national affairs needed real prominence in the homepage and navigation logic. CMS and theme decisions around quoted material, document links, and inline source attribution carried more weight here than on regional civic pages.
The platform migration on this paper is one I still cite when a public-sector or policy-adjacent client asks why the platform choice matters before the design choice does. Readers checking references is the use case that decides it.