:root { --bg: #0f1115; --panel: #171a21; --panel-2: #1e222b; --border: #2a2f3a; --text: #e8eaed; --text-dim: #9aa2ad; --accent: #4f8cff; --accent-2: #2ecf7a; --danger: #ef5350; --radius: 10px; font-family: -apple-system, BlinkMacSystemFont, "Segoe UI", Roboto, Helvetica, Arial, sans-serif; } /* --------------------------------------------------------------------------- The admin surfaces in the corporate identity — white ground, ink type, the amber accent from the marketing site. Matthew, 2026-08-28: the backend should look like the front. Scoped to html[data-ui="light"] and deliberately NOT applied to :root. display.html — the television in a hotel lobby — carries 1,418 lines of its own CSS but defines only LAYOUT variables of its own, and reads --bg, --panel and --text from this file 69 times. Flipping the root here would turn every customer's screen white. So the screen keeps the dark palette above, and only the pages a staff member logs into opt in. The accent carries three jobs on white where on dark it carried one: --accent fills (a button, a progress dot) --accent-ink type ON those fills — amber needs dark type, never white --accent-text accent-coloured type on the white ground, darkened to stay legible; #ffad00 on #fff is about 1.7:1 and fails outright. -------------------------------------------------------------------------- */ html[data-ui="light"] { --bg: #ffffff; --panel: #f7f7f8; /* --panel-2 is the form-field and secondary-button surface. Missing it is what left the stat tiles, every input and the log-out button as dark boxes on a white page, with dark type inside them. */ --panel-2: #ffffff; --accent-2: #17864a; --border: #e4e4e7; --text: #0b0b0c; --text-dim: #5f6368; --accent: #ffad00; --accent-ink: #3d2900; --accent-text: #8a5c00; --danger: #c0392b; } /* Type on the accent. The base rules hardcode #fff, unreadable on amber. */ html[data-ui="light"] button, html[data-ui="light"] .btn, html[data-ui="light"] .btn-hero, html[data-ui="light"] .onboard-tabs button.active { color: var(--accent-ink); } /* Accent-coloured TEXT has to darken on a white ground. Not inside the navigation rail: that is dark in BOTH themes, so a colour chosen for a white ground is wrong there twice over. Left unexcluded, this rule painted the Studio link amber among grey siblings — it out-specifies `.side a` because of the attribute selector on . */ html[data-ui="light"] a:not(.side a), html[data-ui="light"] .link-btn, html[data-ui="light"] .brand span, html[data-ui="light"] .onboard-kicker { color: var(--accent-text); } /* The accent tints are hardcoded blue throughout (rgba(79,140,255,...)) because they predate the variable. Restated here in amber rather than rewritten as color-mix() at source: this stylesheet is also read by the screen path, and a colour function an old TV browser cannot parse drops the declaration outright, which is a worse failure than a stale blue. */ html[data-ui="light"] .onboard-icon { background: rgba(255,173,0,0.16); color: var(--accent-text); } html[data-ui="light"] .btn-hero { box-shadow: 0 8px 24px rgba(255,173,0,0.32); } html[data-ui="light"] .dropzone.dragover { background: rgba(255,173,0,0.12); } html[data-ui="light"] .library-item.assigned { box-shadow: 0 0 0 2px rgba(255,173,0,0.45); } html[data-ui="light"] .voice-preview-block.selected { background: rgba(255,173,0,0.28); } html[data-ui="light"] .sp-zone-instore { background: rgba(255,173,0,0.16); } html[data-ui="light"] .sp-zone-ad { background: rgba(255,173,0,0.08); } /* On dark, a field read as a field because it was lighter than the page. On white it is the same colour as the page, so the border has to do that work instead. */ html[data-ui="light"] input, html[data-ui="light"] select, html[data-ui="light"] textarea { border: 1px solid var(--border); } /* Keyboard focus. login.html defines an amber focus ring for its own fields and the dashboard defined none at all, so the moment a venue tabbed into anything past the front door the accent turned Chrome-default blue — the one colour this identity does not contain. Same ring on both sides of the login now. :focus-visible, not :focus, so a mouse click on a button does not paint one. */ html[data-ui="light"] input:focus-visible, html[data-ui="light"] select:focus-visible, html[data-ui="light"] textarea:focus-visible, html[data-ui="light"] button:focus-visible, html[data-ui="light"] .btn:focus-visible, html[data-ui="light"] a:focus-visible, html[data-ui="light"] summary:focus-visible, html[data-ui="light"] [tabindex]:focus-visible { outline: 2px solid var(--accent-text); outline-offset: 2px; } html[data-ui="light"] input:focus-visible, html[data-ui="light"] select:focus-visible, html[data-ui="light"] textarea:focus-visible { border-color: var(--accent-text); outline-offset: 0; } /* Every form in this product answers through .msg, and both colours were picked for a near-black page: #7fe3ac on the 12%-green tint over white is about 1.9:1 and #ff8a85 on the red tint about 2.4:1 — the confirmation you get for signing up, saving an element or inviting a partner was legible only if you already knew what it said. The tints stay (they are the thing that makes a result feel like a result); the type darkens onto them. */ html[data-ui="light"] .msg.ok { background: #eaf8f0; color: #0f6b3a; border-color: #b6e3c9; } html[data-ui="light"] .msg.error { background: #fdeceb; color: #a4271b; border-color: #f2c2bd; } /* A `code` chip and a `pre` block both painted themselves in --panel-2, which on white IS white — an inline SKU or endpoint had no chip at all and the curl example was a wall of unbounded text. */ html[data-ui="light"] code { background: var(--panel); border: 1px solid var(--border); } html[data-ui="light"] pre { background: var(--panel) !important; border: 1px solid var(--border); } /* White tick on amber is 1.8:1. The tick is the whole point of the checklist. */ html[data-ui="light"] .setup-tick { color: var(--accent-ink); } /* --line is not defined anywhere on this page, so every printable guest code fell back to the hardcoded dark-navy #2a3444 on a white card. */ html[data-ui="light"] .qr-card { border-color: var(--border); } html[data-ui="light"] .overview-stat { background: var(--panel); border: 1px solid var(--border); } /* .btn.secondary as well as button.secondary — an (the "Open the guest page" link on a package row) was getting the base rule only, so it never picked up the light hover and sat visibly apart from the real buttons beside it. */ html[data-ui="light"] button.secondary, html[data-ui="light"] .btn.secondary { background: #fff; color: var(--text); border: 1px solid var(--border); } html[data-ui="light"] button.secondary:hover, html[data-ui="light"] .btn.secondary:hover { background: var(--panel); } * { box-sizing: border-box; } body { margin: 0; background: var(--bg); color: var(--text); min-height: 100vh; overflow-x: hidden; } a { color: var(--accent); } .link-btn { background: none; border: none; padding: 0; margin: 0; color: var(--accent); font: inherit; cursor: pointer; text-decoration: underline; } .wrap { max-width: 1080px; margin: 0 auto; padding: 32px 20px 80px; } .topbar { display: flex; align-items: center; justify-content: space-between; padding: 16px 20px; border-bottom: 1px solid var(--border); } .brand { font-weight: 700; font-size: 1.15rem; letter-spacing: -0.02em; } .brand a { display: inline-flex; align-items: center; gap: 8px; } .brand span { color: var(--accent); } .card { background: var(--panel); border: 1px solid var(--border); border-radius: var(--radius); padding: 20px; margin-bottom: 20px; } .card h2, .card h3 { margin-top: 0; } input, select, textarea { width: 100%; padding: 10px 12px; background: var(--panel-2); border: 1px solid var(--border); border-radius: 8px; color: var(--text); font-size: 0.95rem; /* Form controls do not inherit font-family — that is a browser default, not an oversight of the cascade. Only font-size was being set here, so every