/* bizav.ai — site stylesheet. Plain CSS, no build step. One block per section of the page, in the order the page runs; each block's comments carry the design reasoning (Figma node numbers, measurements at the 1440px design width, why a rule is load-bearing). Every section's arrival animation is keyed off a data-reveal attribute that assets/js/main.js writes, so a reader without JavaScript gets the page whole. */ /* ================================================================== index ================================================================== */ *, *::before, *::after { box-sizing: border-box; } html, body { margin: 0; padding: 0; } html { /* iOS Safari inflates the text in some blocks on its own — "text autosizing" — which makes anything set not to wrap come out wider on a phone than it does anywhere else, and wide enough to push past the edge of the page. This holds the sizes the stylesheet actually asks for. */ -webkit-text-size-adjust: 100%; text-size-adjust: 100%; /* And a hard stop on sideways scroll. Every section on this page is laid out to fit the viewport — measured at 320 through 440, nothing reaches the edge — but three of them host third-party scenes (Unicorn Studio, the shader canvases) that build their own canvas at whatever size they like, on the device rather than here. One of those spilling a few pixels past the right edge is enough to make the whole document wider than the window, and then every section's background, which is only as wide as the window, leaves a white strip down the side of the page. clip rather than hidden: hidden would turn the root into a scroll container, which changes how the fixed bar and the anchor jumps behave. clip just refuses to show anything outside the box. */ overflow-x: clip; } body { font-family: "IBM Plex Sans", -apple-system, BlinkMacSystemFont, "Segoe UI", sans-serif; font-variation-settings: "wdth" 100; -webkit-font-smoothing: antialiased; -moz-osx-font-smoothing: grayscale; background-color: #ffffff; color: #08060d; } img, svg { max-width: 100%; } /* --- rhythm between sections --- Each section's own padding-block is sized off its own Figma frame, and those frames were never laid out as one continuous page — stacked with nothing between them, most of the site read as one uninterrupted sheet: two consecutive white sections (or two black ones, Aira into Signals) share an edge with no seam at all, and even a colour change on its own is a hard cut rather than a pause. This is what gives every section a beat of plain space on both sides of that seam before its own padding starts, so a reader's eye gets a place to land between one section's close and the next one's opening line — the gap "most landing pages have" that was asked for. A margin rather than more padding on each section: padding is that section's own internal spacing, tuned to its own content; this is a property of the page's layout, so it belongs to the boundary between sections rather than to either one. The universal selector below is safe because every top-level section here is a bare
or