When Penske Media Corporation acquired Rolling Stone, the brand’s website was running on a legacy PostgreSQL system that had nothing in common with the rest of PMC’s portfolio. Every new feature had to be built twice, every security patch applied separately, every editorial workflow was its own island.
PMC didn’t rebuild Rolling Stone from scratch. Working with an Enterprise WordPress partner, the brand was migrated onto the same platform already powering Variety, Women’s Wear Daily, Deadline, and 15+ other brands. The shared foundation meant Rolling Stone inherited years of infrastructure investment on day one, while keeping its own editorial voice and identity intact.
This is the 80/20 rule in practice: 80% shared code across the portfolio, 20% brand-specific customization. It’s a simple split that determines whether your platform scales with the business or slows it down.
The problem with building every brand from scratch
Most publishers don’t set out to create complexity, it accumulates. One acquisition brings a Drupal site, another brings a custom CMS, a third brings WordPress, but a version configured so differently it might as well be a separate platform.
Before long:
- The same feature exists in five different implementations
- Security updates become a project, not a routine task
- A new ad integration takes months instead of days
- Editorial teams across brands use completely different tools and workflows, making it nearly impossible to share talent or best practices
And those problems compound. Duplicated effort drains engineering time. Editorial inconsistency across brands makes it harder to maintain quality or move people between teams. And the strategic blindness that comes from siloed data and disconnected systems means leadership is making decisions without a clear picture of how the portfolio is actually performing. Money and time that could go toward audience growth or new revenue streams goes toward keeping the lights on instead.
What 80% shared actually looks like
The shared layer doesn’t mean every site looks the same. It covers the infrastructure that no one sees, but everyone depends on:
- Core architecture and performance optimization
- Security and update management
- Integrations (ad tech, analytics, CRM)
- Audience engagement tools
- Reusable editorial components
- Governance processes
News Corp Australia runs 100+ sites on this model, including The Australian, News.com.au, and Vogue Australia. When 90 of their brands were migrated onto a shared Enterprise WordPress platform, page layout creation became 40x faster. What used to take a day or more took minutes.
iOne Digital took the shared approach even further. A single common theme powers over 70 branded platforms, which meant:
- 60 live sites deployed in three weeks once the foundation was stable
- Tripled content creation output
- Grew traffic by 82%
Those results didn’t come from building 70 separate sites. They came from building one platform well and letting every brand benefit from it.
There’s an editorial dimension to this too. Journalists are not technologists, and they shouldn’t have to be. When the shared foundation handles performance, security, and integrations centrally, editorial teams stop wrestling with the CMS and get back to what they’re actually there to do.
“The efficiency gain isn’t about making journalists faster, it’s about removing the things that aren’t journalism.”
What the 20% protects
The brand-specific layer is what keeps each site distinct. Each site keeps its own:
- Visual identity and design
- Editorial voice and content strategy
- Audience engagement tools
- Custom features that reflect its market position
A business publisher and a lifestyle publisher within the same portfolio have different reader expectations and ways of making money. The 20% gives them room to operate independently where it matters, while the shared engine underneath makes both of them faster and more reliable.
This is where most portfolio strategies go wrong. Either the shared layer is too rigid and brands feel constrained, or it’s too loose and you’re back to maintaining separate platforms. The 80/20 split is a guideline, not a rule. The ratio varies across portfolios. PMC sits at roughly 80% shared; iOne runs closer to 100%. The right split depends on how distinct your brands are and where your biggest operational bottlenecks sit.
This matters most during acquisitions
When a publisher acquires a new brand, three questions come up fast:
- How quickly can you assimilate the platform?
- How soon can you monetize the audience?
- How much will the integration cost?
On a shared Enterprise WordPress platform, a newly acquired brand plugs into proven infrastructure and inherits security, performance, editorial tools, and integrations from day one. When News Corp Australia brought Sky News Australia onto their shared platform, the migration was completed in three weeks with no redesign needed. The team could focus on what makes Sky News distinct as a brand rather than rebuilding the basics from scratch.
Without a shared foundation, the process routinely stretches to six months or more before a new brand is stable and generating revenue. The 80/20 approach compresses that significantly.
How to know if your portfolio needs this
A few signals that your current setup is costing more than it should:
- The same bug gets fixed in multiple places
- Feature rollouts take months because each site needs its own implementation
- Editorial teams across brands have completely different tools, making it hard to move people between teams
- You can’t sell advertising across the network because the sites don’t share the infrastructure to support it
- User data stays siloed by brand, so you have no visibility into how readers behave across your portfolio
- A multi-brand paywall or single sign-on is on the roadmap but keeps getting pushed because the platform can’t support it
- Hosting and maintenance costs scale linearly with every new brand instead of flattening over time
- Acquisitions take 6+ months to assimilate into your tech stack
Key Takeaways
- Shared infrastructure is a business decision, not just a technical one. The right platform architecture determines how fast and efficiently your portfolio can grow.
- The 80/20 split is a starting point, not a fixed rule. The right ratio depends on how distinct your brands are and where your operational bottlenecks sit.
- Enterprise WordPress is proven at scale. Publishers running dozens or hundreds of brands have used it to cut integration time, accelerate content production, and reduce per-site costs significantly.
