- Client
- LivingVERSES
- Industry
- Podcast
- Platform
- Custom (Next.js)
- Year
- 2026
( The brief )
What did LivingVERSES need?
LivingVERSES had about 90 episodes and no website of its own.
New episodes go out through Buzzsprout every week, so the site had to keep up without anyone updating it by hand. Listeners needed a way to find older episodes by topic and Scripture, and to keep listening while they browse.
( What we built )
What did we build for LivingVERSES?
We built a podcast site that reads the show's RSS feed, gives every episode its own page and has a player that keeps playing across pages.
Episodes that publish themselves
The site reads the Buzzsprout RSS feed and refreshes every hour. A private link refreshes it straight away after a new episode.
A page for every episode
Each episode has its own page with show notes, and the Scripture references are pulled out of the notes.
An archive you can search
Listeners can search the whole archive and filter by season.
A player that follows you
Speed control, 15-second skips and lock-screen controls, with a mini player that keeps playing from page to page.
Contact and newsletter forms
Both send a confirmation email and are rate limited against spam.
( The site )
What does the LivingVERSES website look like?
Here is the whole homepage, top to bottom. Scroll inside the window to see every section.

( Stack )
- Next.js 16
- TypeScript
- Tailwind CSS v4
- GSAP
- Lenis
- RSS (Buzzsprout)
- Nodemailer
( Questions )
Questions about the LivingVERSES website
How do new episodes get onto the LivingVERSES website?
The site reads the podcast's Buzzsprout RSS feed every hour, so a new episode appears without anyone touching the website.
Does each podcast episode have its own page?
Yes. Every episode gets its own page with show notes and the Scripture references from them.
What is the LivingVERSES website built with?
It is a custom Next.js site that reads the RSS feed on the server and prerenders every episode page.
( Related )















