Inside BlackBerry for Business was the B2B-facing voice in BlackBerry®’s WordPress® VIP estate, the surface that spoke to enterprise mobility buyers and to the channel partners and IT decision-makers whose budgets they fed into. From an hour up the QEW from BlackBerry’s Waterloo headquarters, I worked on the theme that powered it from the 2011 VIP migration through the 2013 unified-theme rebuild.
The B2B voice on a consumer-known brand
bizblog.blackberry.com carried business-audience content: enterprise mobility, BES updates, channel-partner programs, investor-relations-adjacent stories. The editorial challenge is harder than the consumer-facing equivalent because the reader arrives with an expectation of BlackBerry as a consumer brand and has to be moved into the business-decision frame within a paragraph. Editorial cadence on bizblog skewed steadier and longer-form than the consumer-facing Inside blog, and the article template had to give that longer-form reading room without the marketing-flourishes that worked on the consumer hub.
Enterprise mobility buyers read differently than consumers
The B2B reader scrolls more slowly. They check the byline. They follow links to spec sheets and to BES technical documentation. They forward articles internally to procurement colleagues. None of those behaviours show up on a consumer blog’s analytics. They all show up here. The theme decisions had to honour that: readable inline links, byline prominence, social-share metadata tuned for LinkedIn rather than for Twitter, article-page reading patterns that survived being opened in a tab forty-five minutes after the share was clicked.
By 2013 the unified-theme rebuild had brought the four blogs onto a shared parent codebase, and the business child was where the enterprise-buyer reading patterns got codified into template decisions. Per-property identity: the logo-header-biz.gif wordmark, the teal accent, the favicon-biz.ico, was layered onto the shared theme through colour classes and asset variants. The deploy slug was still vip/rimbizblog years after the corporate rename; VIP slug history doesn’t migrate cleanly once a property’s article URLs are out in the world.
Feedburner, IR-adjacency, and the email-subscription discipline
Subscribers fed in via a Feedburner pipeline (InsideBlackberryForBusinessBlog) that long outlived its parent corporate trajectory. The enterprise-mobility-buyer audience subscribes by email, follows the RSS feed (RSS), and treats the blog as one of the channels they monitor alongside the financial disclosures and the analyst briefings. The platform underneath had to be predictable enough that the subscription chain worked across every post, every cycle. WordPress VIP’s reliability profile mattered more here than the design flourishes did. bizblog.blackberry.com held on longer than the others; Wayback shows a clean 200 response as late as January 2020, roughly a year after Inside, Developer, and Help went 301.
- The work: B2B-audience child theme; reading-pattern decisions tuned to enterprise mobility buyers and channel partners; Feedburner-era subscription discipline
- Platform: WordPress VIP; 2011 self-hosted migration; 2013 unified-theme rebuild on shared parent codebase
- Client: BlackBerry Limited (B2B division), Waterloo, Ontario
- Period: 2011-2014 (property continued running on the unified theme until 2020)
Sibling property: the Inside BlackBerry hub that the bizblog sat under.
The B2B-blog lesson that travels: the enterprise reader is doing different work on the page than the consumer reader, and the theme that serves both audiences with the same template will always be slightly wrong for both. Per-audience child themes inside a shared parent are how you get the brand consistency without forcing the audiences into a compromise.