/* Fieldstone Products — brand styling (cream #F8F1E5 / dark brown #3F2620)
   v1.2.0: grouped menu-list archive (Wix layout), sticky brown header band,
   brown footer band, Roboto headings + humanist sans body (matching the
   theme's redesign fonts; strong fallbacks if the theme fonts are absent).
   v1.2.1: rotating-banner slide rules (retired in v1.4.8 — the banner
   is now one message per day; the .fs-banner-daily rule is below).
   v1.2.3: Nutrition Facts label rules (.fs-nutrition-facts, below).
   v1.2.4: header badge logo + footer rating line (below), and the
   [fs_hero] / [fs_reviews] rules at the end of this file — those two are
   deliberately NOT scoped to .fs-body, because the shortcodes render on
   theme pages (the Home page), where .fs-body is never present.
   v1.2.5: header restyled to match the theme header (badge centred on
   top, nav centred beneath — .fs-header / .fs-brand-logo below), the
   dietary filter box gains its "Dietary" header + 2x2 grid
   (.fs-filters-title / .fs-filters-grid), category archives gain the
   faded photo header band (.fs-cat-header), and the footer social icon
   row (.fs-social) sits above the rating line.
   v1.2.6: larger, bolder type throughout (body 18px/1.65, menu rows
   ~20px/600, nav 17px/600, footer ~17px/1.6 — the Nutrition Facts
   label's sizes are untouched on purpose); the header nav gains the
   Menu dropdown (.fs-subnav) and the mobile sandwich toggle
   (.fs-nav-toggle); the footer becomes three columns (.fs-footer-cols).
   v1.2.7: the footer goes full Cabin-style — the three column
   headings uppercase + letterspaced (.fs-footer-title), all three
   columns centre-aligned at every width (.fs-footer-cols), and the
   reviews column trades the rating line + featured quote for five
   large gold stars over the review count (.fs-footer-stars). The
   same version raises the whole type scale again for readability
   (the owner reads her Cabin site's generous sizes as the target):
   body 20px/1.7, nav 18px/600, menu names 22px/600, prices 19px/600,
   descriptions 17px, product pages 19px (.fs-single), footer
   18px/1.65 with 21px headings, banner 18px/600 (its inline style in
   quick-edit.php moves with it), review quotes 21px — and no weight
   under 400 anywhere. The Nutrition Facts label's sizes are still
   untouched on purpose.
   v1.2.8: the footer is compressed — the Site Map stays visible with
   a <details> category toggle on its Menu entry (.fs-footer-menu),
   Google Reviews puts its stars and count on one line
   (.fs-footer-review-line), the footer columns run at line-height
   1.45, and the footer loses roughly a third of its vertical
   padding — and the type scale rises again, phone-first: body
   22px/1.7 at weight 600, menu names 24px/700, prices 20px/700,
   descriptions 18px/600, product pages 21px, nav 19px/700, banner
   19px/700, review quotes 22px/600, footer 19px/600. No max-width
   media query below reduces any font size under its desktop value.
   The Nutrition Facts label's sizes remain untouched.
   v1.2.9: footer micro-adjustments — the Site Map links'
   no-underline rules are raised in specificity (.fs-footer
   .fs-footer-links a / .fs-footer .fs-footer-sublist a), the
   "Read Reviews" link pulls up to a ~2px gap beneath the
   stars-and-count line, and the Come Visit column
   (.fs-footer-visit) is tightened at the top (heading → Ocean
   Park → address at ~2-3px gaps) with its address on two lines.
   The same version adds the [fs_photoscroll] Instagram photo
   strip rules at the end of this file.
   v1.3.2: two footer tweaks — the dropdown triangle on the Site Map's
   Menu entry is removed (the word "Menu" itself becomes the
   <details> summary toggling the category links, and no longer
   links to /products/ in the footer), and the Come Visit phone
   line (.fs-footer-phone) gets white-space:nowrap so the number
   can never wrap mid-number in the narrow footer column.
   v1.3.3: margins + the last of the small text. .fs-main widens
   (max-width 1100px → 1180px) and its side padding becomes an
   explicit 32px on desktop and 20px at ≤760px (the category
   photo header's negative margins move with it, so the band
   still bleeds to the content edges). The remaining below-body
   copy rises to body scale: the hero panel paragraph
   (.fs-hero-text) 19px → 22px/600 (its ≤640px rule too), menu
   item and group descriptions (.fs-item-desc / .fs-group-desc)
   18px → 20px/600, category nav links (.fs-catnav a) 19px →
   20px/700, the hero button (.fs-hero-btn) 17px → 19px/700 and
   the review byline (.fs-review-by) 16px → 19px/600. Left on
   purpose: the Nutrition Facts label, the footer (19px), the
   dietary filter controls and the 14px dietary badges / © line
   (badge and footer microcopy).
   v1.3.4: on phones (≤640px) the frosted hero panel shrinks so
   more of the photo shows — width 78% of the slide (still
   centred), padding 24px 20px → 12px 14px, gaps tightened
   (title 6px → 4px, script 10px → 6px, paragraph 20px → 12px),
   title 44px → 30px, script 34px → 26px, paragraph 22px →
   20px/600, button padding 12px 26px → 10px 20px. Desktop and
   tablet hero rendering is unchanged.
   v1.3.5: owner walkthrough corrections. (A) The product pages
   go back to the pre-escalation (v1.2.4-era) type scale: body
   22px/1.7/600 → 18px/1.65 at the inherited weight, the
   .fs-single size rule is removed (product pages inherit the
   body again), menu names 24px/700 → 20px/600, menu prices
   20px/700 → 18px/600, item descriptions 20px/600 → 16px,
   group descriptions 20px/600 → 17px, category nav 20px/700 →
   19px/600, ingredients 21px/600 → 17px, the single-page price
   22px/700 → 22px/600, and the hero panel paragraph's base
   rule 22px/600 → 19px (its ≤640px panel rule keeps v1.3.4's
   20px/600, so the weight moves into that rule). Deliberately
   kept: the banner (19px/700), the header nav links
   (19px/700), the footer (19px/600), the reviews ticker, the
   Nutrition Facts label, the v1.3.3 .fs-main margins and the
   photoscroll. (B) On mobile the category subnav is gated to
   the open sandwich panel (.fs-nav.is-open .fs-subnav), so the
   five categories show inside the open panel with no further
   tap; desktop hover is untouched. (C) The header nav's Menu
   link gains a small caret (.fs-nav-caret) flagging the
   dropdown, on desktop and mobile alike.
   v1.4.0: the Cabin-parity build adds two rule blocks at the end
   of this file — the reviews band (.fs-rband..., a full-width
   dark-brown marquee of the top 10 Google reviews behind a
   centred rating summary cell) and the photo carousel
   (.fs-carousel..., one panoramic photo at a time with white
   square arrows and a dot per photo). Nothing above changes.
   v1.4.1: the single page's dietary flags lose their pill
   boxes — .fs-badges / .fs-badge are retired and replaced by
   .fs-dietary-list, a plain bulleted list (16px, ordinary
   bullets, no borders or fills); .fs-badge was used only by
   the single template, and the archive's Dietary filter
   checkboxes (.fs-filters-grid) are a separate control with
   their own rules, untouched. The ingredient list
   (.fs-ingredients) drops 17px → 15px.
   v1.4.4: the Nutrition Facts label scales down ~×0.85 (see
   the .fs-nutrition-facts block below) — the one deliberate
   exception to this file's long-standing "label sizes
   untouched" rule, at the owner's direction; only the scale
   changes, never the label's structure or content rules.
   v1.4.6: the hero panel goes a little transparent at the
   owner's direction — .fs-hero-panel's cream background drops
   rgba(248,241,229,0.92) → 0.75 and its backdrop blur softens
   6px → 4px, so the slideshow photo shows through somewhat
   while the dark-brown panel text stays clearly legible. The
   panel background lives only in that one rule (the ≤640px
   rule sets just width/padding), so both widths move together.
   v1.4.7: the header goes Cabin-style — cream at rest with the
   brown badge and brown nav links (the brown band is gone),
   inverting to the brown bar with the cream badge and cream
   nav links once assets/fs-sticky-header.js adds .is-stuck to
   the .fs-site-header element on scroll. The logo swap rules
   sit with the .fs-brand-logo rules below; the state rules
   are scoped to .fs-site-header so the theme header, rebuilt
   to the same contract classes, inverts identically. The
   rotating banner is unchanged — already brown #3F2620 with
   cream text (its rule below and its inline style agree).
   v1.4.9: the hero panel goes more transparent at the owner's
   direction — .fs-hero-panel's cream background drops
   0.75 → 0.55 and its backdrop blur softens 4px → 3px, so
   the photo behind the panel reads more clearly. Panel size,
   position and text are untouched.
   v1.4.10: on phones (≤760px) the homepage's picture blocks
   run full-bleed, edge to edge — .fs-hero, .fs-rband and
   .fs-photoscroll break out of the theme content's 20px side
   padding to the screen edges (the block at the very end of
   this file). Desktop rendering is untouched.
   v1.4.11: the photo strip becomes a manual gallery — the
   marquee rules are deleted and .fs-photoscroll becomes a
   scrollable row (.fs-photoscroll-row, scrollbar hidden) with
   arrow buttons at its far edges; the block sits beside the
   other shortcode rules below. Nothing in the strip moves
   on its own.
   v1.4.12: the hero panel goes one notch more transparent at
   the owner's direction — .fs-hero-panel's cream background
   drops 0.55 → 0.45, the backdrop blur stays at 3px, and
   nothing else changes (panel size, position, padding, text
   and the ≤640px width/padding rule are all untouched).
   v1.4.13: the photo strip's arrow buttons come off at the
   owner's direction — she tested on her phone and the row
   scrolls fine with a finger swipe, so the buttons added in
   v1.4.11 are unnecessary. Their rules below are deleted
   outright; the scrollable row, hidden scrollbar, daily
   start and the ≤760px full-bleed rule are untouched, and
   the hero panel stays at 0.45.
   v1.4.14: a fixed full-site backdrop — the bread-shelves
   photo (assets/fs-page-bg.jpg) sits fixed behind every
   page under a cream wash while the content scrolls
   vertically over it. The rules are the block at the very
   end of this file. Nothing above changes. */
.fs-body { background:#F8F1E5; color:#3F2620; font-family:'Nunito Sans', 'Segoe UI', 'Helvetica Neue', Arial, sans-serif; margin:0; font-size:18px; line-height:1.65; }
.fs-body h1, .fs-body h2, .fs-body h3, .fs-brand { font-family:'Roboto', 'Helvetica Neue', Arial, sans-serif; }
/* Header (v1.2.5, "seamless"): matches the theme header — the badge
   centred at the top, the nav centred on its own row beneath — so
   moving between a theme page and a product page shows the same
   header. The templates' markup is unchanged (brand, then nav); the
   column flex does the centring, and the text-brand fallback centres
   the same way when no badge is uploaded.
   v1.4.7: the brown band is gone. AT REST the header is cream like
   the page — a hairline brown rule beneath it, the badge in brown,
   the nav links brown. ON SCROLL, when the sticky header pins to
   the top, fs-sticky-header.js adds .is-stuck and the header
   inverts: brown bar, cream badge, cream nav links (the state
   rules sit directly below the logo rules, scoped to the contract
   class .fs-site-header so the theme header follows suit). */
.fs-header { position:sticky; top:0; z-index:50; background:#F8F1E5; border-bottom:1px solid rgba(63,38,32,.16); display:flex; flex-direction:column; align-items:center; gap:6px; padding:8px 24px 6px; text-align:center; }
.fs-brand { font-size:26px; font-weight:900; color:#3F2620; text-decoration:none; }
.fs-nav { display:flex; flex-wrap:wrap; justify-content:center; gap:4px 18px; }
.fs-nav a { color:#3F2620; text-decoration:none; font-size:19px; font-weight:700; }
.fs-nav a:hover { text-decoration:underline; }
/* Menu caret (v1.3.5): a small triangle after the word "Menu" in the
   header nav flags the category dropdown — desktop and mobile alike.
   It sits inside the Menu link, so it inherits the link's colour and
   weight, and sizes off the link text so it scales with it. */
.fs-nav-caret { font-size:.7em; margin-left:3px; }
/* Menu dropdown (v1.2.6): the Menu item's five category links sit in a
   brown panel under the nav row, shown on hover or keyboard focus.
   Pure CSS — no script involved on desktop. */
.fs-nav-item { position:relative; display:inline-flex; }
.fs-subnav { position:absolute; top:100%; left:50%; transform:translateX(-50%); z-index:60; min-width:230px; display:none; flex-direction:column; padding:8px 0; background:#3F2620; border:1px solid rgba(248,241,229,.35); border-radius:0 0 8px 8px; box-shadow:0 10px 24px rgba(38,24,18,.35); }
.fs-nav-item:hover .fs-subnav, .fs-nav-item:focus-within .fs-subnav { display:flex; }
.fs-subnav a { padding:7px 18px; white-space:nowrap; font-family:'Caveat', 'Segoe Script', 'Comic Sans MS', cursive; font-size:26px; font-weight:700; line-height:1.15; }
/* v1.4.7: the dropdown panel stays brown in BOTH header states
   (a brown stamp under the cream header; a continuation of the
   brown bar once stuck), so its links stay cream on desktop.
   The mobile open panel is transparent, so its subnav links
   follow the header state instead — see the ≤861px rules. */
.fs-subnav a { color:#F8F1E5; }
.fs-subnav a:hover { background:rgba(248,241,229,.12); text-decoration:none; }
/* Theme-header dropdown (v1.4.23): pages using the theme header
   (homepage, About, Contact) build their Menu dropdown from the
   WordPress navigation block, not .fs-subnav. Its submenu items
   take the same Caveat face so the dropdown reads the same
   site-wide. Panel colour is the block's own (white) and is
   not touched here. */
.wp-block-navigation__submenu-container .wp-block-navigation-item__content { font-family:'Caveat', 'Segoe Script', 'Comic Sans MS', cursive; font-size:26px; font-weight:700; line-height:1.15; }
/* Theme-header overlay collapse (v1.4.24): in the navigation
   block's OPEN mobile overlay, the Menu submenu starts hidden
   until the parent item is tapped (assets/fs-nav-collapse.js
   toggles .fs-sub-open on it). Desktop dropdowns never carry
   .is-menu-open, so they are unaffected. */
.wp-block-navigation__responsive-container.is-menu-open .wp-block-navigation-submenu .wp-block-navigation__submenu-container { display:none; }
.wp-block-navigation__responsive-container.is-menu-open .wp-block-navigation-submenu.fs-sub-open .wp-block-navigation__submenu-container { display:block; }
/* Mobile sandwich (v1.2.6): below ~861px the nav row hides and a
   three-line button pinned to the top right of the header band (level
   with the badge) toggles the nav as a stacked panel. The toggle's
   script is the small inline block at the foot of both templates.
   v1.3.5: the Menu item's category subnav is gated to the OPEN panel
   (.fs-nav.is-open .fs-subnav) — hidden in every other mobile state,
   and when the panel opens the five categories are simply there,
   stacked beneath "Menu" with no hover and no further tap. Desktop
   hover/focus behaviour above is untouched. */
.fs-nav-toggle { display:none; }
@media (max-width:861px) {
  .fs-nav { display:none; }
  /* v1.4.29 (THE CABIN RECIPE): the open panel is a drop-down
     LAYER under the header bar -- position:absolute at top:100%
     of the header -- instead of a part of the bar itself. The
     bar's size never changes when the menu opens, so the badge
     keeps its size, the sandwich never moves (its centred spot
     in the unchanging bar is its only spot), and the page
     underneath is not pushed around. The panel takes the
     header's own colours (cream at rest, brown once stuck),
     its rows keep their comfortable pre-compression sizes,
     and the screen-height cap with internal scroll remains
     only as a last resort for very short screens.
     v1.4.30: flex-wrap:nowrap and justify-content:flex-start
     are set EXPLICITLY on the open rule -- the base .fs-nav
     rule carries flex-wrap:wrap and justify-content:center
     (right for the desktop row), and with wrapping left on,
     an open column taller than the cap wrapped into
     side-by-side columns and scattered the items across the
     screen (owner's phone, 2026-11-01). A column must never
     wrap. */
  .fs-nav.is-open { display:flex; flex-direction:column; flex-wrap:nowrap; justify-content:flex-start; align-items:center; gap:10px; position:absolute; top:100%; left:0; right:0; z-index:60; padding:6px 16px 14px; background:#F8F1E5; border-bottom:1px solid rgba(63,38,32,.16); box-shadow:0 12px 24px rgba(38,24,18,.18); max-height:calc(100dvh - 96px); overflow-y:auto; }
  .fs-site-header.is-stuck .fs-nav.is-open { background:#3F2620; border-bottom-color:transparent; }
  .fs-nav-toggle { display:block; position:absolute; top:50%; right:16px; transform:translateY(-50%); background:transparent; border:0; padding:10px 6px; cursor:pointer; }
  /* v1.4.7: the sandwich inverts with the header — brown lines on
     the cream header at rest, cream lines once stuck. */
  .fs-nav-toggle span { display:block; width:26px; height:3px; margin:5px 0; border-radius:2px; background:#3F2620; }
  .fs-site-header.is-stuck .fs-nav-toggle span { background:#F8F1E5; }
  .fs-nav-item { display:flex; flex-direction:column; align-items:center; }
  .fs-subnav { display:none; }
  .fs-nav.is-open .fs-subnav { position:static; transform:none; display:none; min-width:0; padding:2px 0 0; background:transparent; border:0; box-shadow:none; align-items:center; }
  /* v1.4.24: in the open panel the categories start collapsed;
     tapping Menu toggles .fs-sub-open (template inline script)
     and the caret flips to show the state. */
  .fs-nav.is-open .fs-nav-item.fs-sub-open .fs-subnav { display:flex; }
  .fs-nav.is-open .fs-nav-caret { display:inline-block; }
  .fs-nav.is-open .fs-nav-item.fs-sub-open .fs-nav-caret { transform:rotate(180deg); }
  /* v1.4.30: no tap-focus outline box around the sandwich
     button or the open Menu link (the owner's screenshots
     showed the box around Menu after tapping it). */
  .fs-nav-toggle:focus, .fs-nav.is-open .fs-nav-item > a:focus { outline:none; }
  /* v1.4.7: inside the open mobile panel the subnav sits on the
     header itself (transparent panel), so its links follow the
     header state — brown at rest, cream once stuck — not the
     desktop dropdown's always-cream. */
  .fs-subnav a { padding:4px 10px; font-size:25px; opacity:.92; color:#3F2620; }
  .fs-site-header.is-stuck .fs-subnav a { color:#F8F1E5; }
  /* v1.4.29: the v1.4.26-1.4.28 open-state compaction block stood here (badge shrink, tight rows, toggle pinning, menu-open class keying) -- REMOVED under the Cabin recipe; the open panel is the layer rule above and nothing about the header restyles when it opens. */
}
.fs-main { max-width:1440px; margin:0 auto; padding:24px 32px; }

/* Archive page title centred on phones (v1.4.50, owner request):
   the bare <h1> direct child of .fs-main is the all-products title
   ("Our Products"); category titles live inside the photo band and
   desktop keeps the left alignment. */
@media (max-width:768px) { .fs-main > h1 { text-align:center; } }
/* Small screens (v1.3.3): explicit 20px side margins — the content
   never runs to the phone's edges. The category photo header's
   negative margins shrink to match, so its band still bleeds
   exactly to the content edges at this width too. */
@media (max-width:760px) {
  .fs-main { padding:20px; }
  .fs-cat-header { margin:-20px -20px 18px; }
}
/* Product pages: the single template's main carries .fs-single, but
   since v1.3.5 the class sets no size of its own — the single page's
   text (description, crumb, ingredients below) inherits the 18px
   .fs-body base, as it did before the v1.2.8–v1.3.3 escalation. */
.fs-main h1 { font-size:34px; font-weight:900; margin:8px 0 4px; }
.fs-main h2 { font-size:24px; font-weight:700; margin-top:28px; }
.fs-price { font-size:22px; font-weight:600; margin:4px 0; }
/* Product page title row (v1.4.43): the price sits beside the
   name, baseline-aligned, and the name runs smaller than the
   shared 34px page headings -- product pages only. The
   !important on the size is load-bearing (v1.4.45): the
   site's Additional CSS pins every H1 at 2.375rem !important
   under 768px, which silently swallowed the v1.4.43/v1.4.44
   sizes on phones; this rule wins on specificity. Do not
   drop the !important without checking that rule first. */
.fs-single-head { display:flex; align-items:baseline; gap:16px; flex-wrap:nowrap; }
/* v1.4.46: the name flexes and the price is fixed, so a name
   long enough to wrap wraps within its share of the row and
   the price stays on the first line instead of dropping below. */
.fs-single-head h1 { flex:1 1 auto; min-width:0; }
.fs-single-head .fs-price { flex:0 0 auto; }
.fs-single h1 { font-size:22px !important; }

/* Single product page, desktop two-column top (v1.4.48, PC pass):
   photo in a 360px column (photos are 300px originals -- kept close
   to native), dietary list and description beside it; crumb and
   name/price span both columns; Ingredients and Nutrition follow
   full width. Phone widths keep the stacked template order. */
@media (min-width:769px) {
  .fs-single { display:grid; grid-template-columns:360px minmax(0, 1fr); grid-template-rows:auto auto auto 1fr; column-gap:36px; }
  .fs-single .fs-crumb, .fs-single .fs-single-head { grid-column:1 / -1; }
  .fs-single .fs-photo { grid-column:1; grid-row:3 / span 2; width:100%; margin:0; align-self:start; }
  .fs-single .fs-dietary-list { grid-column:2; grid-row:3; align-self:start; }
  .fs-single .fs-desc { grid-column:2; grid-row:4; align-self:start; }
  .fs-single > h2, .fs-single .fs-ingredients, .fs-single .fs-nutrition-facts, .fs-single .fs-allergy { grid-column:1 / -1; }
}
.fs-photo { max-width:100%; height:auto; border-radius:8px; margin:12px 0; }
/* Dietary flags on the single page (v1.4.1): a plain bulleted
   list under the title/price — ordinary text and • bullets, no
   borders, fills or pill shapes, so nothing about them reads
   as selectable. (Before v1.4.1 these were .fs-badge pills;
   the class was used only here. The archive's Dietary filter
   checkboxes are unrelated and keep their own rules below.) */
.fs-dietary-list { list-style:disc; margin:8px 0; padding-left:1.3em; font-size:16px; }
.fs-dietary-list li { margin:2px 0; }
.fs-desc { font-size:18px; font-weight:900; }
.fs-catnav { margin:14px 0 6px; text-align:center; }
.fs-catnav a { color:#3F2620; margin-right:14px; text-decoration:none; font-size:19px; font-weight:600; }
.fs-catnav a.fs-on { font-weight:bold; text-decoration:underline; }
.fs-filters { margin:10px 0 20px; padding:12px 14px; border:1px solid #3F2620; border-radius:8px; background:#fff8ee; }
/* Dietary filter box (v1.2.5): "Dietary" is the box's header, and the
   four flags sit in a two-column grid so the rows and columns line up
   (Gluten/Dairy over Egg/Meat, per the template's display order). */
.fs-filters-title { font-family:'Roboto', 'Helvetica Neue', Arial, sans-serif; font-weight:700; font-size:19px; margin:0 0 8px; text-align:center; }
.fs-filters-grid { display:grid; grid-template-columns:repeat(2, max-content); gap:6px 28px; margin:0 0 12px; }
/* PC only (v1.4.47): one centred row of four, so the options
   sit centred like the title and Apply button instead of
   stranding in a 2x2 cluster at the left of the wide box.
   Phone widths are deliberately untouched. */
@media (min-width:769px) { .fs-filters-grid { grid-template-columns:repeat(4, max-content); justify-content:center; gap:6px 36px; } }

/* Dietary filter box, PC tightening (v1.4.49): narrower box, bolder
   and larger text inside -- desktop only, mobile view unaltered. */
@media (min-width:769px) {
  .fs-filters { max-width:880px; margin-left:auto; margin-right:auto; padding:16px 20px; }
  .fs-filters-title { font-size:21px; font-weight:900; }
  .fs-filters-grid label { font-size:18px; font-weight:700; }
  .fs-filters-grid input { width:18px; height:18px; }
  .fs-filters button { font-size:17px; font-weight:700; padding:8px 22px; }
}
.fs-filters-grid label { font-size:16px; display:flex; align-items:center; gap:6px; }
@media (max-width:480px) { .fs-filters-grid { grid-template-columns:1fr 1fr; gap:6px 12px; } }
/* v1.4.2: the header reads "Select Your Dietary Options" (centred,
   above) and the submit button reads "Apply", centred at the
   bottom of the box via .fs-filters-actions ("Apply"); the Clear link, when a
   filter is active, sits beside the button in the same centred row. */
.fs-filters-actions { text-align:center; margin:0; }
.fs-filters button { background:#3F2620; color:#F8F1E5; border:0; border-radius:6px; padding:6px 16px; cursor:pointer; font-size:16px; font-weight:600; }
.fs-clear { margin-left:12px; color:#3F2620; }
/* Grouped menu list (v1.2.0) — replaces the card grid. */
.fs-menu-group { margin-bottom:10px; }
.fs-menu-group h2 { color:#3F2620; border-bottom:2px solid #3F2620; padding-bottom:4px; font-size:26px; font-weight:900; }
.fs-group-desc { margin:2px 0 6px; font-size:19px; font-weight:900; color:#6b554b; }
.fs-menu { list-style:none; margin:0 0 24px; padding:0; }
.fs-item { display:flex; flex-direction:column; gap:6px; padding:10px 6px; border-bottom:1px solid #d8c9b4; text-decoration:none; color:#3F2620; }
.fs-item-top { display:flex; align-items:center; gap:14px; width:100%; }
.fs-item:hover { background:#fff8ee; }
.fs-item-photo { width:110px; height:74px; object-fit:cover; border-radius:6px; flex:0 0 auto; }
.fs-item-name { flex:1 1 auto; font-size:20px; font-weight:600; font-family:'Roboto', 'Helvetica Neue', Arial, sans-serif; }
.fs-item-desc { font-size:18px; font-weight:900; color:#6b554b; }
.fs-item-price { font-size:18px; font-weight:600; white-space:nowrap; }
/* v1.4.68: on wider screens the description sits in the text column
   beside the photo, under the name/price line, not below the photo. */
@media (min-width: 769px) {
  .fs-item { display:grid; grid-template-columns:auto minmax(0, 1fr) auto; grid-template-areas:"photo name price" "photo desc desc"; column-gap:14px; row-gap:2px; }
  .fs-item-top { display:contents; }
  .fs-item-photo { grid-area:photo; }
  .fs-item-name { grid-area:name; align-self:center; }
  .fs-item-price { grid-area:price; align-self:center; }
  .fs-item-desc { grid-area:desc; }
}
@media (max-width:640px) { .fs-item-photo { width:84px; height:56px; } .fs-item-name { font-size:20px; } }
.fs-ingredients { columns:2; column-gap:2rem; font-size:15px; }
.fs-ingredients li { break-inside:avoid; }
/* Nutrition Facts label (v1.2.3): a tidy boxed black-and-white list that
   deliberately overrides the brand palette inside the box — white ground,
   black text, thick divider bars, thin rules between rows, bold main
   nutrients, indented sub-nutrients. Nothing oversized.
   v1.4.4: at the owner's direction the whole label scales down by
   roughly ×0.85 — max-width 340px → 289px, title 24px → 20px,
   "Per 100 g" and rows 15px → 13px, thick bar 10px → 9px, medium
   bar 5px → 4px, sub-nutrient indent 20px → 17px, box padding
   10px 12px 8px → 9px 10px 7px — so the internal proportions are
   unchanged. Structure, nutrient order, borders and display
   rounding are untouched: still no % Daily Value, still no
   oversized Calories number. */
.fs-nutrition-facts { background:#fff; color:#000; border:2px solid #000; max-width:289px; margin-top:28px; padding:9px 10px 7px; font-family:'Roboto', 'Helvetica Neue', Helvetica, Arial, sans-serif; }
.fs-nf-title { font-size:20px; font-weight:900; line-height:1.1; margin:0; }
.fs-nf-per { font-size:13px; margin:2px 0 0; }
.fs-nf-bar { background:#000; height:9px; margin:6px 0 2px; }
.fs-nf-bar-med { height:4px; margin:6px 0 2px; }
.fs-nf-row { font-size:13px; line-height:1.35; margin:0; padding:3px 0; border-bottom:1px solid #a6a6a6; }
.fs-nutrition-facts .fs-nf-row:last-child { border-bottom:0; }
.fs-nf-row.is-bold .fs-nf-name { font-weight:700; }
.fs-nf-row.is-indent { padding-left:17px; }
.fs-nf-row.is-italic .fs-nf-name { font-style:italic; }
.fs-crumb a { color:#3F2620; }
.fs-banner { background:#3F2620; color:#F8F1E5; text-align:center; padding:6px 16px; font-size:19px; font-weight:700; }
/* Daily banner (v1.4.8): one message per day of the week, chosen in the
   visitor's browser by assets/fs-banner.js. fs_banner_html() renders all
   seven days as .fs-banner-day spans; only the server's fallback day is
   unhidden and the script swaps in today's. The [hidden] guard below
   keeps a hidden day hidden even if a broad display rule reaches the
   spans. (The v1.2.1–v1.4.7 .fs-banner-rotate slide rules are retired
   with the rotation itself.) */
.fs-banner-daily .fs-banner-day[hidden] { display:none; }
.fs-footer { background:#3F2620; color:#F8F1E5; padding:19px 24px; text-align:center; margin-top:30px; font-size:19px; font-weight:600; line-height:1.45; }
.fs-footer p { margin:4px 0; }
.fs-footer-loc { font-family:'Roboto', 'Helvetica Neue', Arial, sans-serif; font-weight:700; font-size:19px; }
.fs-footer a { color:#F8F1E5; }
/* Footer columns (v1.2.6; Cabin-style centring v1.2.7; compressed
   v1.2.8): SITE MAP / GOOGLE REVIEWS / COME VISIT side by side on
   desktop, stacking on mobile — every column centre-aligned at every
   width, like the Cabin footer, at a tighter line height and with a
   slimmer column gap so the band sits visibly shorter. The social
   row and the copyright line sit centred beneath the columns. */
.fs-footer-cols { display:grid; grid-template-columns:1fr 1fr 1fr; gap:22px; max-width:1100px; margin:0 auto 4px; text-align:center; line-height:1.45; }
.fs-footer-title { font-family:'Roboto', 'Helvetica Neue', Arial, sans-serif; font-weight:700; font-size:22px; color:#F8F1E5; margin:0 0 7px; text-transform:uppercase; letter-spacing:.12em; }
.fs-footer-links { list-style:none; margin:0; padding:0; }
.fs-footer-links li { margin:4px 0; }
/* Site Map links are never underlined by default (v1.2.9: the
   selectors gain .fs-footer specificity so no upstream link style
   can re-underline them; hover still underlines). */
.fs-footer .fs-footer-links a { text-decoration:none; }
.fs-footer .fs-footer-links a:hover { text-decoration:underline; }
/* Footer Site Map Menu toggle (v1.2.8 as a link plus a separate
   triangle details element; v1.3.2 removes the triangle): the word "Menu" itself
   is the <details> summary — styled like the other Site Map links
   (cream, via the footer's colour; centred; the native marker
   hidden and no triangle character anywhere) — and tapping it
   reveals the five category links stacked centred beneath the
   entry. Closed by default, so the column stays one short list.
   "Menu" no longer links to /products/ in the footer (the header
   Menu still does). */
.fs-footer-menu-details { display:block; }
.fs-footer .fs-footer-menu-details summary { display:block; list-style:none; cursor:pointer; }
.fs-footer .fs-footer-menu-details summary:hover { text-decoration:underline; }
.fs-footer-menu-details summary::-webkit-details-marker { display:none; }
.fs-footer-menu-details summary::marker { content:''; }
.fs-footer-sublist { list-style:none; margin:7px 0 2px; padding:0; text-align:center; }
.fs-footer-sublist li { margin:4px 0; }
.fs-footer .fs-footer-sublist a { text-decoration:none; }
.fs-footer .fs-footer-sublist a:hover { text-decoration:underline; }
/* Footer review line (v1.2.7 as stacked stars over the count;
   v1.2.8 compresses it; v1.2.9 tightens it): five ~20px gold stars
   and the review count share one line, with the "Read Reviews"
   link pulled up tight beneath it — a ~2px gap. The selectors
   carry .fs-footer specificity so they beat the generic
   .fs-footer p margins (adjacent margins collapse to the max,
   so a 0 bottom + 2px top renders as a 2px gap). */
.fs-footer .fs-footer-review-line { margin:2px 0 0; line-height:1.25; }
.fs-footer-stars { color:#E9A13B; font-size:20px; letter-spacing:1px; line-height:1; }
.fs-footer .fs-footer-review-link { margin:2px 0 0; }
/* Come Visit column (v1.2.9): tight at the top — the heading, the
   Ocean Park line and the address sit at ~2-3px gaps, matching the
   tightest spacing in the compressed footer. The address prints
   on two lines (.fs-footer-addr, a <br> in the templates), the
   phone keeps a line of its own, and the hours print on two lines
   — the [fs_hours] shortcode already joins its two Quick Edit
   values with a <br>, so the template markup there is unchanged
   (and its rendering elsewhere, e.g. the Contact page, is too). */
.fs-footer-visit .fs-footer-title { margin-bottom:3px; }
.fs-footer .fs-footer-visit p { margin:2px 0; }
/* The phone number always stays on one line (v1.3.2): nowrap so
   "604-531-7880" can never wrap mid-number in the narrow column. */
.fs-footer .fs-footer-phone { white-space:nowrap; }
.fs-copyright { font-size:14px; opacity:.85; margin:7px 0 0; }
@media (max-width:760px) {
  .fs-footer-cols { grid-template-columns:1fr; gap:18px; text-align:center; }
  .fs-footer-links li { margin:5px 0; }
}
/* Header badge logo (v1.2.4; sized up v1.2.5): fs_brand_html() swaps
   the text brand for the Wix badge image when the
   'fieldstone-badge-header' attachment exists. v1.2.5 centres it at
   the top of the band at ~110px tall, matching the theme header;
   smaller on phones so the band stays proportionate.
   v1.4.7: fs_brand_html() prints TWO variants — the brown badge
   (.fs-logo-brown) and the cream badge (.fs-logo-cream) — and the
   state rules below show exactly one per header state. */
.fs-brand-img { line-height:0; }
.fs-brand-logo { height:110px; width:auto; display:block; margin:0 auto; }
@media (max-width:640px) { .fs-brand-logo { height:84px; } }
/* Header states (v1.4.7) — THE CONTRACT, shared with the theme
   header: the header element carries .fs-site-header, and its
   brand link holds the two logo images (.fs-logo-brown /
   .fs-logo-cream). At rest the brown logo shows on the cream
   header; once fs-sticky-header.js adds .is-stuck (the page has
   scrolled past the banner and the header has pinned), the
   header is the brown bar, the cream logo shows, and the brand
   text and nav links go cream. Rule order matters for the
   single-variant fallback in fs_brand_html() (a lone image
   carries BOTH logo classes): at rest the later .fs-logo-brown
   rule wins so it shows; stuck, the later .is-stuck
   .fs-logo-cream rule wins so it still shows. A theme header
   using different nav markup needs one theme-side rule of the
   same shape for its links; the background and logo swap work
   as-is. */
/* Header parity (v1.4.36): on theme pages WordPress flow
   layout adds a 19.2px top margin to the [fs_header] pieces
   inside the header group (the wpautop <p> around the
   sandwich button, and the nav), which made the homepage
   header ~25px thicker than the identical header on
   product pages. Zero those margins -- the flex gap does
   the spacing on both header sources. */
.fs-site-header > p, .fs-site-header > .fs-nav { margin:0; }
.fs-site-header .fs-logo-cream { display:none; }
.fs-site-header .fs-logo-brown { display:block; }
.fs-site-header.is-stuck { background:#3F2620; border-bottom-color:transparent; }
.fs-site-header.is-stuck .fs-logo-brown { display:none; }
.fs-site-header.is-stuck .fs-logo-cream { display:block; }
.fs-site-header.is-stuck .fs-brand { color:#F8F1E5; }
.fs-site-header.is-stuck .fs-nav a { color:#F8F1E5; }
/* Footer review count (v1.2.4 as the rating line; since v1.2.7 it is
   the "4.5 · 563 reviews" count under the stars in the Google
   Reviews column — it renders only there). */
.fs-footer-rating { font-size:19px; font-weight:600; }
/* Footer social icons (v1.2.5): a centred row above the rating line.
   fs_social_html() renders nothing while FS_SOCIAL_URLS is empty, so
   these rules sit idle until the owner's profile URLs are filled in.
   v1.4.3: at the owner's direction the icons grow 22px → 36px
   (the svg size below pins the render; fs_social_html()'s width/
   height attributes match), the gap opens 14px → 16px, and the
   row gets a little more air (margin 7px 0 1px → 9px 0 2px) so
   the taller icons don't crowd the © line. */
.fs-social { display:flex; justify-content:center; gap:16px; margin:9px 0 2px; }
.fs-social-link { display:inline-flex; line-height:0; opacity:.92; }
.fs-social-link:hover, .fs-social-link:focus { opacity:1; }
.fs-social-link svg { display:block; width:36px; height:36px; }
/* Category photo header (v1.2.5): on a category archive, when a
   'fs-cat-header-{slug}' attachment exists, the title sits over that
   photo as a faded band (menu-header style) — the photo at reduced
   opacity over the cream ground, the band running to the edges of
   .fs-main (hence the negative margins against its padding). Without
   the attachment the template prints its plain <h1> and none of this
   applies. */
.fs-cat-header { position:relative; margin:-24px -32px 18px; height:260px; overflow:hidden; background:#F8F1E5; display:flex; align-items:center; justify-content:center; }
.fs-cat-header-img { position:absolute; inset:0; width:100%; height:100%; object-fit:cover; opacity:.65; }
.fs-cat-header h1 { position:relative; font-size:44px; font-weight:900; margin:0; padding:0 16px; text-align:center; }
@media (max-width:640px) { .fs-cat-header { height:200px; } .fs-cat-header h1 { font-size:44px; } }
/* Hero slideshow (v1.2.4) — [fs_hero]. Full-width photo crossfade with
   the frosted brand-cream panel over it, Wix-style. Slides are
   absolutely positioned; the panel flows in the flex container so the
   hero is never shorter than its panel on a narrow screen. Only the
   .is-active slide shows; assets/fs-rotate.js moves that class, and
   with no JS (or reduced motion) the first photo simply stays up. */
.fs-hero { position:relative; overflow:hidden; min-height:520px; display:flex; align-items:center; justify-content:center; padding:40px 20px; box-sizing:border-box; background:#3F2620; color:#3F2620; font-family:'Nunito Sans', 'Segoe UI', 'Helvetica Neue', Arial, sans-serif; }
.fs-hero-slide { position:absolute; inset:0; opacity:0; visibility:hidden; transition:opacity .8s ease-in-out, visibility 0s linear .8s; }
.fs-hero-slide.is-active { opacity:1; visibility:visible; transition:opacity .8s ease-in-out; }
.fs-hero-slide img { width:100%; height:100%; object-fit:cover; display:block; }
.fs-hero-panel { position:relative; z-index:2; max-width:660px; text-align:center; padding:34px 38px; border-radius:10px; background:rgba(248,241,229,0.45); -webkit-backdrop-filter:blur(3px); backdrop-filter:blur(3px); box-shadow:0 6px 30px rgba(38,24,18,0.25); }
.fs-hero-title { font-family:'Roboto', 'Helvetica Neue', Arial, sans-serif; font-weight:900; font-size:44px; line-height:1.12; margin:0 0 6px; color:#3F2620; }
.fs-hero-script { font-family:'Caveat', 'Segoe Script', 'Comic Sans MS', cursive; font-weight:700; font-size:34px; line-height:1.1; margin:0 0 10px; color:#3F2620; }
.fs-hero-text { font-size:19px; line-height:1.55; margin:0 0 20px; }
.fs-hero-cta { margin:0; }
.fs-hero-btn { display:inline-block; background:#3F2620; color:#F8F1E5; border:2px solid #3F2620; border-radius:6px; padding:12px 26px; font-size:19px; font-weight:700; text-decoration:none; }
.fs-hero-btn:hover { background:transparent; color:#3F2620; }
.fs-hero-dots { position:absolute; left:0; right:0; bottom:14px; z-index:3; display:flex; justify-content:center; gap:8px; }
.fs-hero-dot { width:12px; height:12px; padding:0; border-radius:50%; border:2px solid #F8F1E5; background:transparent; box-shadow:0 1px 4px rgba(0,0,0,0.35); cursor:pointer; }
.fs-hero-dot.is-active { background:#F8F1E5; }
@media (min-width:1024px) { .fs-hero { justify-content:flex-start; } .fs-hero-panel { margin-left:6%; } }
/* v1.3.4: on phones the frosted panel shrinks so more of the photo
   shows — 78% of the slide width (still centred, as it sits below
   1024px), about half the padding, tighter gaps between title,
   script, paragraph and button, and the panel's type scaled down
   with it. The paragraph holds at 20px/600: compact, not tiny.
   Desktop and tablet rendering is untouched. */
@media (max-width:640px) {
  .fs-hero { min-height:420px; padding:28px 14px; }
  .fs-hero-panel { width:78%; padding:12px 14px; }
  .fs-hero-title { font-size:30px; margin-bottom:4px; }
  .fs-hero-script { font-size:26px; margin-bottom:6px; }
  .fs-hero-text { font-size:20px; font-weight:600; line-height:1.45; margin-bottom:12px; }
  .fs-hero-btn { padding:10px 20px; }
}
@media (prefers-reduced-motion: reduce) { .fs-hero-slide { transition:none; } }
/* Google reviews ticker (v1.2.4) — [fs_reviews]. A cream card whose
   reviews share one grid cell (the banner's stacking trick), so the box
   is as tall as its longest review and nothing jumps as they change.
   Only the .is-active review shows; assets/fs-rotate.js moves it. */
.fs-reviews { display:grid; max-width:820px; margin:0 auto; box-sizing:border-box; background:#fff8ee; border:1px solid #d8c9b4; border-radius:10px; padding:26px 30px; text-align:center; color:#3F2620; font-family:'Nunito Sans', 'Segoe UI', 'Helvetica Neue', Arial, sans-serif; }
.fs-review-slide { grid-area:1 / 1; display:flex; flex-direction:column; justify-content:center; opacity:0; visibility:hidden; transition:opacity .6s ease-in-out, visibility 0s linear .6s; }
.fs-review-slide.is-active { opacity:1; visibility:visible; transition:opacity .6s ease-in-out; }
.fs-review-stars { color:#E9A13B; font-size:20px; letter-spacing:3px; margin:0 0 10px; }
.fs-review-text { font-size:22px; font-weight:600; line-height:1.55; margin:0 0 12px; }
.fs-review-by { font-size:19px; font-weight:600; color:#6b554b; margin:0; }
@media (max-width:640px) { .fs-reviews { padding:20px; } .fs-review-text { font-size:22px; } }
@media (prefers-reduced-motion: reduce) { .fs-review-slide { transition:none; } }
/* Photo scroll (v1.2.9; MANUAL GALLERY from v1.4.11) —
   [fs_photoscroll]. One line of photos on the brand cream
   that the CUSTOMER moves through. Through v1.4.10 this was
   a CSS marquee — a track holding the set twice, keyframes
   translating it -50% in a seamless loop, pausing on hover —
   but the owner clarified she does not want this strip
   drifting on its own like the reviews band, so the marquee
   (track, duplicate set, keyframes, hover/focus pause) is
   GONE, deleted outright rather than overridden, and nothing
   here moves by itself. The photos sit in a single
   horizontally scrollable row (.fs-photoscroll-row) holding
   the one set; its scrollbar is hidden for discretion
   (scrollbar-width for Firefox, ::-webkit-scrollbar for
   WebKit/Blink, the -ms- property for legacy Edge). The
   wrapper is position:relative and clips overflow so the
   strip can never push the page sideways. assets/fs-rotate.js
   applies the daily-rotated starting order the strip has
   had since v1.3.1. (v1.4.11 added white square arrow
   buttons at the wrapper's far left and right edges;
   v1.4.13 removes them at the owner's direction — she
   tested on her phone and the row scrolls fine with a
   finger, so their rules are deleted here, not overridden.)
   The row's scroll-behavior keeps keyboard scrolling
   smooth; with reduced motion requested that switches to
   auto — reduced motion is otherwise simply this strip's
   default behaviour. Like the hero/reviews rules
   above, these are NOT scoped to .fs-body — the shortcode
   renders on theme pages. */
.fs-photoscroll { position:relative; overflow:hidden; background:#F8F1E5; padding:18px 0; }
.fs-photoscroll-row { display:flex; overflow-x:auto; overflow-y:hidden; scroll-behavior:smooth; scrollbar-width:none; -ms-overflow-style:none; }
.fs-photoscroll-row::-webkit-scrollbar { display:none; }
.fs-photoscroll-set { display:flex; gap:10px; padding:0 10px; flex:0 0 auto; }
.fs-photoscroll-item { display:block; flex:0 0 auto; line-height:0; border-radius:10px; overflow:hidden; }
.fs-photoscroll-img { display:block; height:260px; min-width:260px; width:auto; object-fit:cover; border-radius:10px; }
@media (max-width:760px) { .fs-photoscroll-img { height:210px; min-width:210px; } }
@media (prefers-reduced-motion: reduce) { .fs-photoscroll-row { scroll-behavior:auto; } }
/* Reviews band (v1.4.0) — [fs_reviews_band]. The Cabin site's
   reviews ticker in Fieldstone's palette: a full-width
   dark-brown band (no rounded corners, spanning its container)
   holding a continuous slow leftward marquee of Google reviews.
   The mechanics mirror the photo scroll's: the track holds the
   cell set twice and the keyframes translate it -50% — exactly
   one set — so the loop is seamless. The first cell is the
   summary — five gold stars over "4.5 · 563 reviews", centred,
   the whole cell a link to the Google listing — then each
   review rides as one cell (~500px on desktop): gold stars,
   the trimmed quote, and the italic "— Name, Google review"
   credit, all cream on the brown. The band's height is set by
   its tallest cell (~95px on desktop; on small screens the
   cells narrow and the band grows as the quotes take more
   lines). The animation runs at the duration the shortcode
   sets inline (~5.5s per cell); it pauses on hover and while
   focus is inside the band, and with reduced motion requested
   it stops, the duplicate set hides, and the band becomes an
   ordinary horizontally scrollable row. Like the hero/reviews
   rules above, these are NOT scoped to .fs-body — the band
   renders on theme pages. */
.fs-rband { background:#3F2620; color:#F8F1E5; overflow:hidden; border-radius:0; font-family:'Nunito Sans', 'Segoe UI', 'Helvetica Neue', Arial, sans-serif; }
.fs-rband-track { display:flex; width:max-content; animation:fs-rband-drift 61s linear infinite; }
.fs-rband:hover .fs-rband-track,
.fs-rband:focus-within .fs-rband-track { animation-play-state:paused; }
.fs-rband-set { display:flex; align-items:stretch; flex:0 0 auto; }
.fs-rband-summary { display:flex; flex-direction:column; align-items:center; justify-content:center; text-align:center; gap:5px; flex:0 0 250px; box-sizing:border-box; padding:12px 18px; color:#F8F1E5; text-decoration:none; }
.fs-rband-summary:hover .fs-rband-count, .fs-rband-summary:focus .fs-rband-count { text-decoration:underline; }
.fs-rband-count { font-size:17px; font-weight:700; white-space:nowrap; }
.fs-rband-item { display:flex; align-items:center; flex:0 0 500px; box-sizing:border-box; padding:12px 26px 12px 6px; }
.fs-rband-line { margin:0; font-size:17px; line-height:1.45; }
.fs-rband-stars { color:#E9A13B; letter-spacing:1px; }
.fs-rband-summary .fs-rband-stars { font-size:19px; }
.fs-rband-by { font-style:italic; opacity:.85; }
@keyframes fs-rband-drift { from { transform:translateX(0); } to { transform:translateX(-50%); } }
@media (max-width:760px) {
  .fs-rband-summary { flex-basis:210px; padding:12px; }
  .fs-rband-item { flex-basis:300px; padding:12px 18px 12px 4px; }
  .fs-rband-line { font-size:16px; }
}
@media (prefers-reduced-motion: reduce) {
  .fs-rband { overflow-x:auto; }
  .fs-rband-track { animation:none; }
  .fs-rband-set + .fs-rband-set { display:none; }
}
/* Photo carousel (v1.4.0) — [fs_carousel]. The Cabin site's
   photo gallery: ONE photo at a time, centred at the content
   measure, in a wide panoramic crop (aspect-ratio 7/2 on
   desktop, 16/9 on small screens; object-fit cover does the
   cropping). Slides stack in the frame and only the .is-active
   one shows, with a short opacity fade as it swaps; the swap
   itself is manual — white square arrow buttons (40px, inset
   15px at mid-height, dark glyphs, gold on hover/focus) and a
   row of small dots overlaid along the photo's bottom edge,
   one per photo, the active dot gold and the rest white
   outline. There is NO autoplay: assets/fs-rotate.js only
   wires the arrows/dots and applies the daily-rotated starting
   photo on load. With reduced motion requested the fade is
   removed and swaps are instant. Like the rules above, these
   are NOT scoped to .fs-body — the carousel renders on theme
   pages. */
.fs-carousel { max-width:1180px; margin:0 auto; box-sizing:border-box; font-family:'Nunito Sans', 'Segoe UI', 'Helvetica Neue', Arial, sans-serif; }
.fs-carousel-frame { position:relative; aspect-ratio:7/2; overflow:hidden; border-radius:10px; background:#3F2620; }
.fs-carousel-slide { position:absolute; inset:0; display:block; line-height:0; opacity:0; visibility:hidden; transition:opacity .35s ease-in-out, visibility 0s linear .35s; }
.fs-carousel-slide.is-active { opacity:1; visibility:visible; transition:opacity .35s ease-in-out; }
.fs-carousel-img { width:100%; height:100%; object-fit:cover; display:block; }
.fs-carousel-arrow { position:absolute; top:50%; transform:translateY(-50%); z-index:3; width:40px; height:40px; padding:0; border:0; border-radius:0; background:#fff; color:#3F2620; font-size:26px; line-height:1; cursor:pointer; display:flex; align-items:center; justify-content:center; box-shadow:0 1px 5px rgba(0,0,0,.3); }
.fs-carousel-arrow:hover, .fs-carousel-arrow:focus { background:#E9A13B; }
.fs-carousel-prev { left:15px; }
.fs-carousel-next { right:15px; }
.fs-carousel-dots { position:absolute; left:10px; right:10px; bottom:10px; z-index:3; display:flex; flex-wrap:nowrap; justify-content:center; gap:6px; }
.fs-carousel-dot { flex:1 1 0; max-width:12px; width:12px; height:auto; aspect-ratio:1/1; padding:0; border-radius:50%; border:2px solid #F8F1E5; background:transparent; box-shadow:0 1px 4px rgba(0,0,0,.35); cursor:pointer; }
.fs-carousel-dot.is-active { background:#E9A13B; border-color:#E9A13B; }
@media (max-width:760px) { .fs-carousel-frame { aspect-ratio:16/9; } .fs-carousel-dots { gap:3px; } .fs-carousel-dot { border-width:1px; } }
/* Carousel lightbox (v1.4.16) — clicking a carousel photo no
   longer leaves the site for Instagram (owner direction); the
   photo opens full-size in this fixed overlay, rendered by
   [fs_carousel] after the frame and wired in fs-rotate.js.
   Brown-black backdrop, the photo contained whole, a round
   white × at top-right and square white ‹ › arrows at the
   sides matching the carousel's own arrows. */
.fs-carousel-slide { cursor:zoom-in; }
.fs-lightbox[hidden] { display:none!important; }
.fs-lightbox { position:fixed; inset:0; z-index:10000; background:rgba(38,24,20,.93); display:flex; align-items:center; justify-content:center; }
.fs-lightbox-img { max-width:92vw; max-height:88vh; object-fit:contain; display:block; border-radius:6px; box-shadow:0 4px 30px rgba(0,0,0,.5); }
.fs-lightbox-close { position:absolute; top:14px; right:16px; width:44px; height:44px; padding:0; border:0; border-radius:50%; background:#fff; color:#3F2620; font-size:28px; line-height:1; cursor:pointer; display:flex; align-items:center; justify-content:center; box-shadow:0 1px 5px rgba(0,0,0,.3); }
.fs-lightbox-arrow { position:absolute; top:50%; transform:translateY(-50%); z-index:3; width:44px; height:44px; padding:0; border:0; border-radius:0; background:#fff; color:#3F2620; font-size:30px; line-height:1; cursor:pointer; display:flex; align-items:center; justify-content:center; box-shadow:0 1px 5px rgba(0,0,0,.3); }
.fs-lightbox-close:hover, .fs-lightbox-close:focus, .fs-lightbox-arrow:hover, .fs-lightbox-arrow:focus { background:#E9A13B; }
.fs-lightbox-prev { left:14px; }
.fs-lightbox-next { right:14px; }
@media (prefers-reduced-motion: reduce) { .fs-carousel-slide { transition:none; } }
/* Full-bleed homepage blocks on phones (v1.4.10) — the [fs_hero]
   slideshow, the [fs_reviews_band] Google reviews band and the
   [fs_photoscroll] photo strip render inside the theme content's
   20px side padding, so on a phone they stopped 20px short of
   each screen edge. At ≤760px they break out to the full
   viewport width with the standard full-bleed margins: the box
   is sized 100vw and pulled left by (50% of its container -
   50vw), which centres it on the viewport as long as the
   container is itself centred or full-width — both hold for
   the theme's content column. Only the outer boxes widen: the
   hero's frosted panel (its ≤640px 78%-of-slide rule now
   resolves against the wider slide, as intended), the band's
   scrolling cells and the strip's photos keep their measures,
   and all three blocks already clip their own interiors
   (overflow:hidden), so no track or slide can spill past the
   new edges. The html/body guard uses overflow-x:clip — NOT
   hidden — because clip creates no scroll container, so the
   sticky headers keep sticking; browsers without clip support
   ignore the declaration, and on phones (overlay scrollbars)
   100vw is the layout width anyway, so the breakout is exact
   with or without the guard. The guard exists for narrow
   windows WITH classic scrollbars, where 100vw runs wider
   than the body by the scrollbar's width and the centred
   breakout would otherwise poke half of that past each edge.
   Everything in this block sits inside the ≤760px query —
   desktop rendering does not change by a pixel. (The plugin
   pages' category photo band needs no such rule: at ≤760px
   .fs-main is full-width and .fs-cat-header's -20px margins
   already cancel its 20px padding exactly, so that band
   already spans edge to edge.) */
@media (max-width:760px) {
  html, body { overflow-x:clip; }
  .fs-hero, .fs-rband, .fs-photoscroll { width:100vw; margin-left:calc(50% - 50vw); margin-right:calc(50% - 50vw); }
}

/* Fixed page backdrop (v1.4.14) — the bread-shelves photo
   (fs-page-bg.jpg, bundled with this plugin) sits FIXED
   behind the whole site while the page content scrolls
   vertically over it, the way The Cabin's site layers its
   photos behind its content. The layer is a body::before
   at position:fixed / z-index:-1 — fixed positioning
   (not background-attachment) so it holds still on phone
   browsers too. A cream wash (brand cream at 0.80) sits
   between the photo and the text so the dark-brown copy
   stays easy to read; the photo still reads clearly as
   shelves of bread behind the page. The body background
   is made transparent so the layer shows through on
   theme pages, and .fs-body's solid cream (the rule at
   the top of this file) is dropped so the plugin's
   product pages get the same backdrop. Components with
   their own backgrounds — the banner, the sticky header,
   the hero, the reviews band, the footer, the filter box
   and the Nutrition Facts label — are untouched and
   simply ride over the photo. */
html { background:#F8F1E5; }
body { background-color:transparent !important; }
body::before { content:""; position:fixed; inset:0; z-index:-1; pointer-events:none; background:linear-gradient(rgba(248,241,229,.80), rgba(248,241,229,.80)), url("fs-page-bg.jpg") center center / cover no-repeat; }
.fs-body { background:transparent; }

/* Allergy notice (v1.4.52) — under the Nutrition Facts label on
   single product pages (owner-approved wording, 2026-11-07). */
.fs-allergy { margin:22px 0 0; font-size:16px; line-height:1.55; max-width:680px; color:#3F2620; }

/* Christmas garland trim (v1.4.58): seasonal strip under the banner,
   same holly motif as the Christmas labels. Remove with the January build. */
.fs-trim { height:78px; margin-bottom:-78px; position:relative; z-index:70; pointer-events:none; background:url('fs-trim.png') repeat-x center top; background-size:auto 100%; }
@media (max-width: 768px) { .fs-trim { height:54px; margin-bottom:-54px; } }

/* Christmas garland SIDES (v1.4.62): the same garland rotated to run down
   the left and right edges of every page (fixed strips; vine at the outer
   edge, leaves pointing inward). Same Quick Edit 'Christmas trim?' switch. */
.fs-trim-side { position:fixed; top:0; bottom:0; width:78px; z-index:1; pointer-events:none; background:url('fs-trim-v.png') repeat-y center top; background-size:100% auto; }
.fs-trim-l { left:0; }
.fs-trim-r { right:0; transform:scaleX(-1); }
@media (max-width: 768px) { .fs-trim-side { width:44px; } }

/* v1.4.73 DEMO: Ingredients / Nutrition Facts popups (Granola page
   only, gated in single-fs_product.php). */
.fs-pop-btns { grid-column:1 / -1; display:flex; gap:12px; flex-wrap:wrap; margin:18px 0 4px; }
.fs-pop-open { background:#3F2620; color:#F8F1E5; border:0; border-radius:6px; padding:10px 20px; font-size:17px; font-weight:700; cursor:pointer; font-family:'Roboto', 'Helvetica Neue', Arial, sans-serif; }
.fs-pop { position:fixed; inset:0; background:rgba(46,29,16,0.55); display:flex; align-items:flex-start; justify-content:center; padding:28px 12px; overflow-y:auto; z-index:200; }
.fs-pop[hidden] { display:none; }
.fs-pop-box { background:#F8F1E5; border-radius:10px; max-width:560px; width:100%; padding:20px 22px; position:relative; }
.fs-pop-box h2 { margin-top:0; }
.fs-pop-box .fs-nutrition-facts { margin:0 auto; }
.fs-pop-close { position:absolute; top:0; right:0; background:none; border:0; font-size:28px; line-height:1; cursor:pointer; color:#3F2620; padding:2px 4px; }

/* v1.4.74: popup buttons on phones -- one row, equal size
   (owner, 2026-11-15). Desktop keeps the v1.4.73 sizing. */
@media (max-width:768px) {
  .fs-pop-btns { flex-wrap:nowrap; }
  .fs-pop-open { flex:1 1 0; text-align:center; }
}

/* Product page layout, desktop (owner, 2026-11-17): on pages with the
   popup buttons, the allergy notice sits beside the picture under the
   dietary list, the description below it, and the Ingredients /
   Nutrition Facts buttons sit below the picture at equal size.
   (v1.4.79: description stays in its original row; the allergy
   notice sits below it, still beside the picture.)
   Partner pages (no buttons) keep the previous layout. */
@media (min-width:769px) {
  .fs-single:has(.fs-pop-btns) .fs-photo { grid-row:3 / span 3; }
  .fs-single:has(.fs-pop-btns) .fs-allergy { grid-column:2; grid-row:5; align-self:start; }
  .fs-single:has(.fs-pop-btns) .fs-pop-btns { grid-column:1; grid-row:6; }
  .fs-pop-open { flex:1 1 0; text-align:center; padding:10px 10px; }
}
