/* * theme.css — WRITTEN BY THE PLATFORM. Do not edit. * * Palette: Your colours (custom) * Source colours: #03060b #20242b #f6f4f0 #12294d #1b3a6b #ffffff * * Every value below is either one of those five or derived from them, and each * one is contrast-corrected against this palette's own background. Consume * them with var(--token); never write a colour value in app code. */ :root { --canvas: #f6f4f0; --surface: #fbfaf8; --surface-2: #eae8e5; --border: #d4d3d0; --border-strong: #adadab; --ink: #20242b; --muted: #6d6d70; --accent: #12294d; --accent-hover: #0f2341; --accent-ink: #ffffff; --accent-text: #1b3a6b; --accent-strong: #12294d; --accent-soft: #d6d8d9; --accent-border: #8f99a7; --success: #15803d; --success-ink: #ffffff; --success-soft: #dbe6db; --success-strong: #116d34; --warning: #b45309; --warning-ink: #ffffff; --warning-soft: #eee1d4; --warning-strong: #994607; --danger: #b91c1c; --danger-ink: #ffffff; --danger-soft: #efdad7; --danger-strong: #b91c1c;} /* The same palette on a dark page — written here, never by the app. It applies while carries data-theme="dark", which the platform's own toggle sets and remembers; an app that never renders that toggle is exactly as it was. Do not repoint any of these from app code: a token that references another token here is a cycle, and CSS makes every property in a cycle invalid. */ html[data-theme="dark"] { --canvas: #03060b; --surface: #1c1f23; --surface-2: #101217; --border: #26292d; --border-strong: #4f5154; --ink: #f6f4f0; --muted: #959594; --accent: #253a5b; --accent-hover: #465874; --accent-ink: #ffffff; --accent-text: #6f7c92; --accent-strong: #7b869b; --accent-soft: #0a111d; --accent-border: #121d2f; --success: #15803d; --success-ink: #ffffff; --success-soft: #072116; --success-strong: #499c68; --warning: #b45309; --warning-ink: #ffffff; --warning-soft: #2a170b; --warning-strong: #c57a40; --danger: #b91c1c; --danger-ink: #ffffff; --danger-soft: #2b0b0f; --danger-strong: #cd5c5c; } /* ==================================================================== * app.css — THIS APP'S OWN CSS. Yours to write. Ships empty. * * design.css is a FLOOR, not a ceiling. * * For a long time it was both, and the cost was measurable: an app could * not write a single CSS rule, so every app built here had the same 10px * radius, the same Public Sans at the same 15px, the same 1px borders and * the same soft shadow. Only fourteen COLOUR tokens ever differed. Three * apps in a row came out looking like the same product in three coats of * paint, which is what this file exists to end. * * It loads AFTER design.css and theme.css, so anything here wins. * * ---- THE FIRST LEVER: RETUNE THE SYSTEM --------------------------- * * A :root block here re-tunes every component at once — nothing is * restyled one class at a time. These are the tokens that decide an app's * CHARACTER, and they are the fastest way to make two apps look nothing * alike: * * --radius-sm --radius --radius-lg 0 is brutal, 4 is crisp, 18 is soft * --font-sans --font-mono a display face changes more than colour * --t-xs … --t-5xl the type scale, and how far it ramps * --lh --lh-tight --track-tight density and tone * --s-1 … --s-12 the spacing scale: tight or generous * --shadow --shadow-raised flat, or lifted * --border --border-strong widths hairline, or heavy and drawn * --dur-1 --dur-2 --ease brisk, or languid * --content-max --measure a wide dashboard or a narrow reading page * * COLOUR IS THE ONE EXCEPTION, and it is not a technicality: the owner * picked the palette on the approval card before you built anything, and * it is the only part of the look they chose themselves. theme.css holds * it. Write var(--accent), var(--ink), var(--canvas) — never a hex, an * rgb() or an hsl(), here or anywhere. The validator refuses those. * * ---- THE SECOND LEVER: WRITE WHAT IS NOT THERE --------------------- * * design.css covers the ordinary furniture. It does NOT cover the one * screen that makes this app itself — a timer's dial, a board's columns, * a chart, a seating plan, a game grid. Write those here, in full, and * name them for what they are (.dial, .board-col), never .card-2. * * Compose the primitives where they fit and write your own where they do * not. An app that used only the frozen classes and added nothing shipped * 160 component classes and zero rules of its own — and read as generated, * because the system's ceiling had become the app's ceiling. * * Keep using the tokens in what you write. A rule built on var(--s-4) and * var(--radius) stays consistent with everything around it and follows the * app when its character changes; one built on 16px and 10px does not. * ==================================================================== */ /* GrandHall — bold and corporate, built for a large exhibition venue. Crisp corners, heavier rules and a brisk motion feel — closer to a trade-show programme than a soft consumer app. */ :root { --radius-sm: 4px; --radius: 8px; --radius-lg: 14px; --track-tight: -0.02em; --dur-1: 120ms; --dur-2: 200ms; } /* Headlines read tighter and heavier — a programme title, not a blog post. */ .page-title, h1 { letter-spacing: var(--track-tight); } /* The brand mark is a hard-edged tile, not a soft rounded badge — it reads like a venue signage block. */ .brand-mark { border-radius: var(--radius-sm); font-weight: 700; letter-spacing: 0; } .topnav .nav-item[aria-current="page"] { font-weight: 600; } /* Hero band: keep the scrim readable regardless of the photo underneath. */ .hero-media { background: var(--ink); } .table thead th { text-transform: uppercase; letter-spacing: 0.04em; font-size: var(--t-xs); } .table td.truncate, .table td .truncate { font-variant-numeric: tabular-nums; }