WordPress for newspapers: Toronto 2012
A WordCamp Toronto 2012 talk on the WordPress 102: Customizing WordPress track, walking through what it actually takes to build a newspaper site on WordPress and the predictable mistakes to avoid. Recording is on WordPress.tv; slides ("Newspapers with WordPress") are on SpeakerDeck.
Where and when
- Event: WordCamp Toronto 2012
- Date: September 29–30, 2012 (exact session day not confirmed)
- Track: WordPress 102: Customizing WordPress
- City: Toronto, Ontario, Canada
- Listed on the WordCamp schedule as: "Building a Newspaper Site with WordPress" (the WordPress.tv release uses the shorter title)
Watch the talk
The slide deck is published on SpeakerDeck under the title "Newspapers with WordPress, from WordCamp Toronto 2012".
The premise
From the WordPress.tv release:
"How do you build a newspaper with WordPress, what steps do you need to take and how you can avoid some common pitfalls."
The classes of pitfall the talk warned about
Reconstructed framework. The recording above captures the actual pitfalls discussed; this section organizes the well-documented categories of newsroom-on-WordPress risk that the talk's premise pointed toward. No specific publications are named.
Organisational pitfalls
- Editorial workflow that doesn't map cleanly to WordPress's draft → review → publish model.
- IT vs editorial control: who owns the production environment when an article is live and broken at 4pm.
- Training the newsroom: writers and editors need to be confident in the tool, not deferential to it.
- Defining a publishing cadence the platform can sustain (not just on a normal Tuesday, on election night).
Technical pitfalls
- Custom theme bloat: every desk wants a custom template, and the theme becomes unmaintainable.
- Plugin sprawl from quick fixes: "we just need this one plugin" five times over.
- Query performance under spike load: homepage caching strategy decides whether the site survives a viral story.
- Archive integrity: old URLs must keep resolving, or SEO and citations break across years of work.
- Image and media handling at newsroom scale: original capture, web variants, lazy loading, accessibility.
Cultural pitfalls
- Print habits carrying over: copy-paste from layout software introducing invisible character noise.
- Treating WordPress as a "blogging tool" when the operation needs CMS-grade governance.
- Multimedia handling: the team has to want to use photo and video well, not just have the tools.
Modern reflection (2026)
Retrospective interpretation, not direct recall.
Of the three classes of pitfall above, the organisational ones are the most persistent. Workflow alignment, editorial-vs-IT ownership, and newsroom training look almost identical in 2026 to how they looked in 2012: different tools, same misalignment. The technical pitfalls have largely transformed: the REST API and headless options give newsrooms more architectural flexibility, modern caching layers (object caches, edge CDNs, WP Engine's NGINX-based stack) make spike load far less scary than it was, and image handling has matured dramatically with WebP, AVIF, lazy loading, and built-in srcsets. The cultural pitfalls are improving slowly: print habits have aged out as digital-native journalists fill more of the newsroom, but the "blogging tool" framing still surfaces in pitches and procurement conversations.
The talk's underlying argument, that WordPress is real publishing infrastructure when treated as such, and that the tension between platform power and editorial accessibility is the actual challenge, has aged into one of the more durable claims in this speaking history. The same argument now applies beyond newsrooms: law firms, accounting practices, training organizations, and healthcare networks face exactly the same choice.
Related talks in this through-line
- WordCamp Montréal 2012: How to Run a Newspaper with WordPress: sister talk delivered six weeks earlier with a different abstract framing
Related work
- Sibling Toronto 2012 talk by the same speaker: Creating Your First Plugin, The Easy Way: WordCamp Toronto Developers 2012
- Working with the speaker: WordPress services · Get in touch