Organogenesis was operating multiple marketing and brand sites on a legacy SSI-based stack that had reached operational and delivery limits. This healthcare digital platform modernization effort focused on creating a scalable, multi-brand marketing platform with unified analytics and CDP integration. The platform was difficult to scale, expensive to maintain, and incompatible with modern AWS-based cloud infrastructure requirements. As a result, content updates were slowed down, releases became risky, and cross-site tracking and analytics were fragmented.
PathToProject was engaged as an additional high-experienced technical vendor to accelerate modernization and provide a fast, pragmatic strategy for migration and future-proof delivery. A two-stage transformation approach was executed: first, legacy SSI sites were migrated into a modern Gulp-based static build system to quickly stabilize delivery and restore compatibility with existing AWS infrastructure. Next, the entire marketing stack was modernized again — migrated from Gulp to a Next.js and NX.dev monorepo platform, enabling unified development workflows, reusable components, and faster delivery of marketing changes.
In parallel, a global customer data platform layer was introduced based on GA4, GTM, and Looker Studio dashboards. User tracking was extended beyond default analytics, enabling structured measurement of UTM attribution (online + offline), video engagement, and webform activity down to the field level. This CDP and Next.js multi-brand platform project improved performance, reduced engineering overhead, and created a scalable foundation for long-term growth across multiple sites and brands.
Multiple marketing and brand sites were operating on a legacy SSI-based stack that had reached architectural and operational limits. This digital platform modernization healthcare case study began with a platform that had become difficult to scale, risky to change, and expensive to maintain. Modern development practices could not be applied consistently, and delivery speed was constrained by outdated build and deployment workflows.
Because each site was maintained independently, duplicated code and unique styling approaches were accumulated over time. UI changes were required to be repeated across multiple repositories, increasing delivery cost and introducing inconsistencies between brands. Component reuse could not be implemented in a predictable way, and shared patterns were maintained through manual synchronization, which increased technical debt with every release.
Release governance and operational stability were also impacted. Changes were difficult to validate automatically, and safe delivery practices such as consistent CI/CD, controlled approvals, predictable builds, and fast rollbacks were not available across all sites. As a result, deployment risk was elevated, incident response time increased, and release confidence depended heavily on manual checks and tribal knowledge.
Platform risks were amplified by the legacy architecture. SSI-driven composition introduced long-term maintainability concerns and made modernization difficult without full refactoring. Security-related risk was increased as well, since legacy patterns often required special configuration exceptions and added complexity to hardening infrastructure policies and headers (including CSP rules).
Performance expectations were hard to meet consistently. Optimization was limited by legacy rendering patterns, fragmented asset pipelines, and the absence of standardized performance monitoring. Lighthouse scores were unstable and often remained in the 50–60+ range, while global delivery latency was affected by the non-unified static delivery approach and inefficient CDN integration.
Customer data and analytics were fragmented across the platform. UTM attribution was not consistently captured across online and offline channels, video engagement was not measurable at the required level of detail, and webform conversions could not be analyzed per field or user journey step. Tracking logic differed from site to site, making unified reporting and reliable performance measurement difficult. Without centralized dashboards, product and marketing decisions were based on incomplete visibility.
A modernization strategy was required that could be executed quickly and safely without blocking business operations. The solution needed to fully remove SSI limitations, restore full AWS compatibility, consolidate development into a monorepo-based workflow, enforce consistent CI/CD governance, reduce release risk with automated validation and rollback-ready delivery, and establish a scalable foundation for performance and customer data tracking across all brands and sites.
A staged modernization replaced legacy SSI marketing sites with a scalable, AWS-compatible delivery platform and a unified development workflow. The solution consolidated multi-site engineering into an NX. dev monorepo with reusable UI components and standardized build, test, and release practices. In parallel, a shared GA4/GTM/Looker Studio analytics layer established consistent attribution and deeper funnel measurement across brands. Together, these capabilities reduced release risk, improved performance, and restored cross-site visibility for marketing operations.
Modernization was executed in phases to remove SSI constraints without interrupting ongoing marketing updates. The first stage stabilized delivery by moving legacy sites into a static build workflow compatible with existing AWS requirements. The second stage evolved the platform again into a Next.js + NX.dev monorepo for long-term maintainability. This approach reduced risk by avoiding a single “big bang” cutover while still delivering a clear end-state architecture.
All sites were brought under a single NX.dev monorepo to standardize tooling, dependencies, and development conventions. Shared libraries enabled teams to reuse components and utilities instead of duplicating work across separate repositories. Consistent linting, testing, and build targets improved predictability across brands. This consolidation directly supported faster delivery of cross-site changes and reduced long-term maintenance overhead.
The platform was modernized to Next.js to support performance-first rendering and a more maintainable front-end architecture. Routing, page composition, and shared layout patterns were standardized across sites to reduce implementation variance. The stack provided a clearer path for future enhancements without reintroducing legacy coupling. This mattered because marketing teams needed frequent updates with lower engineering risk and better SEO compatibility.
A shared UI layer was implemented using Tailwind CSS and shadcn/ui to enforce consistent styling and interaction patterns. Components were designed for reuse across multiple brands while still allowing controlled theming where needed. This reduced duplicated CSS and one-off UI implementations that previously accumulated across sites. The result was more consistent UX and faster implementation of new pages and campaigns.
Build and deployment workflows were standardized so releases could be validated and delivered consistently across sites. Automated checks reduced reliance on manual verification and tribal knowledge during deployments. The same release patterns made it easier to coordinate changes that affected multiple brands. This governance focus improved release confidence and reduced operational risk during frequent marketing updates.
Delivery was aligned to AWS infrastructure requirements to remove legacy hosting constraints and simplify operations. Static assets and site output were structured for predictable deployment and CDN distribution. This improved reliability and reduced the need for special-case infrastructure exceptions common in SSI-era patterns. The platform foundation supports scalable delivery as additional sites and brands are added.
CloudFront distribution was used to improve global delivery latency and ensure consistent caching behavior. Asset pipelines and caching rules were aligned with the modern build output to reduce unnecessary origin traffic. This helped stabilize performance across brands and geographies where legacy delivery patterns were inconsistent. Performance improvements also supported SEO and reduced friction for campaign landing pages.
A shared GA4 measurement approach standardized event naming, parameters, and data collection across all marketing properties. This eliminated site-by-site tracking drift that previously fragmented reporting and attribution. Consistent instrumentation made cross-site comparisons and rollups reliable. It mattered because marketing decisions depended on unified visibility rather than isolated site analytics.
Google Tag Manager was used to centralize tag deployment and reduce the need for code changes for routine tracking updates. A governed tag structure supported consistent rollout of pixels, events, and marketing integrations across brands. This improved operational agility while keeping tracking logic aligned to a single standard. It also reduced the risk of inconsistent or duplicated tags across sites.
Attribution was extended beyond default analytics to capture structured UTM data consistently across sites. The implementation supported scenarios where campaigns originate offline but convert online, preserving source context. Standardized capture and persistence improved the quality of downstream reporting. This was critical for measuring campaign effectiveness across channels and brands.
Video engagement tracking was implemented to measure meaningful interaction rather than relying on page views alone. Webform tracking was extended to field-level events to identify drop-offs and friction points within conversion flows. These signals enabled more precise funnel analysis and optimization opportunities. The added depth mattered because key conversions depended on forms and content engagement, not just traffic volume.
Looker Studio dashboards consolidated reporting into a shared view across brands and sites. Standardized data definitions ensured stakeholders were looking at consistent metrics and dimensions. Dashboards reduced manual reporting effort and improved the speed of insight generation. This supported ongoing optimization by making performance and attribution visible in one place.
Delivery followed a staged modernization plan to remove SSI constraints without disrupting ongoing marketing operations. As a Next. js monorepo multi-brand platform engineering effort, the team first stabilized the legacy sites by migrating them into a static build pipeline compatible with existing AWS delivery, then consolidated development into an NX. dev monorepo and evolved the stack to Next. js. In parallel, CI/CD governance and a shared UI system were introduced to reduce release risk and eliminate duplicated work across brands. A healthcare marketing platform CDP integration project layer (GA4/GTM/Looker analytics) was rolled out to standardize attribution and conversion measurement across all sites.
Legacy SSI composition was replaced with a Gulp-based static build to quickly remove the operational bottlenecks of the old stack. Templates, includes, and shared assets were restructured into a repeatable build pipeline that could be validated and deployed consistently. This phase mattered because it stabilized releases early and restored compatibility with AWS delivery requirements while longer-term modernization continued.
Multiple independent site codebases were consolidated into a single NX.dev workspace with shared tooling, libraries, and build targets. Common components and scripts were centralized to reduce duplication and make cross-site changes predictable. This consolidation was critical for scaling delivery across brands without repeating the same engineering work in multiple repositories.
The static build output and site architecture were migrated into a Next.js platform to enable modern rendering patterns, improved SEO controls, and a more maintainable frontend structure. Routes, page templates, and shared UI were refactored to align with a unified application framework rather than per-site build conventions. This phase mattered because it created a future-proof foundation for ongoing marketing iteration and performance improvements.
Build, test, and deployment workflows were standardized across sites using monorepo conventions to ensure consistent validation and predictable releases. Pipelines were structured to support repeatable builds, controlled promotion, and safer rollbacks when needed. This reduced reliance on manual checks and improved release confidence across a multi-site environment.
Inconsistent, site-specific styling was replaced with a shared Tailwind + ShadCN-based component approach to enforce reusable patterns. Components were implemented to be portable across brands while still allowing controlled theming and variation. This work mattered because it reduced UI drift, accelerated page builds, and lowered long-term maintenance cost.
A global tracking architecture was implemented using GA4 and GTM with Looker Studio dashboards to centralize reporting across sites. Tracking was extended beyond default pageview analytics to include structured UTM attribution (including offline alignment), video engagement, and webform activity down to field-level events. This provided consistent measurement and made cross-site performance and funnel analysis reliable for marketing and product teams.
Organogenesis modernized a legacy, SSI-based multi-site marketing stack into a scalable Next. js + NX. dev monorepo platform aligned with AWS delivery requirements. The program reduced release risk through standardized build and CI/CD practices, improved site performance and global delivery, and lowered ongoing engineering overhead through shared components and workflows. A unified GA4/GTM/Looker analytics layer also restored cross-site visibility, enabling consistent attribution and deeper conversion analysis across brands.
[01]The SSI-based architecture was fully removed, eliminating a major long-term maintainability and modernization blocker. This reduced operational fragility and the need for special-case infrastructure exceptions that complicated hardening and policy enforcement. The result was a platform that could evolve without repeated refactoring workarounds.
[02]Modern build and deployment workflows replaced inconsistent, manual release practices across independently maintained sites. Standardization improved validation and repeatability, reducing the likelihood of regressions and making rollbacks and incident response more predictable. Delivery confidence increased because releases no longer depended on tribal knowledge.
[03]Consolidation into an NX.dev monorepo enabled shared libraries, consistent styling patterns, and component reuse across brands. Teams could implement UI and behavior changes once and propagate them across sites, reducing duplicated effort and inconsistency. This lowered ongoing engineering overhead and improved maintainability as the site portfolio grows.
[04]Migrating to Next.js improved rendering and asset strategy, stabilizing performance across the marketing portfolio. Lighthouse scores increased to ~90+ from prior 50–60+ ranges, supporting better user experience and more reliable SEO outcomes. Performance improvements were achieved through a standardized, modern delivery approach rather than one-off tuning per site.
[05]Serverless AWS delivery with CloudFront enabled consistently fast global response times, with page loading in the ~20–50ms range. This reduced latency variability across regions and improved perceived speed for marketing visitors. The architecture also aligned the platform with modern AWS infrastructure requirements for long-term scalability.
[06]A global customer data platform layer using GA4, GTM, and Looker Studio consolidated tracking and reporting across all sites. Structured measurement expanded beyond default analytics to include UTM attribution (online and offline), video engagement, and webform activity down to the field level. This enabled more reliable cross-site comparisons and more actionable optimization decisions.
The project leveraged a combination of services focused on modernizing legacy CMS platforms, implementing headless architectures, and enhancing frontend delivery with Next. js. Drupal Legacy System Modernization and Drupal to Headless Migration services facilitated the transition from SSI-based legacy systems to a modern monorepo and Next. js platform, ensuring scalable and maintainable content delivery. Complementing this, Next. js Development and Component Libraries services supported the creation of reusable UI components and performant frontend architectures. Additionally, Customer Analytics Platforms and CDP Platform Architecture services enabled unified tracking, analytics, and customer data platform integration, aligning with the project's advanced tracking and analytics goals.
CDP Engineering Services
Accurate event instrumentation for CDP and analytics
Customer analytics platform implementation for governed metrics and behavioral analytics
CDP event pipeline architecture and identity foundations
CDP audience activation with governed delivery to channels
Enterprise CRM data synchronization and identity mapping
Customer profile and event schema engineering
Enterprise CMS modernization services for legacy Drupal estates
Decoupled Drupal + Next.js migration for modern frontend delivery
React SSR/ISR Next.js application engineering
Frontend component library development for scalable UI platforms
These case studies complement the current work by showcasing advanced digital platform modernization efforts within healthcare and marketing contexts. They emphasize scalable architectures, unified content delivery, and enhanced analytics integration, reinforcing themes of multi-site consolidation, performance optimization, and customer data platform implementation. Together, they provide insights into delivering consistent, secure, and efficient digital experiences across complex, multi-brand environments.
An advanced healthcare digital platform for LATAM was required to facilitate collaboration among radiology HCPs, distribute company knowledge, refine treatment methods, and streamline workflows. The solution needed secure medical website role-based access restrictions based on user role (HCP / non-HCP) and geographic region.
The platform enhanced collaboration, streamlined workflows, and empowered radiology professionals with advanced tools to gain insights and optimize patient care.
LSHTM required improvements to its existing higher education Drupal platform to better manage and distribute complex research data, including support for third-party integrations, Drupal performance optimization, and more reliable synchronization.
The solution improved data accessibility, streamlined research workflows, and enhanced system performance, enabling LSHTM to manage complex datasets more efficiently.
The Deprexis mental health digital platform on Drupal required stabilization, faster performance, and a secure ecommerce payment workflow to support online services. The solution needed to meet strict reliability and security expectations common for digital healthcare products.
The platform was stabilized, performance was improved, and secure checkout workflows were delivered with strong automated coverage to reduce operational and compliance risks.
These articles expand on the same kinds of decisions behind this project: how to modernize a multi-site frontend platform, govern tracking and CDP data, and keep delivery safe as the architecture evolves. Together they add context on monorepo-based implementation, enterprise Next. js choices, and the operating model needed to make analytics and activation reliable across brands.
