/* Blog footer parity with besveca.com (2026-11-16): the Framer export never declared
   the wordmark fonts, so "BESVECAhouse" fell back and "house" overflowed. Self-hosted
   copies of the exact files besveca.com loads. Plus generous space above the footer. */
@font-face { font-family: "Boska Medium"; src: url("/assets/fonts/boska-medium.woff2") format("woff2"); font-display: block; }
@font-face { font-family: "Satoshi Bold"; src: url("/assets/fonts/satoshi-bold.woff") format("woff"); font-display: block; }
@font-face { font-family: "Satoshi Medium"; src: url("/assets/fonts/satoshi-medium.woff2") format("woff2"); font-display: swap; }
@font-face { font-family: "Satoshi Regular"; src: url("/assets/fonts/satoshi-regular.woff") format("woff"); font-display: swap; }
.framer-1xjmhdg-container { padding-top: clamp(120px, 15vw, 240px); background: #e9e9e9; }
html, body { background: #e9e9e9 !important; }
/* Footer content is 640px tall inside a 600px footer (desktop variant), which left a strip below. */
.framer-ylFZd .framer-98vjrx { height: 100% !important; }
/* Keep the background video inside the footer box (no dark bands above/below on phones). */
.framer-ylFZd .framer-5zn7zt { overflow: hidden !important; }
.framer-ylFZd .framer-1t790n8-container { top: 0 !important; bottom: 0 !important; height: 100% !important; }
.framer-ylFZd .framer-1t790n8-container video { object-fit: cover !important; width: 100% !important; height: 100% !important; }
/* Blog footer has two extra links (Guide Book, Contact); let them wrap on phones. */
@media (max-width: 809.98px) {
  .framer-ylFZd .framer-1f0ilw9 { flex-direction: column !important; align-items: flex-start !important; gap: 10px !important; }
  .framer-ylFZd .framer-1fbgsny { flex: 0 0 auto !important; width: 100% !important; flex-wrap: wrap !important; justify-content: flex-start !important; row-gap: 10px; }
  /* the footer video has dark bars baked in at phone crop; zoom slightly past them */
  .framer-ylFZd .framer-1t790n8-container video { transform: scale(1.12); }
}
/* Remove Framer branding (Eric 2026-11-18): floating "Made in Framer" badge + template "BuiltIn" credit link in the footer. */
#__framer-badge-container, .__framer-badge, [data-framer-name="BuiltIn Container"], .framer-1dor1xq-container { display: none !important; }
/* Header over the hero (Eric 2026-11-18): the white nav sat on a light gray bar and was hard to read.
   Float the header so each page's hero photo (or the Journal's dark texture) runs up behind it. */
/* Pinned like the home page (Eric 2026-11-18, "nav header is lost" on scroll): fixed to the top,
   transparent over the hero; once scrolled (body.bv-scrolled, set by besveca-blog-header.js) it becomes a
   dark frosted bar so the white nav stays readable over the light article body. Phone too: the hero photo
   now runs up under the 64px bar instead of starting below a black band. */
#besveca-chrome-header { position: fixed !important; top: 0; left: 0; right: 0; z-index: 1000;
  background: transparent; transition: background-color .3s ease, backdrop-filter .3s ease; }
body.bv-scrolled #besveca-chrome-header { background: rgba(11,11,11,.82);
  -webkit-backdrop-filter: blur(14px) saturate(1.2); backdrop-filter: blur(14px) saturate(1.2); }
@media (max-width: 809.98px) {
  #bv-mobile-header { background: transparent !important; transition: background-color .3s ease; }
}
@media (prefers-reduced-motion: reduce) { #besveca-chrome-header, #bv-mobile-header { transition: none !important; } }
/* Nav legibility on every Journal page (Eric 2026-11-18): a soft dark fade behind the nav while it is
   transparent, so the white links read over light photos or before the hero photo has loaded. */
#besveca-chrome-header::before { content: ""; position: absolute; inset: 0 0 -40px 0; z-index: -1; pointer-events: none;
  background: linear-gradient(rgba(11,11,11,.45), rgba(11,11,11,0)); transition: opacity .3s ease; }
body.bv-scrolled #besveca-chrome-header::before { opacity: 0; }
/* Check Availability arrow on Journal pages (Eric 2026-11-18): the copied nav is static, so Framer's hover
   (arrow turns from up-right to right, ~400 ms ease-out) never ran here. Same motion in CSS. */
#besveca-chrome-header a[href*="hospitable"] [data-framer-name="Arrow right"],
#besveca-chrome-footer a[href*="hospitable"] [data-framer-name="Arrow right"] { transition: transform 420ms cubic-bezier(.22,1,.36,1); }
@media (hover: hover) and (pointer: fine) {
  #besveca-chrome-header a[href*="hospitable"]:hover [data-framer-name="Arrow right"],
  #besveca-chrome-footer a[href*="hospitable"]:hover [data-framer-name="Arrow right"] { transform: rotate(0deg) !important; }
}
/* Typography standard (2026-11-18): balanced headline wrapping, no widows in article text. */
h1, h1.framer-text { text-wrap: balance; }
[data-framer-name="Content"] p, [data-framer-name="Content"] h3 { text-wrap: pretty; }

/* Journal story body links (2026-11-19): outbound links to the places named in each story, plus /bookings.
   Same color as the text, thin underline; fades on hover. */
.framer-1bb0aaa[data-framer-name="Content"] a { color: inherit; text-decoration: underline; text-decoration-thickness: 1px; text-underline-offset: 3px; text-decoration-color: currentColor; transition: opacity 200ms ease; }
@media (hover: hover) and (pointer: fine) { .framer-1bb0aaa[data-framer-name="Content"] a:hover { opacity: .55; } }
