Aquison Jewels

A shop that does not sell

Fine jewellery does not close the way retail closes. A gold necklace is not bought from a product grid at eleven at night; it is asked about. What is the purity, can the stone be swapped, can it be made a size smaller, what would it cost. By the time money changes hands there has been a conversation, usually more than one, and often in person.

So the brief was a catalogue, not a store. No cart, no checkout, no prices — because a published price on a piece that will be adjusted, resized and quoted against the gold rate on the day is a number that is wrong the moment it renders. Every piece ends in the same place instead: a WhatsApp thread that opens pre-filled with the name of the thing being asked about, or an email that does the same. The site's job is to get someone to the point of asking, and then get out of the way.

That decision removed most of what a commerce build normally is. What was left was a browsing problem and an imagery problem.

Two ways in

Thirty pieces is an awkward size. It is too many to put on one page and expect anyone to look at all of them, and too few to justify search, facets and pagination.

The catalogue is indexed twice instead. Collections — Vivāha, Heritage Revival, Everyday Aquison, Soirée, Lumière Solitaires — are for people shopping a mood: a bridal edit, something for daily wear, one stone and nothing else. Categories are for people who already know they want earrings. Most visitors arrive knowing one or the other, and neither route is a filtered view of the other; both are first-class, with their own landing pages and their own copy.

The gallery is where the two axes meet: category crossed with collection, resolved in the browser against an index built at compile time. It is the one genuinely interactive surface on the site, and it needed no backend to be one.

The catalogue is code

There is no CMS. The catalogue is a typed data layer — pieces, categories, collections, and the relations between them — and that turned out to be the useful part.

A jewellery catalogue is a graph of references. A piece belongs to a category and a collection, carries a set of views, and appears in curated rails on the home page. Every one of those is a place where a typo produces a page that renders but is quietly wrong: a collection with a piece missing, a rail pointing at nothing, a product whose imagery never loads.

So the integrity checks run at module scope. An unknown category, a collection that does not exist, a piece with no images — any of them throws while the site is being built, and the build stops. Nothing about a static export is checked at runtime, because there is no runtime; this is the only moment those mistakes can be caught, so it is where all of them are caught.

A hundred and seventy images, none of them touched by hand

Jewellery is photographed several ways — front, on a model, on black, in a lifestyle setting — and the source files arrive named however the photographer named them.

A Sharp script owns that boundary. It walks the raw shots, normalises the filenames, resizes to a consistent long edge, writes WebP, orders the views by priority, and emits a typed manifest with dimensions and a base64 blur placeholder for each. It is idempotent, so it can be re-run on the whole set after one new piece arrives.

The payoff is that no image is ever hand-cropped, hand-listed or hand-measured. Dimensions come from the manifest, which means every image on the site reserves its exact space before it loads and nothing shifts as the page settles. The blur placeholders come from the same pass, so a slow connection sees the shape and colour of a piece resolve into focus rather than a grey box.

Making it feel like a room

The visual work was mostly restraint. A display serif with an optical-size axis for headlines against a quiet sans for everything else; a lot of space; a gold used sparingly enough to still read as gold.

The one deliberate exception is contrast. The brand gold is a light, warm tone, and on a pale background it does not clear AA. It is darkened to #8A6423 in light mode and allowed back to its brighter value in dark — the same colour role, two values, so the palette holds without any text failing a contrast check.

The rest is motion that stays out of the way: a splash on first arrival in a session and never again, skeletons on every dynamic route so a slow segment shows structure instead of blankness, and transitions between pages that are short enough to read as continuity. All of it collapses to nothing under prefers-reduced-motion.

Delivery

The whole site is a static export — pre-rendered HTML, no server, no database, no API. Product, article and FAQ structured data are generated from the same catalogue that renders the pages, so the markup and the content cannot disagree, and the sitemap is built from that catalogue rather than maintained alongside it.

It ships as a directory of files to jewels.aquisontechnologies.com. There is nothing running in production to patch, scale or wake up — which, for a catalogue that changes when new pieces are made, is the correct amount of infrastructure.