An English Baroque Journey

A book, a concert series and a website that had to feel like all three. Built for Arcangelo with Next.js and Sanity. Cookie-free, with nothing loaded from a third party, and handed over so the client can run it themselves.

Project An English Baroque Journey
Client Arcangelo
Built with Next.js · Sanity · Vercel
Optimised for Performance · Privacy · Handover

The brief

Arcangelo are a period-instrument ensemble. In 2026 they set out on a two-year project: five concert programmes exploring English music from 1660 to 1760, devised with Wigmore Hall, and a book of new essays to go with them.

The book would be a limited print edition, sold at concerts. The website had to be its companion. Not a facsimile of the printed page, and not a brochure for the concerts either. Somewhere a reader could get their bearings in the century, read a digest of each essay, hear the music and find the full version in the book.

Two things made it unusual. The content would arrive over two years, so the site had to launch unfinished and look finished. And the audience includes scholars who notice when a date is wrong.

The approach

Foundations before looks. The first weeks went on plumbing, not design. A content model that mirrors the book: chapters, authors, images with credits, composers, timeline events, concerts. All 73 composers imported from the client's spreadsheet with their awkward dates intact, c.1655 staying c.1655 rather than being rounded into false precision. Pre-built pages, images served from the CMS's own network, a hard spending cap. It is far cheaper to prove the plumbing works before committing to a look.

The book sets the tone. The hero is Zoffany's The Sharp Family, the book's cover painting, fading to black with the title off the canvas. The typefaces are free, self-hosted serifs in the same tradition as the book's Arno Pro, chosen so the site never depends on anyone's Creative Cloud subscription staying active. Every page has the hard edges and generous margins of a well-set book. A Handel scholar's first reaction was that it really is a book.

Two instruments for the journey. The composer lifelines chart 73 composers across two centuries. Inside the 1660 to 1760 focus window everything is in colour. Outside it, sepia. So Beethoven can sit there as an orientation point without pretending to be part of the story, and nothing gets clipped or misrepresented. Click a composer and you can be hearing him on Spotify in three seconds. The timeline runs 130 events down a spine of reigns, with wars stretching across their years and the moments where music and history landed together picked out.

Launching unfinished. Six of the eight parts were not written at launch. Each gets a tile with its own artwork and a forthcoming mark, and the chapter page lights up on its own the moment the digest is published in the CMS. No rebuild, no call to me. Concert pages have a switch the client controls, so each one goes live fully stocked with its films.

No cookies, no banner, nothing from a third party. The site makes zero third-party requests on page load. YouTube films and Spotify albums load only when someone presses play, so nobody is tracked just for visiting. Visitor numbers come from Vercel's cookie-free analytics. There is no consent banner because there is nothing to consent to. For a site that spent three months refusing to behave like a website, this mattered.

Never alter supplied data. Where the client's spreadsheet disagreed with the record, I flagged it rather than fixed it. A birth year, a nationality, a king on the wrong throne in 1760. The authors' own corrections, when they came, were live within a day.

Handover built in. Arcangelo run the site themselves now. Sanity Studio has help text on every field, amber warnings where a credit is missing, and a set of short crib sheets for the jobs they will actually do. Build-time checks report problems without ever blocking a deploy, because an editor fixing a typo should never take the site down.

The result

The site went live in October 2026, ahead of the first Wigmore Hall concert. The client's executive director, after showing it to his team, reported general amazement and an outright delighted "who made this?". The Prologue author called the lifelines a fun resource that will play well with audiences. A Cambridge Handel scholar said the lifelines and timeline pages were wonderful and that the site could be a model for others.

Behind the scenes, publishing a new chapter is a job the client does without me. The one line of feedback I will keep: "Sanity is a doddle. Where has it been all my life?"

Is this for you?

If your content is structured, will grow over time, and has to be right as well as beautiful, this is the approach I'd recommend. See it at baroque.arcangelo.org.uk.

If your project sounds similar, get in touch.

Stack Next.js · React
CMS Sanity (headless), client-run
Content 8 parts · 73 composers · 130 events · concert companion · Watch & Listen
Privacy Zero third-party requests · no cookies · no consent banner
Fonts Self-hosted · Cormorant Garamond, EB Garamond, Fontin SmallCaps
Hosting Vercel · static generation · spend-capped
An English Baroque Journey home page, Zoffany's The Sharp Family fading to black beneath the title
Home page, Zoffany's The Sharp Family (© The National Gallery, London) fading to black
Composer lifelines chart, bars in colour inside the 1660 to 1760 focus window and sepia outside it
Composer lifelines, colour inside the focus window and sepia beyond it
Timeline page showing the 1680s, with reigns running down the spine and events either side
Timeline, 130 events down a spine of reigns
A chapter page with the essay digest, inline images and author biography
A chapter page, the digest with its images and author biography
Concert companion page with the programme, players and a stack of films from the musicians
Concert companion, programme, players and films