← Back to work

Case file 06 · Web · Client

What Came After

A custom Next.js and Sanity rebuild for a podcast telling the stories of people whose lives changed after October 7. Six seasons of real episode data, behind an audio player that keeps playing as you browse.

Year
2026
Role
Solo: client rebuild, design, build
Read
4 min
90+Episodes integrated
20+Daily visitors
6Seasons, plus a miniseries
3Weeks to build from scratch

Context

A podcast about ordinary people with extraordinary stories, whose lives were changed by October 7 and the war that followed. The show has just started its sixth season, hosted on Podbean and distributed through Spotify and Apple. The site was originally built and hosted on Squarespace, and the brief was blunt: it felt outdated, it wasn't clean, and the About page was a block of text, not something you move through.

The subject is heavy, so the design had to stay editorial and restrained, not dramatic. The identity was the way in. The logo is an anemone breaking out of a Star of David, inspired by the anemone fields in the memorial landscape around the Gaza envelope. The colours (maroon, crimson, gold and ivory) and the typography (Bebas Neue over Cormorant Garamond) came from a mock-up the client already liked, and they sit naturally with the logo's red and yellow.

The shipped hero

The problem

The rebuild had to solve three problems at once. The episodes live in a podcast RSS feed (the public list of episodes that apps like Spotify and Apple read from), and the real feed was messier than the original spec assumed. 30 of its 80 items had no season tag and three had no episode number, so seasons couldn't just be read off it. The site also had to stay editable by people who aren't developers, because the team needed to add guests and swap images without calling me. And the show was planning to move to a different podcast host, so any web address tied to the current host's own IDs would break the day it moved.

A fourth problem only showed up once I was building: the visual direction was still moving and unclear. My main reference was the old site, and the team were still working out how they wanted the brand to look.

What I built

A Next.js 16 site with Sanity for content, on Vercel. Episodes are pulled from the feed when the site builds and refreshed every hour. Web addresses are based on episode titles so they last, and guest names are picked out automatically. Where the feed doesn't say which season an episode belongs to, a list I keep in the code fills it in. All ninety-plus episode pages are generated ahead of time.

One audio player keeps playing as you move between pages, and every play button on the site controls it. Each season has its own URL, so you can share a season, and going back returns you to the one you were browsing. About, Contact and the team pages are Sanity documents, which means the team can edit those pages themselves. When an editor wants to change an episode's details, they pick it from a searchable list of titles, not by a feed ID they'd never be able to find.

A season, at its own URL
Episode detail

Decisions & iterations

The web addresses changed first. The spec wanted paths like /episodes/s5e8, but the feed couldn't support that, so each address uses the episode title only and will survive a move between hosts.

The biggest call was visual. The first hero, the big opening screen, was a saturated red fill, and once I saw it live I thought the connotation was wrong. The show is about rebuilding, not violence. So it became a photo of an anemone field, where the red reads as remembrance, not aggression or vengeance. What made that change cheap was the order I built in. The whole skeleton was built on real data with no design decisions in it, while I worked on the design in parallel, and all the visual work went on in one paint pass at the end. So only the hero needed redoing, not a batch of finished pages. It's the workflow I still use today.

The design itself was handed over as a working prototype, not a picture: a running build with a panel for adjusting the colours and type live, so the palette could be judged in motion instead of argued about. Later, working with the team, the nine “Live From Israel” episodes became their own miniseries instead of being folded into Season 5. The contact form was connected to Notion, because that's where the executive director works, and the raw feed ID an editor could never find was replaced with a dropdown of episode titles.

The miniseries, kept separate

Outcome

Live at whatcameafter.com, off Squarespace and onto the new build. Every page has been restyled, and 141 automated tests check that nothing breaks when something changes. Real content is in Sanity, and I wrote a simple guide for the team, so they can add a guest or swap an image without me.

Credits & tools
Solo: client rebuild, design, build — Alfie ReesNext.js 16 · Sanity · VercelLive at whatcameafter.com · live
Case file 06 of 07