Five connected areas designed around audiences, singers, editors, officers, and librarians
The public site is only one part of the work. Over time, recurring needs from singers, board members, editors, and librarians became connected tools for commerce, membership, publishing, and collection management. I designed and developed these systems while also serving as a singing member and board member, so product decisions could be informed by direct observation and regular feedback.
This page goes area by area. Private member and administrative screens are described at the workflow level so the case study can explain the design without exposing member information or operational access.
The public site has to introduce the organization, sell the next concert, preserve its history, recruit singers, support donors, and make recordings and programs discoverable. I created the information architecture, visual system, reusable templates, responsive behavior, and application code as one maintainable foundation rather than a collection of disconnected campaign pages.
Concertgoers, prospective singers, donors, alumni, and returning supporters arrive with different goals. Navigation and page hierarchy prioritize the next useful action without requiring visitors to understand the organization chart.
Reusable page structures, typography, spacing, cards, calls to action, and media treatments let new content feel intentional without requiring a new layout for every concert cycle.
The PHP, MySQL, HTML, CSS, and JavaScript implementation supports clean URLs, shared templates, structured content, search-friendly metadata, forms, integrations, and ongoing releases.
Tickets, recordings, merchandise, and digital products share the Camerata's visual language on the public site while Shopify provides the secure commerce foundation. The experience keeps product discovery connected to concerts and content, then makes the checkout handoff explicit.
Products are retrieved through Shopify's Storefront API and presented inside the Camerata site, allowing product cards and detail views to match the surrounding experience.
Ticket paths begin with the event information people need—date, venue, program, and ticket options—rather than dropping visitors directly into a generic storefront.
Server-side fulfillment logic distinguishes eligible digital products and ticket bundles from physical merchandise, reducing manual handling while keeping order behavior understandable.
The member experience is designed for repeat use by singers and board members. It favors familiar language, direct destinations, and reliable status information over promotional presentation. Authentication and role checks keep member resources separate from public content.
Members can maintain their profile, find other singers, and reach policies, rehearsal materials, and ensemble resources from one authenticated home.
Shared event information and attendance workflows help singers understand what is coming up and help officers see where follow-up is needed.
A Givebutter webhook and reconciliation workflow match dues activity against the Camerata roster. The member database remains the source of identity while payment events update useful status and reminder workflows.
The administrative experience is intentionally denser than the public site. Editors and officers need clear system status, safe bulk actions, and enough context to understand what will change before anything reaches production.
Editors can update page content, media, and homepage campaigns through managed interfaces instead of changing templates or database records directly.
An isolated staging content database supports preview and review. Grouped publishing, revision history, and rollback controls make consequential changes visible and recoverable.
Read-only bridges expose the production roster and library where a preview needs them without letting staging create a conflicting copy of member or catalog records.
The Demetrius Project connects public discovery with the detailed cataloging and lending work required to care for a physical collection. More than 3,300 works and roughly 200,000 scores can be represented without flattening the relationships among compositions, artists, classifications, source collections, and individual copies.
Visitors can search and filter by the attributes that matter for programming and research, then inspect holdings and begin a borrowing request.
Librarians can manage works, artists, classifications, source collections, individual copies, and attached score or audio files without repeating shared information.
The same system supports request review, approval or rejection, checkout, due dates, returns, and borrower communication, keeping public discovery connected to library operations.
The main Camerata case study provides the shorter story of why these systems exist and how my roles as developer, board member, and singer inform the work.