VVyshyvka
studio

Case study

Artist Platform

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.

Capabilities
Design, Frontend, Backend, DBA, DevOps, Media Infrastructure
Type
Cultural platform and operations desk
Stack
Next.js, TypeScript, Drizzle ORM, D1, R2
Scope
Editorial site, Private desk, Archive model, Media delivery
Year
2026

Product inventory

Repository evidence: routes, data model, interface screens, and workflow code.

Page routes
34
Schema tables
40
Locales
11
Test files
14
Import scripts
7

Project overview

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.

What was built

A careful cultural platform build where editorial presentation, structured archives, desk workflows, and deployment infrastructure share one product model.

Public cultural site

Locale-aware public pages for calendar, archive, projects, listening, media, press, biography, contact, legal, and news content.

Private operating desk

Protected desk routes for calendar, projects, media, press, campaigns, settings, next actions, and project health.

Structured archive model

Drizzle/D1 schema for profile, performances, works, projects, media, press, subscribers, campaigns, imports, normalization, and audit logs.

Calendar operations

Import, enrichment, repair, normalization, recovery, filters, and audit scripts keep performance data maintainable.

Media infrastructure

R2-backed serving, path normalization, range requests, content types, and cache headers support cultural media.

Approval-gated broadcast scaffolding

Provider adapters and publish-attempt records capture review, approval state, and logged publishing attempts.

Selected details

Implementation details from the product, data, workflow, and infrastructure layers.

  • 01

    Public and private routes stay separated from the visible navigation model.

  • 02

    R2 media serving includes path normalization, range requests, content types, and cache headers.

  • 03

    Calendar import, repair, normalization, recovery, and audit scripts support structured maintenance.

  • 04

    Automation adapters keep provider selection, publish attempts, approval state, and audit history connected.

  • 05

    Calendar source entries, normalization runs, performance sources, import batches, publish attempts, and audit logs support provenance and review.

  • 06

    Editorial routes connect biography, repertoire, press, media, projects, calendar, and guided-listening pages.

  • 07

    Private desk workflows support parsing, normalization, recovery, audit, and approval paths for maintained cultural records.

Systems overview

How the public pages, staff workflows, data, review steps, and infrastructure connect.

Public site

Editorial routes, calendar, archive, media.

Private desk

Projects, press, campaigns, settings.

Content model

Performances, works, media, press records.

Media delivery

R2-backed serving and cache behavior.

Import scripts

Calendar import, normalization, recovery.

Technology

The platform stack behind the build.

Next.js
React
TypeScript
Drizzle ORM
SQLite
Cloudflare D1
Cloudflare Workers
OpenNext
Cloudflare R2
Vitest

Design language

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

A living archive before a promo site

The platform treats performances, repertoire, media, press, and projects as maintained cultural records, with a private desk supporting the public editorial layer.

Source-aware calendarGuided listening roomsProject dossiersApproval-gated publishing
Aa
Editorial serif, compact UI sans, Fira CodeArchive pages, metadata, import logs
Ink#25211d
Paper#f7f0e7
Rust#a65336
Moss#4f6047
Rule#d9cbbb

Selected screens

Additional screens from the case study.