Skip to content
Design systems · Motion · Engineering

Three versions of one website

How the EXORDIC website went from correct but anonymous, through a louder second attempt, to an identity built around one sculpted object.

Published
Reading time
4 min

A studio website is an odd brief. It has to show what you can do, but most of what it can say about you is still to be written. This site went through three versions before launch. The rules about honesty never changed; almost everything else did.

Version one: quietLink to this section

The first version followed one rule: nothing fake. No invented clients, metrics or team members, no effects without a job, no section that exists only because landing pages usually have one.

That rule survived. The visual language built around it didn't. We had read "restraint" as "remove everything", and we ended up with a near-black page, one typeface at one weight, the same section skeleton repeated five times and a single fade-in on everything. It was accessible and honest, and in screenshots it was anonymous.

Version two: louder, not betterLink to this section

The second version added light and material: a stack of chrome frames lit by a volumetric ray shader, cut corners on every panel, a giant expanded headline at the bottom of the hero. It was more striking and it was rejected, for good reasons. The headline was oversized and sat too low. The 3D object was generic, a sequence of squares that could belong to anyone. The product screenshots were small. Technical labels ("Fig. 01", "Signal") decorated pages without informing anyone. More effects had not added up to a point of view.

The lesson: version two changed the surface and kept the composition. The third version started from composition.

Version three: one objectLink to this section

Before any section was redesigned, we designed one thing: the EXORDIC object. It is the symbol (an open frame and the point that has left it) machined as a solid. The frame is a square bar with chamfered edges, cut open along a single 45° line, its two ends separated in depth like one turn of a helix. The point is a chamfered cube that has escaped.

It is rendered live with a small signed-distance raymarcher in WebGL2: no 3D library, a studio environment written by hand (softboxes, black flags, a floor), brushed faces and polished chamfers. It redraws only when something changes, falls back to a still rendered from the same shader, and the stills double as brand assets.

The 45° cut became the system's one geometric gesture. Primary buttons carry it, a page transition opens along it, and each dark section rises over the silver one with the cut on its corner.

We prototyped two heroes in the browser, one dark and one on a pale silver sweep, and chose the silver one. It reads as a lit studio rather than a dark screen, and it gives the rest of the site a rhythm: silver, anthracite, ink.

Surfaces instead of a single blackLink to this section

Components use one set of token names. A section sets data-surface="silver" and the same names take light values, so a button or a paragraph works on either surface without variants:

TokenAnthraciteSilver
--bg#0d0f12#dfe2e6
--fg#f2f3f5#0d0f12
--fg-2#a6acb5#3d434b
--fg-3#7d848e#50565f

Every text tone is checked against its own surface, including the darkest part of the silver sweep: the tertiary tone sits at about 5.1:1 on anthracite and 5.7:1 on silver.

Type, recalibratedLink to this section

The faces stayed (Hubot Sans for display, Mona Sans for reading, Martian Mono only for real data), but the relationships changed. Display type dropped from fully expanded to near-normal width and settled at a size that holds a line instead of shouting it. Mono uppercase labels, which had been everywhere, are now plain sentence-case words, used only where they tell you something.

Motion with a jobLink to this section

The hero headline rises in pure CSS so it never waits for JavaScript. The object turns away as you scroll. The VEYN browser frame tilts back to face-on as it enters, and the feature views open along the cut when you switch them. Nothing is pinned and nothing intercepts the wheel.

Reveals moved from an IntersectionObserver to CSS scroll-driven animations. That removed JavaScript and fixed a real bug: the observer marked elements before React had hydrated them, which produced hydration mismatches. Browsers without animation-timeline simply show the content.

Two bugs worth recordingLink to this section

In development, React runs effects twice. Our cleanup told the browser to discard the WebGL context, and the second run then tried to compile shaders on a context that no longer existed. Every log came back null. The fix was to release our resources but leave the context alone.

The other: the object's polished chamfers were chosen per pixel with a hard threshold on the surface normal. At a crease, a one-pixel strip flipped between "polished" and "brushed" and drew a dashed line along the edge. The material now blends smoothly between the two.

What stayed the sameLink to this section

The content rules didn't move. The VEYN case study uses screenshots of the live product and cites where every fact comes from. The lab marks concepts as concepts. Research areas with no entries say so. The contact form only appears once a real delivery service is behind it.

Search EXORDIC

Pages
HomeIdeas into systems.
StudioWhat EXORDIC is and how it works
About usWho we are and what we do
WorkProducts and systems we have built
JournalWriting on design and engineering
Contact usStart a conversation
PrivacyHow this site handles data
Work
VEYNDigital identity platform
EXORDICStudio identity & website
paged.ccLink & sharing tools
CloreDigital news publication
Research
The Exordic FieldExperimental interfaces · experiment
Journal
Three versions of one websiteHow the EXORDIC website went from correct but anonymous, through a louder second attempt, to an identity built around one sculpted object.
Visit veyn.bioVEYN — external site
Visit paged.ccpaged.cc — external site
Visit www.clore.newsClore — external site