Case study · 07 / 12
Datum
One codebase, rebuilt into a different brand
- Year
- 2026
- Focus
- TypeScript
- Status
- Live
A complete rebrand carried out in code: an existing studio site turned into Datum, an engineering-led product studio, with a new name, voice, type, colour and motion, following a 31-page brand guide.
Most rebrands change a logo and a palette. This one had to change how the site behaves. Datum's idea is measurement: set a reference, then build to it. So everything soft in the old site went. Springs became precise, instrument-like movement. The hero's ink trail became a hard-edged inspection lens with a live coordinate readout. The scrollbar became a ruler with a needle. The work section became a pinned stage that the scroll wipes through, one project at a time. I treated it as an engineering job: tokens first, then checks that prove every retired colour and name is gone from the code, then the new pieces, each with a plain fallback for touch, keyboard and reduced motion.
What it does
- 01Inspects the hero image through a lens that shows the drawing under the render
- 02Replaces the browser's scrollbar with a ruler, a needle and a three-digit readout
- 03Pins the work section and wipes through each project as you scroll
- 04Runs a band of giant type that surges and reverses with scroll speed
- 05Drives its numbers and 40-tick meters straight from scroll position
- 06Brackets whatever the cursor can click with a following reticle
- 07Takes enquiries as numbered work orders
How it was solved
- 01Moved the whole brand into design tokens, then wrote searches that must come back empty to prove no old value survives
- 02Replaced every spring with two timed curves kept in one motion file, so the site moves like an instrument and no component invents its own timing
- 03Wrote scroll-linked values straight to the page and let React re-render only when the section changes, which keeps the gauge at full frame rate
- 04Flipped the gauge's ink between light and dark by reading the section beneath it
- 05Built the pinned stage from one sticky frame and scroll-linked clip-paths, with the same projects listed plainly for screen readers
- 06Made the animated grid from a fixed number sequence, so the server and the browser draw the identical pattern
- 07Gave the lens a simple toggle for touch, keyboard and reduced-motion visitors, so nobody is locked out of the idea
- 08Drew the placeholder artwork in code and rendered it to files with a script, so it can be rebuilt at any time
- 09Checked every colour pairing for contrast as part of the guide, with bone on graphite at 15.72 to 1
Stack
- Languages
- TypeScriptCSSHTML
- Front-end
- Next.js 16 (App Router)React 19TurbopackServer Actions
- Motion and graphics
- MotionLenisCanvas 2DSVGCSS clip-path
- Styling
- Tailwind CSS v4Design tokensnext/font (Geist, Geist Mono, Kinematical)
- Art pipeline
- Node.js scriptsPlaywrightSVG to JPEG rendering
- Tools
- ESLintGitGitHub
- #typescript
- #nextjs
- #rebrand
- #design-tokens
- #motion
- #accessibility
The case study is the how. The site is the proof.