One of the underappreciated parts of building for a network like Postmedia is what happens at the smaller papers. The Regina Leader-Post has been the dominant English daily in southern Saskatchewan since 1883, and it does not have the traffic of the National Post or the section weight of the Vancouver Sun. It still has to feel like a serious paper of record for its market, on the same shared WordPress® platform as the network’s flagships.
Lean newsroom, serious platform
The architecture made that possible. The Leader-Post ran as its own child theme on the shared Postmedia parent that carried the eleven properties of the network. The parent carried performance, infrastructure, and platform integrations identical to those running on the flagship papers. The Leader-Post’s child carried the editorial defaults that suited a smaller newsroom. Fewer hands on the homepage means the CMS and theme have to do more of the work an editor would do at a larger paper, and they have to do it in a way that does not look automated.
The child theme build leaned on defaults that produced a good homepage when nobody touched them, rather than offering a long admin form that nobody had time to fill in correctly. That is a different design philosophy than the one a flagship paper’s child theme operates under. The National Post’s child theme could afford to expose more editorial controls because there were more editors with time to use them. The Leader-Post’s child theme could not afford that, because the next sensible homepage configuration had to come from the system when the human resources were not there to produce it.
Defaults-first CMS design
That is the deliverable on a lean newsroom: the absence of decisions, not the presence of options. A senior-engineer instinct on a CMS project is to give the editor more controls, more knobs, more configurability. That instinct is the wrong one here. Better defaults beat more knobs, every time, when the editorial team does not have the bandwidth to make the per-day decisions the knobs assume. The Leader-Post’s child theme is one of the cleanest examples of that principle in the Postmedia network — the homepage looks competent and recognisably the Leader-Post’s even on the days when no editor has touched the configuration since the morning.
The 2011-2012 Postmedia migration onto WordPress VIP gave the Leader-Post the same production-grade platform as the flagships — same parent theme, same Automattic VIP review at the parent level, same engineering posture under the hood. That was a deliberate publisher decision, and the shared-parent architecture is what kept it economical to extend the flagship-tier platform to the smaller papers without separately justifying the cost for each one. A smaller-market paper deserves the same infrastructure quality as the flagship; the architecture pattern is what makes that financially honest.
- The work: Regina Leader-Post child theme on the shared Postmedia parent; defaults-first homepage and editorial-ergonomics work tuned for a lean-newsroom configuration
- Architecture: Shared parent with the National Post and the rest of the Postmedia network
- Client: Postmedia Network Inc. (Regina Leader-Post)
- Period: 2011-2012
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.