Built fast
This preview was assembled quickly because the architecture is intentionally simple: static HTML, CSS, HTTPS, headers, and no unnecessary backend.
For Brian and Jenna
I built this as a working conversation piece, not a sales brochure.
The point is simple: Santa Fe Brewing already has the beer, spaces, photography, story, and people. I wanted to show how quickly I can construct a cleaner web and ops layer around that without touching payments, replacing BrewOS, or disrupting the media team.
What I noticed
This is mainly a workflow problem, not a talent problem.
Your existing media and photography work are strong. The friction appears to be that routine updates, event pages, location content, and operations information take too much coordination. A better system should reduce repetitive work and keep human approval in place.
- Keep the existing brand voice and photography.
- Give Jenna faster drafts, captions, alt text, and event templates.
- Give managers a cleaner handoff and ops view.
- Protect BrewOS before discussing any replacement.
- Keep cardholder data and payment systems out of this first phase.
Security posture
No payment handling, no POS integration, no customer tracking, no secrets, no Worker code, and no hidden database surface.
Lighthouse-ready
The target is clean Lighthouse posture: performance, accessibility, best practices, SEO, and inspectable security headers. I will only claim final scores after running the live deployed URL.
BTW — the demo itself
This page is also the presentation.
Rather than send a PDF nobody reads, I built the pitch as a small site: guided, private, mobile-readable, HTTPS-ready, and easy to expand into beer pages, venue pages, events, media workflow, and operations dashboards.
Web/media lane
Jenna-facing workflow
One approved event or beer entry can become a page block, newsletter section, social draft, alt text, recap shell, and archive item. The goal is to make creative work reusable without making it generic.
Ops/security lane
Brian-facing pilot
Start with a manager friction map, warehouse placement observations, long-bar lighting/service visibility notes, Raspberry Pi sensor starter, and BrewOS protection checklist.
Recommended next step
14-day prototype sprint — $3,500
Small enough to approve, concrete enough to judge, and useful even if you decide not to continue.
- Customize this demo with approved SFBC images/copy.
- Map website and content-update friction.
- Build Jenna's first reusable content workflow.
- Map manager workflow pain points.
- Outline BrewOS backup/isolation/reporting path.
- Deliver a short roadmap with priorities and costs.