Copa City & Triple Espresso

The Predicament

Triple Espresso arrived with a delicate request: they needed a custodian for their digital presence. The task was to inherit and refine the complex architectures of the Copa City and Triple Espresso platforms—built on Next.js and Storyblok.

On the surface, it appeared to be a standard development hand-over. Beneath, it was a high-stakes performance. With a ticking clock, ten localized versions to synchronize, and the looming surge of global campaign traffic, the project demanded more than just a developer. It required someone who could navigate a volatile network infrastructure without breaking the aesthetic or functional integrity of the brand. It was never just a "website"; it was a global operation where failure was not an option.

The Orchestration

I began by re-weaving the integration between Storyblok and the core application. My goal was to ensure that ten distinct languages could coexist with surgical fluidity, adhering to the highest technical standards.

To preserve the project’s resources, I silently migrated the entire asset infrastructure to Cloudflare—a move of quiet efficiency that shielded the budget from the weight of massive global traffic. I then expanded the internal logic of the CMS, empowering the team to manipulate stadiums, clubs, and game modes with effortless precision. Finally, I introduced a bespoke lead-capture system, a subtle but powerful gateway that allowed Triple Espresso to curate their Closed Beta audience directly through the site. I didn't just maintain the structure; I made it responsive to their every ambition.

The Outcome

• Instantaneous Grace: Static generation that delivers performance as sharp as a tailored suit.

• The Triple Alliance: A flawless, resilient ecosystem bridging Vercel, Storyblok, and Cloudflare.

• Global Footprint: Over 500,000 global impressions orchestrated since the baton was passed.

• The Selection: A curated list of over 30,000 candidates secured for the Closed Beta.