Platform build

Jamb

A large catalogue and journal, rebuilt on one CMS

IndustryAntiques & luxury retail
EngagementPlatform build
StackNext.js · Sanity · TypeScript · Tailwind · Turborepo · Vercel
In one lineA large catalogue and journal, rebuilt on one CMS

THEchallenge

Jamb is a London dealer in antique chimneypieces, lighting, and furniture, with a reputation built over decades and a catalogue to match. The existing site held a large, carefully photographed collection alongside an editorial journal, and all of it had to move to a modern platform without losing its standing in search.

A catalogue that size is mostly links: to Google, to old bookmarks, to references scattered across the web. A migration that breaks those links quietly breaks the reputation attached to them, so the rebuild had to preserve every route it inherited.

THEsolution

We rebuilt the catalogue and the journal on Next.js and Sanity in a single monorepo, so the shop, the editorial section, and the studio share one codebase and one publishing pipeline. Editors get a catalogue and a journal they can run themselves, without a developer in the loop.

The migration was mapped route by route, with a full redirect audit so old URLs land where they should. On the performance side, the publishing pipeline was reworked around webhook-driven revalidation, so edits reach the live site quickly without rebuilding the whole thing each time.

THEresults

One CMScatalogue and journal, published from one place
Redirectspreserved across the migration
Unblockedpublishing pipeline: edits go live without a full rebuild
Visit jamb.co.uk

This engagement is an example of standalone builds.

Have a similar problem?

Tell us what you're working on. We'll tell you how we'd approach it.

We reply within one working day.