Portfolio
Selected builds, systems, and tradeoffs. Raintree product pages live at raintree.technology.
Selected projects
17 projects
Agent Safety & Evals
Apps
Context & Developer Tools
Data & Intelligence Systems
Product SaaS
Systems & Low-Level
Music & Creative Systems
Music Catalog
Audio archive / personal case study
Public catalog and custom player
What I built
Public music catalog and player for archive recordings, album pages, and agent-readable discovery.
- track index
- Velite
- audio storage
- R2
- player core
- HTML audio
- public catalog
- Archive mode
Stack
- Next.js 16
- React 19
- Velite
- Cloudflare R2
- Neon + Drizzle
- Radix UI
- Better Auth
Runtime
- Public Next app serves track pages, albums, artist views, player routes, search, feeds, sitemap, archive-only mode, and optional admin/auth surfaces.
- AudioProvider owns one hidden HTML audio element and synchronizes play, pause, seek, rate, ready state, abort handling, and playback errors.
- The app builds from static content and public archive fallback when private DB/auth/R2 credentials are absent.
Data model
- Track Markdown frontmatter stores album, track number, audio path, cover image, order, artist, duration, genre, and public catalog metadata.
- Archive objects use canonical Cloudflare R2 key patterns such as `featured/*`, `catalog/*`, and `albums/<album>/*` behind a public CDN base URL.
- Generated Velite indexes power tracks, albums, artist pages, theory references, llms.txt, OpenSearch, sitemap, manifest, and JSON-LD discovery.
Techniques
- Playable public tracks filter to archive-backed `featured/` audio so broken external blobs do not enter the catalog.
- Curated archive data separates public recordings from optional database, social, upload, and monetization features.
- Global search and catalog filters are built locally from content indexes rather than a remote search service.
- Public-mode scripts intentionally stub DB migration/backup jobs so a static catalog cannot imply live private service operations.
Verification
- Content query filters archived/draft tracks before rendering public lists.
- Audio state is centralized so switching tracks preserves playback rate and handles abort errors.
- R2 public base URL is safe client config while bucket credentials stay private and optional.
- Disabled DB/admin scripts keep the public archive mode from implying live upload or monetization features.