Bluewave Podcast Site

Give listeners a place to discover an interview, understand its subject and keep listening while they browse the archive. Bluewave Podcast Site pairs a dark cobalt-lit hero and compact audio card with editorial episode pages, duotone covers and a docked player. The Even Keel reference contains 24 fictional episodes across three seasons; replace its people, recordings and show facts with your own.

What you get

  • A connected show website: home with latest episodes, themed playlists, playable quote moments, guest mosaic, host introduction and newsletter; an archive with text search, topic/season/sort filters, grid/list layouts, result counts and reset/empty states; episode details; guest directory; About with suggestion/contact material; privacy, terms and a designed not-found view.
  • Episode pages that can carry chapter navigation, show notes, three key ideas, timestamped transcript excerpts, mentioned items, guest background, previous/next and related episodes. The 24-episode reference distinguishes richer chapter-equipped entries from simpler archive entries; actual episodes and seasons come from your data. The home latest list shows six newest entries and topic filtering can draw from the whole archive.
  • A persistent listening interface: play/pause, seek by pointer/drag/keyboard, 15-second back and 30-second forward, six speed choices from 0.8× to 2×, chapters, queue add/remove, auto-advance and progress indicators. A first play reveals the docked bar; its now-playing panel includes chapters and Up next, with a compact phone bar and full-height mobile sheet. Position, queue and rate use local storage when allowed, with an in-memory fallback.
  • A real-audio path when you supply an episode audio URL, and a simulated clock when you do not. The supplied waveform is seeded decorative SVG rather than analysis of the recording. Audio hosting, feed ingestion, transcription and recordings are not supplied. Remote recordings need connectivity even if the surrounding page’s fonts and pictures are embedded offline.
  • An editorial visual system with Schibsted Grotesk UI/heavy hero type, Newsreader reading/section type and italic accents, and Geist Mono timestamps. A 1240px layout uses cool paper, one cobalt accent, blue-lit hero/newsletter/404 stages and live-text episode labels over duotone portraits. Default presentation is a light page with dark-blue stages; a full dark theme is an additional request, not the default.
  • A template, style/section/image/motion/icon guidance, sixteen example image assets, build helper and static validator. Default output is one adapted HTML file with fonts and pictures embedded; a framework project receives proper routes and a player mounted once in its shared layout. Newsletter and guest-suggestion forms are local demonstrations until connected to the show’s email or inbox service.

Before you choose

Review the listener journey with an actual recording: discover an episode, inspect its context, jump to a chapter, queue another and navigate without losing playback. Keep the show’s facts and people authentic, and distinguish a working-looking silent clock from sound, a generated waveform from analysis, and local confirmation from a delivered subscription.

Good fit

  • An interview-show host or producer needs episodes, people, listening and subscriptions organized in one coherent destination.
  • A company podcast wants episode pages, show notes, approved guest material and a newsletter without presenting itself as an audio-hosting platform.
  • A show already has chapter timings or transcript excerpts and wants visitors to browse and seek into that material on the web.

Not for

  • Hosting or producing recordings, importing an RSS catalog automatically or generating transcripts. You supply and verify the episode data and audio sources.
  • A subscriber collection or guest inbox that works without a service connection. The template only validates and changes local form state.
  • A video-first player or guaranteed offline playback of remote recordings. The core interface is designed around audio, covers and reading material.

How to use

You say/bluewave-podcast-site Build the Even Keel site, a weekly interview show about independent businesses built to last, hosted by Maren Holt.
  1. Provide show name, host(s), promise, schedule, feed/site addresses and recurring topics. For each episode include number, season, date, actual duration, title, guest, business/place and summary; add approved chapters, three key ideas, a quote, transcript excerpt, mentioned items, guest photos and audio URL where available. List missing copy for review, and never invent listener/download totals, chart positions, ratings, awards, quotes or sponsorship evidence.

  2. With no existing project, adapt the standalone template. In an existing/requested React, Next.js, Vue, Svelte or Astro project, use real archive/detail routes and mount one player store/context in the shared layout so route changes do not recreate it. Use typed episode collections, local fonts/images and stack-appropriate icons. Navigation persistence is a design requirement to test in the completed port, not a backend service included by the Skill.

  3. Keep the home sequence and signature composition: cobalt-lit rounded hero with a short heavy three-line heading, one serif italic accent, one play action, recent-guest faces, four neutral follow marks and a compact audio card. Use Newsreader headings below it, natural-color portraits when describing people and duotone crops when showing episode artwork. Keep the featured episode consistent across static hero controls, durations, cover, footer link and player notes link.

  4. Populate show, topic, episode, theme-playlist, quote-moment and mosaic data together. Removing an episode also removes its references from playlists, quote moments and the mosaic. Theme sections take two to five tabs of two to four episodes; moments need at least two quoted episodes. Adjust the guest mosaic for three photographed guests or use a typographic list with fewer; keep two to four recent-guest faces only when appropriate material exists.

  5. Adapt the structure to the show: solo/co-hosted work can replace guests with recurring topics and omit the directory/mosaic; a company show can use “Pitch a story” and remove sponsorship; a seasonal narrative can make seasons and scene chapters prominent. With fewer than roughly ten episodes, reconsider the season selector and retain topic chips only where each category has enough material. Remove unused routes and their links together.

  6. Use permissioned actual host/guest photographs for a real show. The ten guest portraits, host portrait and four face crops portray fictional people and must be replaced; only the unbranded studio scene can serve as a disclosed neutral stand-in. Missing episode portraits fall back to the CSS show artwork. Image generation is appropriate for fictional demo portraits or non-person artwork and may incur the agent tool’s charges; it must not fabricate photographs of real guests.

  7. Connect approved audio URLs and check that catalog duration, chapter/transcript offsets and real recording length agree. Without a URL, controls advance a silent simulated clock. The helper embeds fonts and supported image assets, not MP3 recordings, so real-audio offline delivery needs separate work. Inspect media loading, play rejection, seeking after metadata, network errors and mixed simulated/real episodes: the inspected engine catches a rejected play promise but has no explicit metadata/error recovery handlers.

  8. Test play/pause, seek preview and dragging, keyboard sliders, skip limits, every speed, chapter/transcript jumps, quote playback, theme playlist queuing, queue removal and auto-advance. Keep the bar clear of page content and check the phone sheet. Reload to verify resume only where storage is available; sandbox/privacy restrictions may reduce it to the current page session. Decorative wave peaks should not be described as audio-derived amplitudes.

  9. Check sharing against the actual deployed routes. The template builds a site URL ending in /episodes/<number> with optional ?t=<seconds>, whereas the standalone detail router uses #/episode/<number> and does not consume that start-time query. A copied timestamp link is therefore not an end-to-end working deep link by default. Adapt its destination and receiver together, then open the copied link in a fresh tab and verify the intended episode/time.

  10. Exercise search via slash or Ctrl/Cmd K, arrows/Enter, highlighted matches and no-results states; combine archive query/topic/season/sort and grid/list controls. Test neutral follow/feed-copy controls, mobile focus trap and Escape, and form errors/loading. Newsletter and suggestion handlers are timers that display subscribed/sent wording; keep them explicitly local in a demo and connect confirmed service responses before promising subscription or delivery.

  11. Use Node.js 18+ and initial internet access for the four font downloads to build the default file with the bundled inliner. Target at most 5 MB, with an 8 MB hard cap, then run the supplied validator. Check exit status: an output may exist even if missing assets caused failure. Files mode supports locally hosted assets. The validator checks structure, routes, controls and identity leftovers but does not prove media availability, truthful form delivery or timestamp-link round trips; remote audio assigned by script is outside its resource-attribute checks.

  12. Review all routes at 1440, 1024, 768, 390 and 360px, with two screenshot/critique/fix passes and a restricted-iframe pass for the standalone preview. Inspect crops, portrait repetition, content hierarchy, keyboard focus, reduced motion, overflow and player overlap. Deliver the path, checks actually performed and every drafted fact or stand-in image; then play an actual episode, browse during playback and request content/layout changes in ordinary language.

Requirements and costs

You bring
Show name, host, schedule and feed address · Episode list: number, season, date, duration, title, guest and a short summary · Optional: chapters, transcript excerpts, guest photos and audio links
Dependencies
Node.js 18 or newer on your agent's machine, to run the bundled script that builds the single offline file · Internet access while the file is built, so the fonts can be downloaded once and embedded · Your own host and guest photos for a real show; an image generation tool in your agent only for fictional demo portraits
Outside costs
Portraits for a fictional demo are generated with your agent's own image tool, which may incur that tool's usage charges. A real show uses your own photos, and episodes without one fall back to the show's cover artwork.
Publisher testing
v1.0.6 — Claude Code / Claude Desktop / Cowork / Codex / ChatGPT

FAQ

User reviews

—0 reviews

Select a star to share your experience.

No reviews yet. Ratings appear once readers share real experiences.

Similar Skills

View all skills