A brand with personality. A platform with one too.

UX Lead on Dogfish Head’s Sitecore XM Cloud migration. One site for a brewery, distillery, restaurant, brewpub, inn, events, and merch — without losing what makes them them.

live site → dogfish.com

ux lead multi-line-of-business cms migration 2024–2025 at verndale

challenge

Dogfish Head’s brand is warm, weird, and specific. The old site was polished but generic.

The harder problem: this isn’t just a beer brand. One site has to carry brewery, distillery, restaurant, brewpub, inn, events, and merch — and serve as a foundation for other Boston Beer Company brands.

Dogfish Head homepage after redesign after
Dogfish Head homepage before redesign before

homepage — before & after redesign

Dogfish Head design system overview
system overview — product detail, events, cocktails, brand expression

strategic foundation

Boston Beer commissioned third-party qualitative research with younger craft beer drinkers before our engagement started. Findings shaped the brief: Dogfish Head was at an inflection point with declining craft consumption among LDA drinkers in their 20s.

The Focus Session named the operating principle, quoting DFH co-founder Sam Calagione: “Marketing is less about what your product is or does than what it stands for.” That became the IA rule: Why beats How beats What. Stories first. Products second. Transactions third.

Dogfish Head — Information Architecture
Navigation system redesign · Multi-line-of-business IA · Sitecore XM Cloud migration
UX Lead: Will Bruno · Verndale for Dogfish Head / Boston Beer Company · 2024–2025  — full notes →
Primary nav items
6 flat7 + utility row
Lines of business in IA
1 (brewery)4 (+ distillery, inn, restaurant)
Nav naming options explored
6 frameworks
Mega menu system
NoneTwo-panel L1 → L2
Page templates
Ad hoc19 designed
Dogfish Head information architecture after redesign after — v6.0
Dogfish Head information architecture before redesign before
Change 01
Brand voice applied to navigation

“Blog” became “Blogfish.” FishFinder became a named utility-nav anchor. Off-Centered Society moved from buried footer to persistent utility row. The navigation itself became a brand artifact.

Change 02
Four lines of business surfaced

Brewery, distillery (Spirits), restaurant (Chesapeake & Maine), brewpub (Brewings & Eats), and the Inn each got distinct IA presence under Hospitality & Visit — not folded into a generic Locations bucket.

Change 03
Drinks mega menu introduced

Flat product list replaced with a two-panel mega menu: L1 (Brewery / Spirits / Canned Cocktails / Recipes) → L2 columns. Spirits and Canned Cocktails got first-class nav presence for the first time.

Change 04
Contact & Support separated

FAQ, contact forms, and OCS-specific support were buried in About Us. Now a standalone primary nav item — reducing cognitive load and giving support content a findable home.

Change 05
Utility row created for brand programs

FishFinder, Newsletter Sign-Up, Off-Centered Society, and Boston Beer Brand links moved to a persistent utility row — giving brand programs top-of-page presence without competing for primary nav slots.

Deep Dive 01

Naming the Navigation: Six Frameworks, One Decision

Navigation naming is IA strategy made visible. For a brand like Dogfish Head — warm, weird, and specific — generic labels like “Blog” read as borrowed from a different site. Six distinct naming frameworks were evaluated against two criteria: findability (can a first-time visitor get oriented?) and brand fidelity (does it sound like Dogfish Head?). The winning approach was mostly noun-based with selective brand voice applied where it added meaning rather than confusion.

Navigation naming — six frameworks evaluated
6
Naming frameworks evaluated before final nav structure locked
+1
Primary nav items added (Contact & Support separated from About Us)
+4
Utility row items surfaced — brand programs given top-of-page presence
1
Brand-voice nav label applied where it added meaning — Blogfish
Deep Dive 02

Drinks: From Beer Catalog to Multi-Product Mega Menu

The original Drinks nav was beer-only — a flat list of Core Beers, Rarities & Archives, and a Release Calendar. It treated Dogfish Head as a single-product brewery. By the time of the redesign, DFH also operated a full spirits line, canned cocktails, and a recipes section. The mega menu redesign introduced a two-panel L1 → L2 system: category selection on the left, contextual content columns on the right — keeping the beer catalog rich without crowding out the distillery and cocktail lines.

Drinks mega menu — before flat dropdown vs. after two-panel system
1 → 4
Product categories with dedicated nav presence (Brewery, Spirits, Cocktails, Recipes)
2-panel
Scalable mega menu system — any new product line slots in without nav restructure
Evergreen
Year-specific “2024 Release Calendar” label eliminated — nav stays accurate without annual updates
Dual
FishFinder anchored in both utility row (persistent) and Brewery panel (contextual)

deep dive 01 — one platform, four lines of business

Most beer brand sites are catalogs with a contact page. This one had to support Chesapeake & Maine restaurant, Brewings & Eats brewpub, the Dogfish Head Inn, ongoing events, brewery tours, the Beer & Benevolence community program, and the merch shop.

The decision: don’t reinvent UX patterns for restaurant reservations or inn bookings. The brand does the work, not the patterns. One template family. Distinct brand codes per surface.

Dogfish Head Visit page — four coastal Delaware locations
visit — gateway to four coastal delaware properties
Weddings and Private Events page
weddings & events — venue photography, availability, inquiry flow
Brewings and Eats restaurant page
brewings & eats — restaurant + brewpub experience
Alternate Takes whiskey collection page
alternate takes — small-batch whiskey storytelling

deep dive 02 — two audiences, one IA

The Experience Strategy on a Page made the calculus explicit: secure the regional fan base through activation, while growing the national audience through engagement.

Activation = lines of business and innovative brews. Growth = storytelling and the Fish Finder, the named beer-locator that doubles as brand expression. Same nav, different jobs.

Dogfish Head x Grateful Dead American Beauty collaboration page
grateful dead collaboration — brand partnership as design moment
Dogfish Head product family across IPAs, sours, lagers, seasonals
product family — one system across every beer style

deep dive 03 — system primitives

Nineteen templates and eleven product themes only work if the underlying primitives hold. Forms aren’t just forms — they’re base, error, success as named states. Empty results are a designed surface, not a leftover.

Search results page with results
search results — with results
Search results page with no results
without — designed as a path forward
tension

Warm and weird, structured and scalable.

The temptation in a project this big is to choose: lean fully into the brand’s eccentricity and lose the system, or build a clean scalable platform and lose the brand. The work was about refusing that choice.

Coastal Grit was the visual frame Brittany Janeczek named for it — coastal nautical softness plus rugged working-brewery toughness.

Every screen had to feel like the brand — not just reference it.
— design intent, dogfish head

result

19

page templates designed across desktop and mobile.

11

product page color themes for line-of-business variation.

live

shipped on Sitecore XM Cloud at dogfish.com.

key decisions

Three calls that shaped the site.

Two audiences with one IA.

Regional fans get activation surfaces — events, hospitality, drops. National fans get engagement surfaces — storytelling, the Fish Finder, articles. Same nav, different jobs.

Lines of business as content, not microsites.

Restaurant, inn, brewpub, events, donations all share template structure. The differentiation lives in brand expression, not the pattern.

System primitives, not screens.

Form base / error / success. Search with / without. Navigation as a four-state system. The 19 templates only hold up because the primitives underneath are explicit.

Let's make something work.

Boston & remote · Open to full-time & contract

will.a.bruno@gmail.com