Skip to main content
Okhare Paul — Portfolio©2026
000
Back

Case study · 07 / 12

Datum

One codebase, rebuilt into a different brand

Fig. 07 — DatumSame engine, new identity: ruled, measured and scrubbed by the scroll.
About the project

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.

Main features

What it does

  1. 01Inspects the hero image through a lens that shows the drawing under the render
  2. 02Replaces the browser's scrollbar with a ruler, a needle and a three-digit readout
  3. 03Pins the work section and wipes through each project as you scroll
  4. 04Runs a band of giant type that surges and reverses with scroll speed
  5. 05Drives its numbers and 40-tick meters straight from scroll position
  6. 06Brackets whatever the cursor can click with a following reticle
  7. 07Takes enquiries as numbered work orders
Approach

How it was solved

  1. 01Moved the whole brand into design tokens, then wrote searches that must come back empty to prove no old value survives
  2. 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
  3. 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
  4. 04Flipped the gauge's ink between light and dark by reading the section beneath it
  5. 05Built the pinned stage from one sticky frame and scroll-linked clip-paths, with the same projects listed plainly for screen readers
  6. 06Made the animated grid from a fixed number sequence, so the server and the browser draw the identical pattern
  7. 07Gave the lens a simple toggle for touch, keyboard and reduced-motion visitors, so nobody is locked out of the idea
  8. 08Drew the placeholder artwork in code and rendered it to files with a script, so it can be rebuilt at any time
  9. 09Checked every colour pairing for contrast as part of the guide, with bone on graphite at 15.72 to 1
Technologies

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

The case study is the how. The site is the proof.

Next project · 08 / 12Jerrie Bones