Skip to content
CUYCO

Phantomium

Phantomium's site was moving off Webflow into Next.js. I joined the build mid-flight to take it from a scaffold to something safe to deploy — full English, Dutch and German localisation, a draft gate for unfinished case studies, and a contrast pass that fixed genuinely invisible text.

Client
Phantomium
Year
2026
Built with
Next.jsnext-intlGSAPLenisLottie
Phantomium — A Next.js rebuild of a digital studio's brand site, replacing Webflow and adding three-language support.

The Brief

Phantomium is a digital product studio moving its brand site off Webflow onto Next.js. The design and initial scaffold were already in place. I joined to close the gap between a scaffold that renders and a site that can be put in front of clients in three markets.

The Challenge

The riskiest thing on the site was not a bug — it was the placeholder case-study copy. Invented narrative about real client work is the kind of thing that has to come off before launch, not after someone notices. Everything else was the ordinary work of making a half-built site trustworthy: text that was invisible in the light theme, missing localisation, and no way to keep unfinished pages out of production.

What We Built

  • Real case studies replacing fabricated ones — placeholder narrative removed and swapped for content-request stubs, so nothing on the site claims work that cannot be verified
  • A draft gate — unfinished case studies stay out of production until their content and client clearance actually land
  • Full en/nl/de localisation with next-intl, covering all three of the studio's markets rather than an English site with translated fragments
  • Light-theme and contrast fixes — including text that was rendering invisible against its own background
  • SEO and accessibility pass across the site
  • Motion layer — GSAP and Lenis for scroll behaviour, Lottie for brand animation

The Outcome

main builds clean and is safe to deploy. The fabricated case studies and the invisible-text bug are off it, and the site is waiting on client content rather than on engineering.

Tell me what you are trying to solve.

Thirty minutes on a call is usually enough to work out whether this is a two-week job, a two-month job, or something you should not build at all. You get a written scope and a fixed price before anything starts.

Taking on new work from August 2026 · Replies within one business day