CardNexus

Problem

CardNexus had a clear challenge on their hands: a rebrand with no marketing site to show for it.

But this wasn’t a case of spinning up a standalone site. Their codebase was a monorepo housing the product, mobile apps, business logic, and static directories, all with their own conventions, colour systems, and shared UI. Any marketing presence had to live within that structure, not alongside it. And to top it off, it had to do so in two languages, with English and French audiences both needing a seamless experience.

They’d already tried bringing in a freelancer to tackle it. It didn’t work out.

So by the time I got involved, the stakes were higher. They needed someone who could navigate a complex, real-world codebase and deliver work that genuinely belonged there.

Solution

Rather than treating the marketing site as a separate concern, I worked within the grain of the existing codebase.

Inheriting the colour system, reusing shared UI components where appropriate, and building  Prismic into the stack in a way that felt native to the project rather than bolted on, including full multilingual support so content editors could manage both English and French content without it becoming a technical headache.

On the core pages, I built out the animations and interactions that make the difference for an audience like this. CardNexus sits in a space where the people visiting already have a feel for what polished, well-crafted products look like. The motion work made sure the site held up to that scrutiny and helped build trust from the first scroll.

Alongside the core pages, I built out a suite of  Prismic slices for the blog that let content editors do more than write; they could pull in products directly, making posts richer and giving readers a natural path toward exploring the catalogue.

The result was a marketing site that felt like it had always been part of the product, and a content system that gave the team genuine editorial flexibility without touching the codebase.