Whimsy Gossip

Whimsy Gossip had a website: a template-based landing page that worked fine as a placeholder. But the podcast had grown. There were fan films in production, a cast and crew worth introducing, episodes across multiple platforms, and a fanbase that was showing up with real interest. The landing page had nowhere to send them.

Content lived across platforms the team doesn't control: Spotify, Apple Podcasts, YouTube, social media. A new fan who found the podcast on one of them had no single place to explore the rest. There was no newsletter, no contact channel that wasn't a social DM, and no way to surface the full scope of what they were building without updating a template that wasn't designed for any of it.

The site was designed around one core requirement: the team needed to manage it without developer involvement. All content lives in a headless CMS: episodes, fan films, cast and crew profiles, FAQ entries, and site-wide settings. The team updates anything through a visual editor, and changes appear on the live site automatically.

The visual design carried forward from the podcast's existing identity: a dark fantasy aesthetic with gold accents, editorial typography, and animated details that fit the subject matter without overwhelming it. The audio player was treated as a first-class feature rather than a basic embedded widget. Visitors can start an episode and browse the site freely without the playback stopping between pages.

Newsletter infrastructure was built end-to-end (signup, welcome email, unsubscribe flow), so the team had a working audience channel from day one, not a placeholder to be set up later.

Whimsy Gossip now has a canonical home for everything they produce. Every episode, fan film, and cast profile is indexed and discoverable in search. The newsletter list is growing through an on-site signup the team owns. Content is managed and updated independently. New episodes go live without a developer in the loop.

The site handles analytics, cookie consent, and form submissions without ongoing maintenance. The team's time goes toward making the podcast and the films, not coordinating with a developer every time something needs to change.

The site had one unusual requirement: the audio player needed to keep running as visitors moved between pages. Start an episode on the episodes list, navigate to a cast profile or fan film, and the audio stays live throughout. Most sites don't need this, and it required careful planning around how the site's navigation was structured. The behavior visitors experience is seamless; the work to make it seamless was the most involved part of the build.