Case study

Bent Beam Brewing

A taproom site the staff run themselves - what is pouring right now, who is playing this weekend, which food truck is parked outside - without a developer touching it.

Sector
Craft brewery and taproom
Location
Canton, NY
Year
2026
A longer view of the Bent Beam Brewing homepage showing the hero followed by the current tap list.
Bent Beam Brewing as it appears today at bentbeambrewing.com.

The problem

A new brewery's information changes faster than anyone can email a web developer about it. The tap list turns over weekly, food trucks and live music are booked days ahead, and hiring happens in bursts. Anything that needed a developer in the loop would simply go stale, and a stale taproom page costs walk-in traffic. Alcohol sales also carry a legal obligation to gate the site by age.

The approach

Everything that changes often was moved behind an editor the owners use from a phone. Everything that has to be right every single time - the age gate, form handling, the open/closed status - was pushed to code that runs at the network edge, where it cannot be forgotten.

What was built

  • Age verification enforced at the edge before any page content is served, not by a script the visitor can skip
  • A tap list the staff update themselves, with pour status, ABV, and tasting notes
  • Events and food-truck schedule, published from the same editor
  • Hours-aware status that shows open or closed against the real schedule and time zone
  • Job postings with an application form that accepts resume and cover-letter attachments
  • Contact form with spam protection, delivered to email and to a private inbox
  • Location map and directions
The Bent Beam Brewing events page listing upcoming live music and food truck dates.
The Bent Beam Brewing homepage on a phone-sized screen.
The same site on a phone. Most visitors arrive this way.

What makes it work

Details that mattered here

Staff-editable, developer-free

Tap list, events, hours, and posts are all edited through a browser-based editor. No developer, no ticket, no waiting.

Legal age gate at the edge

The gate runs before the page is delivered, so the content is never sent to an unverified visitor in the first place.

Built for a phone first

Most taproom traffic is someone standing on the sidewalk deciding where to go. The layout is designed for that moment.

Seven independent services

Age gate, tap list, events, contact, applications, mail handling, and scheduled jobs each run on their own so one failure cannot take the site down.

Where it landed

The owners publish a new tap list in under a minute from behind the bar. Every change still passes the full accessibility, performance, and security check before a customer sees it.

Next step

Want something like this?

Tell me what the business does and what is not working online right now. I will tell you honestly whether I am the right person for it.