Operational Notes

Content Pipeline

Reference page for future content updates. This page prevents accidental publication of unverified performance media, release data or artwork.

Live / Performance Proof

  • Add only verified real material to data/performanceProof.ts.
  • Recommended photos path: public/images/live/.
  • Recommended videos path: public/video/.
  • Required fields: title, date, location, type, src, poster, credit and caption.
  • Do not publish generic stock media as live proof.

Hero Video

  • The Hero is ready for a real video through data/heroMedia.ts.
  • Current state: video is null and fallback image is /images/antony-well-hero.webp.
  • When a verified 10-15s loop exists, place it in public/video/ and set heroMedia.video to the file path.
  • Keep poster as a still image fallback.
  • Run pnpm lint and pnpm build after enabling video.

Pending Releases

  • Use data/releasePipeline.ts as the holding area for titles that are not yet safe to publish in the catalog.
  • Move a release into data/site.ts only after Beatport URL, cover UUID, label and date are confirmed.
  • Do not invent labels, cover UUIDs, release dates or Beatport links.

Production Audit Method

  • Prefer curl.exe -I and PowerShell Invoke-WebRequest with a cache-buster query when validating production.
  • Some external fetch tools may return stale HTML after repeated checks in the same chat/session.
  • Treat Vercel headers, browser incognito checks, and apex/www redirect tests as the source of truth.
  • Record the commit hash used for every audit so future reports can compare production against Git accurately.