Public cultural site
Locale-aware public pages for calendar, archive, projects, listening, media, press, biography, contact, legal, and news content.
Case study
A custom platform for a solo classical artist, framed publicly as an anonymized cultural-product build: editorial site, structured performance archive, project dossiers, media and press pages, private desk workflows, import tooling, and Cloudflare deployment infrastructure.

Repository evidence: routes, data model, interface screens, and workflow code.
A custom platform for a solo classical artist, framed publicly as an anonymized cultural-product build: editorial site, structured performance archive, project dossiers, media and press pages, private desk workflows, import tooling, and Cloudflare deployment infrastructure.
A conventional artist website would flatten the domain into biography, dates, and media links. This platform has to manage changing performance data, long-lived repertoire, project dossiers, press materials, recordings, writing, artwork, presenter resources, private review, and future publishing workflows without exposing operational details.
A careful cultural platform build where editorial presentation, structured archives, desk workflows, and deployment infrastructure share one product model.
Locale-aware public pages for calendar, archive, projects, listening, media, press, biography, contact, legal, and news content.
Protected desk routes for calendar, projects, media, press, campaigns, settings, next actions, and project health.
Drizzle/D1 schema for profile, performances, works, projects, media, press, subscribers, campaigns, imports, normalization, and audit logs.
Import, enrichment, repair, normalization, recovery, filters, and audit scripts keep performance data maintainable.
R2-backed serving, path normalization, range requests, content types, and cache headers support cultural media.
Provider adapters and publish-attempt records capture review, approval state, and logged publishing attempts.
Implementation details from the product, data, workflow, and infrastructure layers.
Public and private routes stay separated from the visible navigation model.
R2 media serving includes path normalization, range requests, content types, and cache headers.
Calendar import, repair, normalization, recovery, and audit scripts support structured maintenance.
Automation adapters keep provider selection, publish attempts, approval state, and audit history connected.
Calendar source entries, normalization runs, performance sources, import batches, publish attempts, and audit logs support provenance and review.
Editorial routes connect biography, repertoire, press, media, projects, calendar, and guided-listening pages.
Private desk workflows support parsing, normalization, recovery, audit, and approval paths for maintained cultural records.
How the public pages, staff workflows, data, review steps, and infrastructure connect.
Editorial routes, calendar, archive, media.
Projects, press, campaigns, settings.
Performances, works, media, press records.
R2-backed serving and cache behavior.
Calendar import, normalization, recovery.
Technology
The platform stack behind the build.
An archival editorial interface for a solo classical artist: warm paper fields, serif-led hierarchy, score-like textures, compact uppercase metadata, rust accents, and denser private-desk panels.
Philosophy
The platform treats performances, repertoire, media, press, and projects as maintained cultural records, with a private desk supporting the public editorial layer.
Additional screens from the case study.