Automated Seasonal Hours
J. Rieger & Co.
Four venues. Three seasons. One system that manages itself.
Every venue runs seasonal hours. Three shifts a year across four spaces. All of it lived as static text scattered across the site. Updating hours meant hunting down every instance manually and hoping nothing got missed. The real risk wasn't the effort. It was a guest showing up during hours that were wrong.
Challenge
This wasn't a content problem. It was a structural one. The site was architected in a way that made a routine update unnecessarily risky. Twelve combinations of venue and season, managed entirely by hand.
The Goal
Seasonal hours that update automatically. One place to manage everything. A system the team can trust without checking.
Methods
We audited the existing eat-and-drink page structure first. Four venue sections, each with the same layout but different content and CTA configurations. Hours were embedded inline as static text, with no shared source of truth. A change to one didn't propagate to others.
We evaluated Wix's native content options and confirmed that a CMS-driven approach with Velo automation was the right path. A single queryable data source with server-side season detection, replacing the scattered static blocks entirely.
The Insight
One collection not four. A single data source for all venues and all seasons, with date-based logic that determines what to show and when. Flat, queryable, and entirely in the hands of the content team.
Build Process
The System
All venue hours live in one CMS collection, organized by venue and season. Season boundaries are set using a date picker, not separate number fields. Keeping the experience intuitive for anyone managing the collection. When a season turns, the right hours load automatically.
Key Decisions
Date picker over manual entry. A small UI decision with real impact. Setting a season boundary should feel like picking a date on a calendar, because that's exactly what it is.
Built for expansion. Distillery Hours currently lives as static text in the site footer and across multiple content blocks. The same problem this system solved for the venues. Adding a fifth entry to the existing collection closes that gap without any structural changes.
Impact
Twelve manually maintained static text blocks replaced by one CMS collection. The team updates hours in one place. The site reflects the right information for the right season, automatically — no developer required, no stale content, no guest-facing errors.
URL: jriegerco.com
Takeaway
Static text scattered across a page isn't a content problem — it's an architecture problem. Get the structure right first. The automation follows naturally.
Let's Build Something