Organogenesis /

[The Challenge]

Multiple marketing and brand sites were operating on a legacy SSI-based stack that had reached architectural and operational limits. The platform 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.