Public cultural site
Public routes present concerts, season, repertoire, composers, ensembles, program notes, visit information, support, donations, and institutional pages.
Case study
A Cloudflare-native cultural platform that combines a public chamber-music site with protected patron, staff, content, ticketing, archive, and AI/data workflows.

Recorded scope across routes, data models, interface screens, and workflow code.
A Cloudflare-native cultural platform that combines a public chamber-music site with protected patron, staff, content, ticketing, archive, and AI/data workflows.
The same chamber-music records must serve a patron choosing a concert, a staff member building a campaign, and an archive visitor browsing decades of programming. Internal workflows also connect tickets, patrons, venues, repertoire, program notes, and media.
One concert record can support public listings, staff campaigns, repertoire history, program notes, and archive browsing.
Public routes present concerts, season, repertoire, composers, ensembles, program notes, visit information, support, donations, and institutional pages.
Drizzle schemas model artistic, archival, patron, ticketing, campaign, document, and operational entities as connected records.
Protected staff modules manage campaigns, content, patrons, messages, email, box office, social ads, and concert building.
Program archive extraction, composer and performer generation, repertoire research, concert generation, artwork selection, validation, review gates, and approved writes support archive repair and content production.
R2-backed archive assets and previews.
Archive extraction, generation, audits, approval gates.
Implementation details from the product, data, workflow, and infrastructure layers.
Public routes cover concerts, composers, ensembles, repertoire, program notes, seasons, and discovery.
Ticketing foundations model inventory, orders, holds, issued tickets, signed QR payloads, scan events, refunds, and transfers.
Program archive extraction creates reviewable JSON/CSV artifacts, page manifests, rendered-page queues, issue lists, audit workbooks, vision packets, and import-ready concert-generation inputs.
Generation pipelines handle source research, draft records, media and artwork selection, quality audits, human review gates, and approved database writes for composers, performers, pieces, repertoire, and concerts.
Pipeline sessions persist status, phase progress, artifact paths, manifests, errors, costs, resume counts, and summaries.
Media serving supports local development storage and Cloudflare R2-backed production storage.
The application model also covers locale routing, security middleware, NextAuth sessions, and Cloudflare deployment infrastructure.
How the public pages, staff workflows, data, review steps, and infrastructure connect.
Concerts, seasons, profiles, giving.
Records, relationships, translations.
Review, repair, publishing, operations.
R2-backed archive assets and previews.
Archive extraction, generation, audits, approval gates.
Technology
Languages, frameworks, data stores, and infrastructure.
The implemented CPM interface uses full-field brand colour, League Spartan as the workhorse UI face, Baskervville for editorial passages, thin teal rules, search/filter controls, archive cards, and staff review states.
Philosophy
The interface treats CPM as both a cultural publisher and a working institution: expressive for public discovery, restrained for archive records, patrons, and staff operations.
More screens showing the product in use.