Case study06 / 12

Cray Networks Rebrand

A design-engineering rebrand of a 20-year-old Central Texas IT shop, built around a live OKLCH theming engine and a Base UI design system.

Year
2026
Cray Networks Rebrand
5 images
View gallery

Overview

The Cray Networks rebrand modernizes the brand of a real 20-year-old IT support business serving Central Texas while doubling as a senior-level design-system demonstration. The build keeps the company's existing blue-and-white identity but finally systematizes it: a canonical OKLCH token model drives every color, and a live theming engine lets the entire site re-skin in real time without a single React re-render. It is a full React Router framework-mode app with SSR, a Base UI component library, a variable-font typography lab, and a hand-coded SVG logo built from network nodes. An interactive showcase walks through the design rationale, including an honest before-and-after slider against the actual 2003 site. The result argues for design-system competence by proving it in the product itself rather than claiming it.

What I learned

Building the theming engine pushed me deep into the CSS cascade and the OKLCH color space. Authoring tokens as composable lightness, chroma, and hue channels meant I could override accent color, density, and radius by setting inline CSS variables on the html element, letting them outrank the root scope and re-theme the page instantly with no component re-render. I worked out SSR-safe theme persistence with cookies to avoid a flash of unstyled content, plus Zod-validated shareable theme query parameters. The variable-font work taught me to drive real wght and opsz axes for genuine optical sizing rather than faking type scales. Pairing Base UI primitives with Class Variance Authority and Tailwind v4's @theme inline gave me a clean way to keep utility classes overridable while a single token file stayed the source of truth and prevented drift.

Why it matters

The rebrand gives a 20 year old Central Texas IT company a presence that finally matches its reputation, without asking its customers to relearn the brand: the blue and white identity they already recognize, systematized instead of replaced. Every color, radius, and density value resolves from one token file, so new pages and future campaigns stay on brand without a redesign, and the next brand change is a variable edit rather than another ground up rebuild. The before and after slider against the actual 2003 site makes the argument to their own prospects: same company, same trust, a website that no longer costs them the first impression.

Screens

04 images, select to enlarge
Next projectVirtruvBrand identity and a custom site for a cybersecurity firm, built so the owner updates his own content instead of filing a ticket.

Hiring a senior frontend engineer?

I'm looking for my next role on a product team, building design systems and AI tooling. The resume has the details, and my inbox is open.