Product · shipped
manncavemedia.com
A media hub that updates itself — new episodes, videos and posts appear on their own, with no CMS and no manual edits.
- Year
- 2026
- Disciplines
- Web product, infrastructure
- Stack
- AstroTypeScriptTailwindDocker
The brief
One site for three brands, that never needs a human to publish to it.
MannCave runs a podcast, an apparel label and a dev practice. Three audiences, three release rhythms, one team. The brief was a hub that keeps itself current — so publishing an episode is the only publishing step there is.
What we built
- 01
One adapter per source
Every feed — podcast RSS, YouTube, GitHub — normalises to a single shape the UI consumes. Adding a fourth source is one file, not a redesign.
- 02
A cache that fails well
Feeds refresh hourly behind a stale-on-error cache: new episodes land within the hour, and a dead upstream serves yesterday’s data instead of an error page.
- 03
Blog and admin, self-hosted
A password-gated editor with drafts and previews, plus a companion post generated for every episode automatically — deduped, and never overwriting an edit.
Screens
-
The homepage: the studio leads, with a featured system from the work beside the pitch. -
The podcast archive. Every episode arrives from the show's RSS feed on its own; nobody publishes it here. -
The work index. Each row opens a case study, and a tagged GitHub repo can join it without a code change. -
Services: web development, web apps, AI and automation, each with its own page, FAQ and structured data.
Where it stands
Live in production at manncavemedia.com. The front end has been redesigned three times since the first build without a single change to the feed layer — episodes, videos and posts kept arriving through every one.
- From publish to on-site
- < 1 hr From publish to on-site
- Manual publishing steps
- 0 Manual publishing steps
- Lighthouse accessibility, mobile and desktop
- 100 Lighthouse accessibility, mobile and desktop
Next case
CMD-OS