The Challenge
At Brunello, Inc., we worked with a healthcare consumer engagement and technology company that creates digital experiences for major health plans and healthcare organizations.
Its technology supports member acquisition, onboarding, benefits activation, preventive care, and retention across Medicare, Medicaid, and commercial audiences. The platform helps members understand their benefits, access healthcare services, and navigate complex health information.
The company maintained a centralized content platform containing health articles, recipes, benefits information, and other educational resources. That content powered a network of branded microsites, APIs, and content feeds.
Each microsite needed to reflect the identity and requirements of a specific healthcare organization while continuing to use the same underlying platform. Building every site as a separate product would have created duplicated code, inconsistent functionality, and an increasingly difficult maintenance burden.
Our challenge was to create a reusable theming architecture that could be white-labeled and configured for different healthcare clients without making every site look or behave the same.
A Shared Theming Architecture
Brunello architected and developed the shared Drupal theming layer used across approximately 10–20 healthcare microsites.
The system allowed each site to use its own colors, typography, branding, navigation, layouts, and content configuration while sharing a common foundation of templates, components, and functionality.
This created a clear separation between the parts of the platform that were shared and the parts that could be customized for an individual healthcare client.
Shared functionality and improvements could be developed once and applied across the network. At the same time, each organization could maintain a distinct experience designed around its members, programs, and brand requirements.
Supporting White-Label Microsites
We designed the theming system to support repeatable white-label implementations.
Rather than copying an existing theme and modifying it for every launch, we could configure a new microsite from a defined set of brand, layout, and content requirements.
The architecture supported:
- Client-specific colors, typography, logos, and visual styles
- Reusable page templates and content components
- Configurable navigation and page layouts
- Centralized content delivered through APIs and feeds
- Shared responsive and accessibility behavior
- Custom extensions for specialized client requirements
This reduced duplicated development while keeping the base system flexible enough to support different audiences and use cases.
Programmatic Site Creation
We created processes for generating and configuring microsites programmatically.
These tools automated much of the repetitive setup involved in launching a new site, including theme configuration, site structure, and implementation details.
This gave Brunello and the client team a more consistent process for moving from requirements to a working microsite. It also reduced the risk of individual implementations drifting away from the shared platform architecture.
A relatively small development team could support a broad network of enterprise healthcare sites without maintaining a separate codebase for every client.
Content Platform Integration
The microsites consumed content from a centralized Drupal platform through APIs and structured feeds.
Brunello helped design the API integration and content structure used to package and distribute articles, recipes, benefits information, and related content.
Editorial teams could create and manage content from a central control point, then distribute selected materials to individual microsites based on each client’s audience, program, and content strategy.
This allowed the company to maintain consistent editorial quality without recreating the same content separately for every healthcare organization.
Flexible and Custom Experiences
The shared architecture covered the majority of microsite requirements, but it also needed to support clients whose needs extended beyond the standard templates.
For these projects, we developed custom Drupal themes and incorporated React components alongside the existing theming layer.
These implementations provided more interactive and application-like experiences while continuing to use the same centralized content platform and data structure.
This allowed the company to offer both repeatable white-label microsites and highly customized digital experiences without maintaining entirely separate platforms.
Supporting Content Operations
The platform included more than public-facing microsites. It also provided tools for content creation, editorial planning, reporting, workflows, project tracking, and content lineups.
Brunello designed and developed administrative interfaces to make these tools easier for internal teams to use.
The architecture needed to support both sides of the platform: the member-facing experience and the operational workflows required to create, organize, approve, and distribute content at enterprise scale.
The Result
The resulting platform gives the company a scalable way to deliver branded healthcare content across a network of enterprise client microsites.
A centralized content system supports editorial creation and distribution. The shared theming architecture gives individual healthcare organizations control over their visual identity and presentation. And programmatic deployment processes reduce the effort required to launch and maintain new sites.
The system allows Brunello and the client team to support many distinct healthcare experiences without treating each microsite as an entirely separate product.
As one client collaborator described the partnership:
Kyle was a thoughtful and reliable partner who understood both the technical and operational constraints of enterprise delivery.