Dorsyth Records Artist Platform
Designed and developed a cinematic multi-artist platform for Dorsyth Records, supporting artist-specific branding, release promotion, video content, newsletter segmentation, and future merch expansion.
For Decision-Makers
Executive Summary
Designed and developed a config-driven Next.js platform for a multi-artist record label, supporting artist-specific branding, release promotion, video content, and segmented newsletter automation. Built reusable components and theme systems so new artists onboard as data, not engineering work.
Business Challenge
What was at stake
Dorsyth Records needed a digital platform capable of supporting multiple artists with distinct visual identities under a unified label experience, while preparing for future artist onboarding, release promotion, newsletter automation, and ecommerce expansion—without rebuilding the application architecture each time.
Key Problems
- Multiple artists with distinct identities sharing one label
- Future artist onboarding without rebuilding the codebase
- Release promotion and cinematic video content presentation
- Newsletter segmentation by audience interest
- Foundation needed for merchandise/ecommerce expansion
Stakeholders Affected
Label leadership, artists, fans and newsletter subscribers, and future commerce partners.
Technical Approach
Config-driven architecture so adding an artist is data, not code
Built a Next.js platform separating label identity, artist identity, and release identity into reusable configuration-driven systems. Artist pages render dynamically from centralized config files. Theme variables, release data, and newsletter segmentation are managed independently to enable long-term scale.
Config-driven artist architecture using TypeScript artist files
Reusable cinematic page sections—releases, videos, streaming, merch, storytelling
Artist-specific theming under a unified label identity
Resend Contacts/Topics/Events integration for segmented newsletter automations
Deployment workflows and operational documentation for long-term maintenance
The Process
Project Lifecycle
Defined the Dorsyth Records brand identity and established requirements for artist onboarding, release promotion, newsletter infrastructure, and future commerce expansion.
Designed a reusable configuration-driven architecture separating artist data, release media, themes, newsletter segmentation, and shared UI components.
Built the Next.js frontend, reusable section components, cinematic theme system, Spotify/video integrations, and Resend subscription API.
Configured GitHub and Vercel deployment workflows, production environment variables, newsletter automations, and operational maintenance documentation.
Technical Deep Dive
Scalable Label Infrastructure
The project evolved from a visual landing page into a scalable digital platform for a cinematic record label. The architecture was intentionally designed to support future artists, independent visual themes, segmented newsletter automations, and reusable content systems while maintaining a unified Dorsyth Records brand experience.
Architectural Decisions
Choices that shaped the build
Config-driven artist pages over per-artist code
Decision
Render artist pages from TypeScript config files.
Rationale
New artists onboard as data. One template owns the structure; one fix propagates to every artist surface.
Theme variables separated from layout
Decision
Artist themes as variable systems rather than component overrides.
Rationale
Visual differentiation without forking layouts. Keeps the unified label experience while letting each artist feel distinct.
Resend Topics for newsletter segmentation
Decision
Topic-based segmentation in Resend rather than per-list provisioning.
Rationale
Subscribers self-select interests. Scales without operational overhead and avoids list-sprawl as the roster grows.
Next.js on Vercel deployment
Decision
Next.js with Vercel hosting and CI.
Rationale
SSR/SSG flexibility, image optimization, deployment simplicity for a small team—and modern operational tooling out of the box.
Key Tradeoffs
What was chosen, and against what
Content management approach
Chose
TypeScript config files
Instead of
Headless CMS
Reasoning
Small team, technical owner, rapid iteration. CMS overhead unjustified at current scale; can be layered in later when non-technical editors join.
Visual system
Chose
Custom theming for cinematic feel
Instead of
Generic component library
Reasoning
Visual differentiation is the product when the product is a label. Off-the-shelf component libraries don't deliver cinematic.
Email service provider
Chose
Resend with Topics
Instead of
Mailchimp or similar legacy ESP
Reasoning
API-first, modern developer experience, sufficient feature set at current scale. Reduces vendor sprawl and operational toil.
Measurable Outcomes
Results
Key Impact
Scalable Multi-Artist Platform
2
Artist Platforms
3
Newsletter Segments
8+
Reusable Sections
Qualitative Outcomes
Beyond the numbers
- Two artist platforms shipped under unified label
- Three newsletter segments supporting targeted promotion
- Eight+ reusable cinematic page sections
- Operational documentation enabling long-term maintenance
- Architecture ready for future artist onboarding and merchandise expansion
Lessons Learned
What generalizes
- 01
Config-driven patterns shine when content has predictable structure and varying data.
- 02
Brand identity is the product when the product is a label. Design isn't decoration.
- 03
Newsletter segmentation by interest beats segmentation by artist for engagement.
- 04
Documentation pays back fast on platforms with multiple stakeholders.
- 05
Modern stack choices—Next.js, Resend, Vercel—keep operational overhead low for small teams.
When This Approach Makes Sense
Is this a fit for your program?
Strong fit when
- Multi-tenant or multi-brand experiences share a unified parent identity
- New entities should onboard via configuration rather than engineering
- Brand differentiation matters and off-the-shelf design systems won't suffice
- Small team needs operational simplicity—modern hosting, modern ESP, low toil
Probably not when
- Single brand with no multi-tenant needs
- Non-technical owners need a CMS-first editorial workflow
- Scale demands enterprise-grade marketing infrastructure today
Next Step
Planning a config-driven product-style web platform?
If a Next.js platform with reusable architecture and modern tooling fits your scope, share the project and I'll respond with options.
Not sure how to engage? See engagement options.
Related Services
See engagement options or contact Bryan to discuss a similar engagement.