DOSE.ca: bespoke entertainment property on the Postmedia VIP platform, 2011-2012

Christopher Ross

4 min read
DOSE.ca: Publishers & Media, 2011-2012

DOSE.ca was Postmedia’s digital-native entertainment property: no print edition, no broadsheet parent to inherit a template from. It was an editorial brand built for the web from the start, with a publishing rhythm set by pop culture and entertainment news cycles rather than by a morning print deadline. At its peak it had over 85,000 Facebook fans (a meaningful number in the early 2010s) and daily readership in the hundreds of thousands.

Not built off the dailies’ theme

DOSE was not a Postmedia newspaper-blog theme. The Postmedia WordPress® VIP platform ran a standardized theme family for the daily-paper blog networks, with sensible defaults, consistent chrome, and a content model that suited the news desk. That family was the right answer for the dailies. It was the wrong answer for an entertainment magazine whose readers arrived for the celebrity-news lead, the year-end list, the album-drop reaction, and the late-night-show recap.

Built for the entertainment-news cycle

A bespoke WordPress VIP property with its own framework on top of the platform: its own theme, its own content types for the long-running editorial series the brand ran, and a publishing model built around community and conversation rather than around the news desk. The home page led with what the editors had picked for the day, not with what the wire had pushed last. Social-share affordances were built into the article layout rather than bolted onto a sidebar. Reader-submitted galleries and contests were first-class objects with their own backend workflows, because that kind of engagement was the brand’s actual conversion engine.

Where DOSE broke from the network pattern Two parallel publishing workflows on the same Postmedia WordPress VIP platform, compared across four steps: what sets the agenda, the content model, how the page renders, and how readers engage. The top track is the standard daily-network workflow, its stations outlined in navy. The bottom track is DOSE.ca’s bespoke workflow, each station marked with a copper bar to show it departed from the standard pattern: editors pick the lead instead of the wire, series and community content types replace the news-desk model, a bespoke theme carries social inside the article instead of a sidebar bolt-on, and reader galleries and contests are first-class objects instead of generic comments. A BESPOKE PROPERTY Where DOSE broke from the network pattern Both rode the same WordPress VIP platform. Copper marks where DOSE diverged. SETS THE AGENDA CONTENT MODEL HOW IT RENDERS HOW READERS ENGAGE STANDARD NETWORK DOSE.CA Wire setsthe lead News-deskcontent model Shared parenttheme Sidebar socialbolt-on Editors pickthe lead Series +communitycontent types Bespoke theme,social in-article Galleries &contests asfirst-class Copper marks where DOSE departed from the standard pattern
I put the two publishing workflows side by side so you can see that DOSE ran the same VIP platform as the daily-paper blogs but broke from the standard pattern at every step, from who picked the lead to how readers engaged.

Where DOSE wound down

DOSE.ca eventually wound down with the broader Postmedia digital-native consolidation later in the 2010s. The bespoke-framework-on-top-of-shared-platform pattern, however, became one of the standard ways large media groups now ship distinct brand sites: a per-brand theme layer riding on top of the shared infrastructure and security baseline of the chain, with the brand keeping the parts that make it a brand and the chain keeping the parts that make it operationally efficient.

  • Platform: WordPress VIP, custom framework
  • The build: Bespoke digital-native entertainment property on Postmedia infrastructure, with community-first content types and social-share affordances built into the editorial flow
  • Client: Postmedia Network: DOSE.ca
  • Period: 2011–2012

Where this pattern transfers

Any digital-native brand sitting inside a larger media or commerce group has a version of this job. A lifestyle vertical inside a national publisher, an entertainment site inside a broadcaster, a community-driven sub-brand inside a chain that mostly publishes hard news. In all of them, the temptation is to put the new property on the standard chain theme and call that “efficient,” and the cost of that decision shows up six months in as a brand that reads exactly like every other property in the group and never builds an audience of its own.

This work was part of the broader Postmedia WordPress VIP migration: one parent theme, eleven distinct child themes across Canada’s major daily newspapers. The full architectural story, including the parent-child seam and the platform decisions that made the network work, is in the Postmedia WordPress VIP migration case study.

Working through something on your own site? Get in touch →