Inside BlackBerry was the umbrella publication for BlackBerry®’s public blog network, the front door above the Business, Developer, and Help blogs that ran in parallel underneath. From a desk an hour up the QEW from BlackBerry’s Waterloo headquarters, I worked on the WordPress® VIP theme that powered all four properties from a single codebase. The hub was the piece of the estate I held longest — both the 2011 VIP migration and the 2013 unified-theme rebuild ran through this template.
Archived capture (June 2016, mid-life): view blogs.blackberry.com on the Wayback Machine. Earliest WP VIP era capture: April 2011 capture on the Wayback Machine.
Inside BlackBerry as the front door
blogs.blackberry.com routed readers across four sub-properties — Inside, Business, Developer, and Help — each with its own audience but a shared editorial voice. The hub carried headline announcements, product launches, and cross-cutting stories; sub-blogs carried the depth. Cross-blog navigation lived in a top strip on every page, colour-coded per surface, so a reader who arrived on a help-blog troubleshooting post could see at a glance that the corporate hub and the developer blog were one click away in the same publishing family.
Cross-blog navigation as a publishing surface
The umbrella ran under the parent vip/blackberry-blogs slug after October 2013, while each child sat under its own short-form variant. The cross-blog navigation strip itself was the load-bearing design decision on the hub — it had to be readable on a developer scrolling SDK release notes and on an enterprise buyer scrolling channel-partner program updates without either reader feeling like they had wandered into the other audience’s territory. The colour-coding handled the wayfinding; the consistent strip position handled the spatial-memory.
In 2011, the four BlackBerry blogs migrated off self-hosted WordPress onto WordPress.com VIP, each running its own custom theme — vip/rimblogs, vip/rimbizblog, vip/rimdevblog, vip/rimhelpblog. The rim prefix is a fingerprint of the pre-rebrand corporate identity; the WordPress.com backend subdomains kept the RIM naming through the entire VIP era, even after the January 2013 corporate rebrand to BlackBerry.
In 2013 the four custom themes were retired and replaced with a single mobile-responsive codebase, vip/blackberry-blogs, that powered all four properties from one source. Per-blog identity was handled through colour classes, logo variants, and per-surface favicons rather than separate theme directories. The unified theme deployed in October 2013 and ran until the network was decommissioned in March 2019.
- The work: Theme development across all four properties (2011 and 2013 engagements); umbrella + child theme architecture; cross-blog navigation surface
- Platform: WordPress VIP; mandatory code review, performance constraints, disallowed-PHP discipline
- Client: BlackBerry Limited, Waterloo, Ontario (parent corporation: BlackBerry Limited on Wikipedia (opens in new tab))
- Period: 2011-2014
What the hub had to absorb that the children didn’t
An umbrella publication on a multi-property estate carries one job the children never have to: hold the brand-level coherence that lets four distinct audiences feel they are in the same publishing family. The Business reader, the Developer reader, the Help reader, and the press reader who arrived at Inside BlackBerry through a major product announcement all needed the property to feel like one organisation speaking, even though four different editorial teams were writing the content underneath. That coherence work happens in the hub theme — in the global navigation, in the cross-property recommendation logic, in the consistent typographic voice — and it does not happen anywhere else on the estate.
The other three properties in the estate each carry their own portfolio entry: Inside BlackBerry for Business, the BlackBerry Developer Blog, and the BlackBerry Help Blog. blogs.blackberry.com now redirects to a Next.js property at blackberry.com; the WP VIP era captures are preserved on the Internet Archive.
The hub-and-spoke pattern from this work informs how I think about every multi-audience publication estate I encounter now. The hub does the brand work, the children do the audience work, the shared parent code makes both economical to maintain — and the cross-property navigation is the architectural piece that makes the estate read as one organisation rather than four parallel publications that happen to share a domain.
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.