/* ============================================ Lettiva V2 Site Interactions — Shared CSS Companion styles for site-v2-interactions.js ============================================ */ /* --- Horizontal rails --- `contain`, deliberately, and ONLY on the rails. MDN: `contain` observes the element's own bounce and blocks scroll chaining; `none` blocks chaining AND suppresses the bounce. The bounce is an affordance on touch — it is how a thumb learns the row scrolls sideways — so `none` is the wrong value here and shipping it cost the rails their discoverability. There is deliberately NO html/body rule. MDN warns that these values disable native browser navigation, including horizontal swipe navigation (swipe to go back). Setting it at the document would trade a working back gesture for nothing: once every rail contains its own overscroll, no chaining reaches the page anyway. Audited 2026-08-14: no generated rail touches the left screen edge, so none of them sits in the back-gesture zone either. This covers the Tailwind utility before JS runs; initRails() catches block and bespoke rails, which declare overflow-x in their own CSS under names this stylesheet cannot know. */ .overflow-x-auto, .overflow-x-scroll { overscroll-behavior-x: contain; } /* --- Nav items: never wrap mid-label --- Flex items in the nav

anchors so the logo link (no
wrapping) and the CTA button (also outside
) are not restyled. !important is used because Tailwind utilities for text colour (text-muted-foreground / hover:text-foreground) live in @layer utilities and at certain cascade points can outrank our un-layered rule on these anchors — we want the active marker to be unmistakable, so brute-force the colour and add a subtle underline. */ nav li a[aria-current="page"] { color: var(--color-accent, #009933) !important; font-weight: 600 !important; text-decoration: underline; text-decoration-color: var(--color-accent, #009933); text-decoration-thickness: 2px; text-underline-offset: 6px; } /* --- Base --- */ /* Prevent horizontal page scroll from overflowing buttons/content. overflow-x: clip (not hidden) avoids the fixed-positioning containment side-effect that overflow-x: hidden creates in some browsers. */ html, body { overflow-x: clip; max-width: 100%; } /* Override Tailwind preflight "img { height: auto }" — without this, images inside aspect-ratio containers don't fill vertically. */ figure img, [style*="aspect-ratio"] img, [class*="aspect-"] > img { height: 100% !important; object-fit: cover; } /* --- Scroll Reveal --- Only applied when .animations-ready is on (added by JS). Without JS, all content is fully visible (progressive enhancement). */ .animations-ready [data-reveal] { opacity: 0; will-change: opacity, transform; transition: opacity 0.6s cubic-bezier(0.22, 1, 0.36, 1), transform 0.6s cubic-bezier(0.22, 1, 0.36, 1); } .animations-ready [data-reveal="fade-up"] { transform: translateY(30px); } .animations-ready [data-reveal="fade-in"] { transform: none; } .animations-ready [data-reveal="slide-left"] { transform: translateX(-40px); } .animations-ready [data-reveal="slide-right"] { transform: translateX(40px); } .animations-ready [data-reveal="scale-up"] { transform: scale(0.95); } [data-reveal].revealed { opacity: 1; transform: none; } /* --- Stagger Reveal --- AI agents sometimes write [data-reveal-stagger] > * { opacity: 0 } to hide children for a staggered entrance. Our JS adds .revealed to each child when the parent enters the viewport. This rule provides a safety net so .revealed always wins, even if the agent forgot the reveal state. */ [data-reveal-stagger] > *.revealed { opacity: 1 !important; transform: none !important; } /* --- Lightbox --- */ .lightbox-overlay { position: fixed; inset: 0; z-index: 9999; display: flex; align-items: center; justify-content: center; background: rgba(0, 0, 0, 0); backdrop-filter: blur(0); opacity: 0; visibility: hidden; transition: background 0.35s ease, backdrop-filter 0.35s ease, opacity 0.35s ease, visibility 0.35s ease; } .lightbox-overlay.active { background: rgba(0, 0, 0, 0.92); backdrop-filter: blur(8px); opacity: 1; visibility: visible; } .lightbox-image-wrapper { position: relative; max-width: 90vw; max-height: 85vh; display: flex; align-items: center; justify-content: center; transform: scale(0.92); opacity: 0; transition: transform 0.35s cubic-bezier(0.22, 1, 0.36, 1), opacity 0.35s ease; } .lightbox-overlay.active .lightbox-image-wrapper { transform: scale(1); opacity: 1; } .lightbox-image-wrapper img { max-width: 90vw; max-height: 85vh; object-fit: contain; border-radius: 4px; user-select: none; -webkit-user-drag: none; } .lightbox-close { position: absolute; top: 16px; right: 16px; z-index: 10000; width: 44px; height: 44px; display: flex; align-items: center; justify-content: center; background: rgba(255, 255, 255, 0.1); border: 1px solid rgba(255, 255, 255, 0.2); border-radius: 50%; color: #fff; font-size: 20px; cursor: pointer; transition: background 0.2s ease, transform 0.2s ease; line-height: 1; } .lightbox-close:hover { background: rgba(255, 255, 255, 0.2); transform: scale(1.1); } .lightbox-nav { position: absolute; top: 50%; transform: translateY(-50%); z-index: 10000; width: 48px; height: 48px; display: flex; align-items: center; justify-content: center; background: rgba(255, 255, 255, 0.1); border: 1px solid rgba(255, 255, 255, 0.15); border-radius: 50%; color: #fff; font-size: 22px; cursor: pointer; transition: background 0.2s ease, transform 0.2s ease; line-height: 1; } .lightbox-nav:hover { background: rgba(255, 255, 255, 0.2); transform: translateY(-50%) scale(1.1); } .lightbox-nav--prev { left: 16px; } .lightbox-nav--next { right: 16px; } .lightbox-counter { position: absolute; bottom: 16px; left: 50%; transform: translateX(-50%); color: rgba(255, 255, 255, 0.7); font-size: 14px; font-family: inherit; user-select: none; } /* Cursor hint on lightbox-enabled images */ [data-lightbox] img, img[data-lightbox] { cursor: zoom-in; } /* --- Accordion --- */ .accordion-trigger { display: flex; align-items: center; justify-content: space-between; width: 100%; padding: 1rem 0; background: none; border: none; border-bottom: 1px solid rgba(0, 0, 0, 0.08); font: inherit; font-weight: 600; text-align: left; cursor: pointer; color: inherit; transition: color 0.2s ease; } .accordion-trigger:hover { opacity: 0.8; } .accordion-trigger::after { content: '+'; flex-shrink: 0; margin-left: 1rem; font-size: 1.25em; font-weight: 300; transition: transform 0.3s cubic-bezier(0.22, 1, 0.36, 1); } .accordion-trigger[aria-expanded="true"]::after { content: '\2212'; /* minus sign */ transform: rotate(180deg); } .accordion-content { overflow: hidden; max-height: 0; opacity: 0; transition: max-height 0.4s cubic-bezier(0.22, 1, 0.36, 1), opacity 0.3s ease, padding 0.3s ease; padding: 0; } .accordion-content.open { opacity: 1; padding-bottom: 1rem; } /* --- Carousel --- */ .carousel-wrapper { position: relative; overflow: hidden; } .carousel-track { position: relative; min-height: 100px; } .carousel-slide { position: absolute; inset: 0; opacity: 0; visibility: hidden; transition: opacity 0.5s ease, visibility 0.5s ease; } .carousel-slide.active { position: relative; opacity: 1; visibility: visible; } .carousel-dots { display: flex; justify-content: center; gap: 8px; margin-top: 1.25rem; padding: 0; list-style: none; } .carousel-dot { width: 10px; height: 10px; border-radius: 50%; border: none; background: rgba(0, 0, 0, 0.15); cursor: pointer; padding: 0; transition: background 0.25s ease, transform 0.25s ease; } .carousel-dot:hover { background: rgba(0, 0, 0, 0.3); } .carousel-dot.active { background: rgba(0, 0, 0, 0.6); transform: scale(1.2); } /* --- Preview banner clearance --- The preview banner and the site nav are both `sticky top-0`, so they landed on the same line and the banner (z-100) simply covered the nav — the brand and half the links sat behind it on every unpublished site, which is exactly the state a customer is shown their demo in. The banner keeps a FIXED height (h-9, no wrapping) so this offset is exact at every width; both bars stay pinned and neither hides the other. Applies to already-generated sites without a rebuild, because the nav's `top` is overridden here rather than in its baked markup. */ :root { --preview-banner-h: 2.25rem; } /* !important is required, not lazy: each site's own generated CSS pins its nav through an id selector (#site-nav), which outranks any attribute-based rule this shared stylesheet can write. The declaration only shifts the pin down by the banner's height, so it cannot fight whatever else that CSS is doing. */ body:has([data-preview-banner]) [data-sticky-nav], body:has([data-preview-banner]) #site-nav { top: var(--preview-banner-h) !important; } /* --- Sticky Nav --- */ [data-sticky-nav] { transition: background-color 0.35s cubic-bezier(0.4, 0, 0.2, 1), background 0.35s cubic-bezier(0.4, 0, 0.2, 1), box-shadow 0.35s cubic-bezier(0.4, 0, 0.2, 1), border-color 0.35s cubic-bezier(0.4, 0, 0.2, 1), backdrop-filter 0.35s cubic-bezier(0.4, 0, 0.2, 1), padding 0.35s cubic-bezier(0.4, 0, 0.2, 1); } /* Nav background fallback: provides a sensible default for sites where the agent-generated CSS omits a nav background entirely. Wrapped in :where() so specificity is 0-0-0 — any site-specific #site-nav rule wins regardless of source order (this stylesheet loads after inline