Evianchezvous

Full rebuild of evianchezvous, Evian's home water delivery site (Paris / Île-de-France): migration from a monolithic Magento 1 to headless Magento 2 with a React + GraphQL front-end. Front-end tech lead for 2 years, from scoping to production.

The project meant doing everything at once: migrating Magento 1 → 2, pulling the front out of the monolith into a React app, rethinking checkout and the customer account, and porting the subscription logic (recurring water delivery) that Magento doesn't ship with. With SSR running underneath to keep search rankings, and performance that had to beat the V1 from day one.

• React front-end built from scratch across the full e-commerce tunnel: cart, checkout, account, subscriptions, postal-code-based delivery slots — all the business logic moved to JS.
• Custom GraphQL layer on top of Magento 2: native M2 doesn't cover everything, lots of custom resolvers and extended schemas to serve the front without unnecessary round-trips.
• Subscription module + recurring payments + one-shot orders, wired into per-zone delivery constraints — something Magento can't do alone, coded custom on both sides.

Magento 2 on the back for the e-commerce stack (catalog, orders, customers, payments), with a custom-extended GraphQL layer. React + Apollo Client + SSR on the front for performance and SEO — pulling out of a Magento monolith without losing indexation is the whole headless bet. React also enables a real mobile experience — components designed for touch and native-feeling transitions — that Magento 1 couldn't deliver. M1 → M2 data migration (products, customers, orders, active subscriptions) without breaking history.

Still live years after delivery. Performance and conversion rate up vs the Magento 1 V1. On a personal level, this is my first React e-commerce site and my first front-end tech lead role over 2 years. The main lesson: moving a Magento to headless means rebuilding in React things the V1 used to give for free — cart, sessions, customer flows. A lot of plumbing to lay back down to gain on UX and perf.