More than a new website. A new way to run the show.

The starting point

Keep the character. Rethink the tools.

The original site already carried the essentials: menus, venue information, and a busy live-music calendar. Events were entered manually in WordPress each week, with a calendar plugin handling their public presentation.

The work went well beyond a fresh coat of paint. Repeat bookings, last-minute changes, menu updates, artist information, and community photos all needed a place in the plan. Live music has enough moving parts already.

The heart of the site

A calendar that understands the gig.

Today’s lineup, the full calendar, and event details draw from the same schedule. Guests can browse by week, month, or a specific date; phone layouts turn the calendar into readable day-by-day listings.

Behind the scenes, staff can create single bookings or weekly and monthly repeats, review the dates before saving, and change an individual performance without losing the rest of the series. Cancellations and postponed dates have explicit states, while event links and attached photos retain their identity as details change.

Dedicated tools handle tap takeovers and wine tastings, including the brewery or winery details and accompanying music. Private-event closures appear clearly in the public calendar so guests know when the venue is unavailable.

Useful every day

Menus that work on a screen and on paper.

Food and coffee menus are structured content, with names, descriptions, prices, options, and section notes that staff can maintain. Guests can search the food menu and narrow it by category instead of hunting through a long page.

The printable food menu uses the same content and includes the full menu, even if a visitor has been filtering it on screen. Artist profiles give performers their own place on the site, connecting the schedule with biographies and published photos.

Made for the community

Turn a night out into part of the story.

Guests can share a photo without creating an account. Staff can print a general photo-sharing QR flyer or one for a specific performance, so the photo form already knows which event the guest attended.

Publication consent and staff review are built into the process. Pending photos stay private; approved images can appear in the gallery and relevant artist or event pages. Staff can organize the collection and pin selected photos to the top.

Guests get to contribute to the story, and the team gets the final say on what goes public. Both matter.

The application behind the website

Give people the tools their role needs.

Invited staff sign in with an email code and see the tools assigned to them. Menu maintainers, event organizers, and photo reviewers can work in their own areas; managers and owners handle the appropriate account permissions.

Changes carry a readable history, and safeguards check for conflicting edits before saving over someone else’s work. Scheduled announcements let staff post a timely message with an expiration, while image controls keep routine updates out of the codebase.

The custom stack uses Next.js for the site and staff application, Supabase for database, authentication, and storage, and a GitHub-to-Vercel deployment workflow. The technology supports the everyday jobs: update a price, adjust a booking, approve a photo, or tell guests what changed.

A careful migration

Bring the history along.

Existing bookings came across from the old calendar’s published data. Repeat imports avoided duplicates and preserved staff edits, event identities, and photo associations. Legacy page, event, and image URLs redirect to their new destinations, so old links still have somewhere useful to go.

The new site launched on October 15, 2026, at Janey’s existing domain, cavecreekazmusic.com. Public pages include search metadata, event information for search engines, and share images with event details. Launch checks covered the live site, staff sign-in, inquiry emails, and guest photo submissions; the existing email setup stayed in place through the move.