Project journal · eight chapters
Private Practice Is a Bitch
The name arrived first. The website then spent ten commits finding its hero, one day publishing thirteen times, and several months becoming a much larger product than the original one-page brief.
This is not a clean case study. It is a sourced sequence of choices, reversals, code, releases, missing transcripts, and one repository that was created after most of the work had already happened.
Start with the paper trail
The central contradiction
I rejected the loud branding. The surviving site kept it.
A quieter editorial concept was explored after the June 18 rejection. The repository and current public site still preserve the plum, hot-pink, cream, and collage system. The project journal keeps both facts instead of inventing a tidy redesign.
Read the branding chapter
The mini-season
Eight chapters, in the order the mess makes sense
Current evidence state
What the archive can actually support
- Implemented
- Responsive hero, embedded Spotify, Fishbowl topic voting, episode routes, guest pitch, newsletter, SEO, and performance work appear in the preserved source history.
- Published at the time
- Fourteen Replit-originating “Published your App” commits are preserved: one on June 11 and thirteen on June 18.
- Verified now
- The Ludara-hosted site, Spotify show, and all six registered Spotify episode URLs responded on August 28, 2026.
- Still missing
- Authorized episode transcripts, complete Replit conversation export, audience analytics, conversion evidence, and proof that every later repository feature reached production.
The next shelf
Six more stories hiding inside this one
A journal can keep growing without pretending every source gap is already solved.
- Evidence ready
The Fishbowl became a real product feature
Follow one “let people vote” request through the topic schema, generated client, API route, and reader-facing state.
- Evidence ready
The smallest newsletter signup became another backend
A short feature note about how a simple email box acquired validation, persistence, generated contracts, and delivery questions.
- Evidence ready
The social image changed more often than the story
Icons, favicons, Open Graph captures, share copy, and the repeated work of making one loud identity survive every rectangle.
- Needs source
Six episode diaries
One note per episode, but only after authorized transcripts or reviewed source notes exist. Public metadata alone is not the conversation.
- Needs verification
Did Fishbowl, guest pitching, and newsletter actually work live?
A runtime audit of persistence, email delivery, error states, and current deployment rather than a summary of source files.
- Needs outcome data
What happened after launch?
Listeners, discovery, site-to-Spotify behavior, and what Emily wanted to keep doing—without using launch as a substitute for impact.
Why the record looks weird
The project existed before its GitHub repository did.
Naming and rejection live in conversation history. Most of the first build lives in imported Replit commits. GitHub was created in July, after the June work it now contains. A later unmerged content-steward branch holds the six-episode metadata registry. The chronology has to be reconstructed across all three.
No invented ending: publication is verified; audience, revenue, conversion, and comparative design performance are not yet measured.