@charset "UTF-8"; /* The whole stylesheet. * * This was five Sass partials until it was plain CSS; the sections below are * where the partial boundaries used to be. Sass earned its place when the * only way to get variables and nesting was to compile for them. Both are * native now -- custom properties everywhere, and nesting in Chrome 120, * Firefox 117 and Safari 17.2, all from 2023 -- so the transpiler was buying * a `&__suffix` shorthand and an @import that Hugo can do by reading one * file. Dropping it also drops the hugo-extended requirement from * mise.toml, since SCSS was the only thing the site used it for. * * The one Sass feature with no native equivalent is `&` concatenation: * `.page { &__header {} }` cannot be expressed, because native `&` refers to * the parent selector rather than pasting its text. So BEM names are * written out in full. Nesting is kept for what it still does natively -- * pseudo-classes and short descendant chains -- and every nesting parent * here is a single selector, not a list, so `:is()`-wrapping `&` does not * move any specificity. */ /* ------------------------------------------------------------------ theme */ /* Every color in the stylesheet resolves to one of the custom properties * below. Keeping them as properties rather than build-time constants is * what lets one stylesheet carry both palettes: they are resolved by the * browser, so the single fingerprinted main.css holds light and dark and * `prefers-color-scheme` picks between them -- no toggle, no inline