/* * Pickle component system. * * The .ex-* vocabulary is the stable API every site and every render string in * app.js consumes. This file dresses the six app UIs: the faucet, the explorer, * the bridge, the toolkit, .pkl names and mini-blocks. The marketing page in * web/ shares the tokens and the faces but not this rhythm, because it is a * document you read once and these are tools you use weekly. * * - Flat surfaces on the #0A0A0B stage, 2px radius, one hairline. * - Every rule paints through the register properties (--banx-text, * --banx-line, --banx-surface-1, --banx-muted, --banx-subtle, * --banx-accent-text, --banx-ground) rather than through literals, so a * section can redefine its own ground without duplicating a rule. * - Mono uppercase micro-labels in IBM Plex Mono against Inter Tight display * type. There is no second text family. * - The signature layout patterns: numbered eyebrow headers, 1px-gap cell * grids, hairline stat strips, waterfall bars. * - Structure only. Everything with a duration lives in shared-ui/motion.css, * which loads after this file: entrances, the scroll cascade, hover and * press. The one exception is the cadence lanes and the pulse dot, whose * motion IS the information they carry. * * Explorer-only pieces stay in explorer-ui/css/explorer.css. */ /* ============================================================ shell: nav bar */ /* * The shell host. shared-ui/shell.js replaces the contents of * `

` with the bar below, and that host needs two things * this rule gives it. * * First, it has to be the sticky box. `.ex-nav` declares `position: sticky` and * on the two apps that write their bar straight into (explorer-ui and * bns-ui) it pins correctly. In the four that mount it through shell.js it did * not, and measuring showed why: the host's height is exactly the bar's 72px, and * a sticky element cannot move within a containing block its own size. So the bar * scrolled away on the faucet, the bridge, mini-blocks and all seven toolkit * pages - where the six-section subnav is the only navigation between the tools. * Nothing about the CSS looked wrong; only scrolling the page showed it. * * Second, min-height reserves the bar's space before the script runs. An empty * header is 0px tall, so the page painted 72px too high and then dropped. * * The z-index has to live HERE, on the host, and not be left to the .ex-nav * inside it. `position: sticky` establishes a stacking context unconditionally - * unlike relative or absolute, which need a non-auto z-index first - so the * moment this host became sticky it began trapping the bar's own * --banx-z-nav inside itself. The host then competed with page content at * z-index 0, lost on document order because

comes after

, and the * toolkit's cells painted straight over the bar at 375px. Naming the level on the * box that actually stacks is what fixes it. */ [data-banx-shell] { display: block; position: sticky; top: 0; z-index: var(--banx-z-nav); min-height: var(--banx-nav-h); } .ex-nav { position: sticky; top: 0; z-index: var(--banx-z-nav); display: flex; flex-wrap: wrap; align-items: center; gap: 0 var(--banx-space-5); height: var(--banx-nav-h); padding-inline: max(var(--banx-gutter), calc((100vw - var(--banx-content)) / 2)); /* The bar keeps its own ink register on both grounds, and that is a choice * rather than a failure to invert. Making a sticky bar track the register * underneath it needs either mix-blend-mode: difference, which distorts the * accent's hue into something that is no longer the brand colour, or a * timeline-scope naming every paper act by hand. A persistent ink running * head over paper is a legitimate editorial form and removes both. * * Redeclaring the register properties here is what makes that work: without * them the bar would inherit a paper act's #121212 text and paint near-black * on near-black. */ --banx-text: #ffffff; --banx-line: rgb(255 255 255 / 14%); --banx-muted: #9aa3a0; --banx-subtle: #6b7370; --banx-accent-text: var(--banx-mint); color: var(--banx-text); /* Keyed to --banx-bg (#0A0A0B), not to the #121212 the page used to be: at 82% * opacity a lighter ground reads as a grey band floating over black rather * than as the page's own surface. */ background: rgb(10 10 11 / 78%); backdrop-filter: blur(20px) saturate(150%); border-bottom: 1px solid var(--banx-line); } .ex-nav > * { display: flex; align-items: center; height: var(--banx-nav-h); } /* The running head's act readout. Mono, small, and the only thing in the bar * that changes as the reader scrolls - the section eyebrow pattern reduced to * bar height. * * `display: none` by default and shown only where there is room: the bar already * carries a brand, six links, two buttons and a burger, and the readout is the * one element that is orientation rather than navigation, so it is the one that * should go first when space runs out. */ .ex-act { display: none; gap: .5rem; margin: 0; padding-left: var(--banx-space-5); color: var(--banx-subtle); font-family: var(--banx-font-mono); font-size: var(--banx-text-2xs); letter-spacing: var(--banx-tracking-caps); text-transform: uppercase; white-space: nowrap; border-left: 1px solid var(--banx-line); } /* Through the register, not the raw accent. The bar pins its own ink values so * this resolves to the same green either way - but routing it through * --banx-accent-text means there is no exception to remember, and no exception * for tests/design-language.test.mjs to have to allow. */ .ex-act .n { color: var(--banx-accent-text); } /* Shown exactly where the link rail is hidden, and the thresholds are measured * rather than chosen. * * The bar's content column is capped at --banx-content whatever the viewport, so * it is 1240px wide at 1440px and at 1920px alike. Brand, six links and two * buttons already fill it: measured, adding the readout pushed the action group * onto a second row at every width from 1360px up, including 1920px. Making room * would mean dropping a nav item or letting the bar span wider than the text * column it sits above - a misalignment that reads as a bug. * * So the readout appears below 1220px, where the rail is hidden and there is * real room. That is also where it earns the most: with no links on screen, * nothing else says which chapter you are in. Below 560px even the burger and * the testnet button leave no space, so it goes again. */ @media (min-width: 560px) and (max-width: 1219px) { .ex-act { display: flex; } } /* A single row, always: brand, links and actions share one 72px bar. The * subnav used to be forced onto a second row with `flex: 1 0 100%`, which put * the logo above the buttons. It now sits inline and scrolls sideways when it * runs out of width. */ /* One row where the contents fit, two where they wrap, and the background * follows either way. This was pinned at a flat 72px while `.ex-nav > *` gave * each row that same 72px, so on a phone the subnav row painted 72px BELOW the * bar's box - outside its background and its border, over the scrolling page, * on transparent ground. `overflow: visible` meant nothing clipped and nothing * looked wrong in the stylesheet. */ .ex-nav.stack { height: auto; min-height: var(--banx-nav-h); } .ex-brand { gap: 10px; flex: 0 1 auto; min-width: 0; overflow: hidden; color: var(--banx-text); font-family: var(--banx-font-display); font-size: 1.16rem; font-weight: 600; letter-spacing: var(--banx-tracking-tight); white-space: nowrap; } .ex-brand:hover { color: var(--banx-text); } .ex-brand img { width: 30px; height: 36px; object-fit: contain; flex: 0 0 auto; } .ex-brand span { min-width: 0; overflow: hidden; color: var(--banx-subtle); font-family: var(--banx-font-mono); font-size: var(--banx-text-2xs); font-weight: 400; letter-spacing: .13em; text-transform: uppercase; text-overflow: ellipsis; } /* Link rails scroll sideways rather than wrapping, so the bar keeps its * declared height on every viewport. */ .ex-links, .ex-subnav { display: flex; align-items: center; gap: var(--banx-space-2); min-width: 0; overflow-x: auto; overflow-y: hidden; scrollbar-width: none; overscroll-behavior-x: contain; } .ex-links::-webkit-scrollbar, .ex-subnav::-webkit-scrollbar { height: 0; } .ex-links { flex: 1 1 auto; } .ex-subnav { flex: 1 1 auto; height: var(--banx-nav-h); } /* Every interactive target in a bar stays 44px in both directions. */ .ex-nav a, .ex-nav button, .ex-tabs button { display: inline-flex; align-items: center; justify-content: center; min-width: var(--banx-tap); min-height: var(--banx-tap); } .ex-links a, .ex-subnav a { flex: 0 0 auto; padding-inline: var(--banx-space-4); border: 1px solid transparent; border-radius: var(--banx-radius); color: var(--banx-muted); font-size: var(--banx-text-base); font-weight: 500; white-space: nowrap; transition: color var(--banx-fast) var(--banx-ease), background var(--banx-fast) var(--banx-ease); } /* No filled plate on hover. With the underline mark below doing the work, a * background as well is two signals for one state, and it is the one that made * the bar look like a row of buttons. */ .ex-links a:hover, .ex-subnav a:hover { color: var(--banx-text); } /* The active link is marked UNDER the word rather than boxed around it. * * The hairline chip this replaced put a rounded border around one item in a row * of plain words, which read as a button among links and made the bar look like * a toolbar. A 2px rule under the label is the same information with none of * that: it belongs to the word, it lines up across the whole rail, and it is the * mark the section eyebrows already use elsewhere on the page. * * The rule is a pseudo-element rather than a border-bottom so it can be inset * from the link's padding and sit under the text instead of under the hit area, * which at 44px tall is a long way below the word. */ .ex-links a.on, .ex-subnav a.on { color: var(--banx-text); border-color: transparent; background: transparent; } .ex-links a, .ex-subnav a { position: relative; } .ex-links a.on::after, .ex-subnav a.on::after { content: ""; position: absolute; left: var(--banx-space-4); right: var(--banx-space-4); bottom: calc(50% - .95em); height: 2px; background: var(--banx-mint); } /* Hover gets the same mark, faint, so the rail tells you where a click lands * before you make it. */ .ex-links a:not(.on)::after, .ex-subnav a:not(.on)::after { content: ""; position: absolute; left: var(--banx-space-4); right: var(--banx-space-4); bottom: calc(50% - .95em); height: 2px; background: var(--banx-line); transform: scaleX(0); transform-origin: center; transition: transform var(--banx-base) var(--banx-ease); } .ex-links a:not(.on):hover::after, .ex-subnav a:not(.on):hover::after { transform: scaleX(1); } .ex-net { gap: 8px; flex: 0 0 auto; padding-inline: var(--banx-space-3); color: var(--banx-muted); font-family: var(--banx-font-mono); font-size: var(--banx-text-2xs); letter-spacing: .13em; text-transform: uppercase; white-space: nowrap; } .ex-net b { color: var(--banx-accent-text); font-weight: 500; } .ex-net::before { content: ""; width: 6px; height: 6px; border-radius: 50%; background: var(--banx-mint); animation: banx-pulse 2.2s infinite; } .ex-wallet { position: relative; gap: var(--banx-space-3); flex: 0 0 auto; margin-left: auto; } /* Ghost nav action (Docs). */ .ex-navghost { height: 42px; padding-inline: 20px; color: var(--banx-accent-text); font-size: var(--banx-text-base); font-weight: 500; border: 1px solid var(--banx-mint-line); border-radius: var(--banx-radius); } .ex-navghost:hover { color: var(--banx-mint-hi); border-color: var(--banx-mint); background: var(--banx-mint-soft); } /* A promise the product cannot keep yet, shipped as a disabled span rather * than a dead : it is not a link, so it must not look or behave like one. */ .ex-soon { display: inline-flex; align-items: center; gap: 8px; height: 42px; padding-inline: 22px; color: var(--banx-subtle); font-size: var(--banx-text-base); font-weight: 600; white-space: nowrap; cursor: not-allowed; background: rgb(255 255 255 / 4%); border: 1px solid rgb(255 255 255 / 12%); border-radius: var(--banx-radius); } .ex-soon b { padding: 2px 7px; color: var(--banx-faint); font-family: var(--banx-font-mono); font-size: .58rem; font-weight: 400; letter-spacing: .12em; text-transform: uppercase; border: 1px solid rgb(255 255 255 / 12%); border-radius: var(--banx-radius); } /* Burger + full-screen menu, shown only where the link rail does not fit. */ .ex-burger { display: none; width: 42px; height: 42px; place-items: center; color: var(--banx-text); cursor: pointer; background: none; border: 1px solid rgb(255 255 255 / 16%); border-radius: var(--banx-radius); } .ex-mobmenu { position: fixed; inset: var(--banx-nav-h) 0 0; z-index: var(--banx-z-menu); display: flex; flex-direction: column; gap: 6px; padding: 28px var(--banx-gutter); overflow-y: auto; background: rgb(20 22 21 / 97%); backdrop-filter: blur(18px); } .ex-mobmenu[hidden] { display: none; } .ex-mobmenu a { padding: 15px 0; color: var(--banx-text); font-family: var(--banx-font-display); font-size: 1.5rem; font-weight: 600; border-bottom: 1px solid var(--banx-line); } .ex-mobmenu a.accent { color: var(--banx-accent-text); border-bottom: 0; } /* Scroll progress: a 2px brand line driven purely by CSS scroll timelines. * scaleX(0) is the base state, so browsers without animation-timeline simply * never show it. Injected by shell.js - decoration, not content. */ .ex-progress { position: fixed; top: 0; left: 0; right: 0; z-index: var(--banx-z-progress); height: 2px; background: var(--banx-mint); transform: scaleX(0); transform-origin: 0 50%; pointer-events: none; animation: banx-progress linear; animation-timeline: scroll(root block); } @keyframes banx-progress { from { transform: scaleX(0); } to { transform: scaleX(1); } } /* ================================================================ shell: page */ /* App pages: the same editorial rhythm as the marketing page, one step down. * They were opening 56px below the bar, which read as cramped next to the * 132px hero on the home page. */ .ex-wrap { width: min(100%, var(--banx-content)); margin-inline: auto; padding: var(--banx-section-sm) var(--banx-gutter) var(--banx-section); } .ex-wrap.app { width: min(100%, var(--banx-content-app)); } /* ============================================================== page headings * The numbered eyebrow is the signature section header: a 26px dash, a dim * index, and a green mono label. Sites write: *

01Faucet

markup. * * .ex-dl is `

` and puts the hairline on the

. * A