Edmonton’s news cycle has its own gravity. The Legislature is here, so provincial politics lands harder on the homepage than it does in Calgary, and the reader expects the paper to carry the story. Two Alberta papers, adjacent markets, distinct editorial centres — and the architecture had to honour both.
The Edmonton Journal ran as its own child theme on the shared Postmedia parent, alongside the Calgary Herald‘s child. Same upstream code; different homepage discipline. The temptation when two papers in the same publisher serve adjacent markets is to over-share the homepage logic — let one front page configuration drive both, save some maintenance, ship faster. The better answer turned out to be sharing the chrome, the performance budget, and the publishing tools, but letting each paper’s editor configure the front page on their own rhythm. The reader can tell the difference. Provincial politics, civic affairs, arts and culture, energy reporting — the Journal’s mix is recognisably its own when the homepage doesn’t impose Calgary’s pacing on it.
In 2011-2012, when Postmedia moved its network of daily newspapers onto WordPress, the Edmonton Journal landed on WordPress VIP — 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 child-theme model is what made that scale: the parent earned the review, the eleven children inherited the production posture.
The child theme build for the Journal is the cleanest illustration in the network of the architectural principle: share infrastructure, hold editorial identity in the child.