/* GENERATED by tools/build_css.py from the files named below.
   Edit those, then run the tool. Do not edit this file. */

/* ==== static/vendor/fonts/fonts.css ==== */
/* Inter and Montserrat, self-hosted (static/vendor/LICENSES.txt).
   Variable fonts: one file per subset covers every weight the site uses.
   Generated from the Google Fonts css2 response; the unicode-range values
   are theirs, so latin-ext is only fetched by a page that needs it. */
@font-face {
    font-family: 'Inter';
    font-style: normal;
    font-weight: 300 700;
    font-display: swap;
    src: url('/static/vendor/fonts/inter-latin.woff2?v=1') format('woff2');
    unicode-range: U+0000-00FF, U+0131, U+0152-0153, U+02BB-02BC, U+02C6, U+02DA, U+02DC, U+0304, U+0308, U+0329, U+2000-206F, U+20AC, U+2122, U+2191, U+2193, U+2212, U+2215, U+FEFF, U+FFFD;
}
@font-face {
    font-family: 'Inter';
    font-style: normal;
    font-weight: 300 700;
    font-display: swap;
    src: url('/static/vendor/fonts/inter-latin-ext.woff2?v=1') format('woff2');
    unicode-range: U+0100-02BA, U+02BD-02C5, U+02C7-02CC, U+02CE-02D7, U+02DD-02FF, U+0304, U+0308, U+0329, U+1D00-1DBF, U+1E00-1E9F, U+1EF2-1EFF, U+2020, U+20A0-20AB, U+20AD-20C4, U+2113, U+2C60-2C7F, U+A720-A7FF;
}
@font-face {
    font-family: 'Montserrat';
    font-style: normal;
    font-weight: 600 800;
    font-display: swap;
    src: url('/static/vendor/fonts/montserrat-latin.woff2?v=1') format('woff2');
    unicode-range: U+0000-00FF, U+0131, U+0152-0153, U+02BB-02BC, U+02C6, U+02DA, U+02DC, U+0304, U+0308, U+0329, U+2000-206F, U+20AC, U+2122, U+2191, U+2193, U+2212, U+2215, U+FEFF, U+FFFD;
}
@font-face {
    font-family: 'Montserrat';
    font-style: normal;
    font-weight: 600 800;
    font-display: swap;
    src: url('/static/vendor/fonts/montserrat-latin-ext.woff2?v=1') format('woff2');
    unicode-range: U+0100-02BA, U+02BD-02C5, U+02C7-02CC, U+02CE-02D7, U+02DD-02FF, U+0304, U+0308, U+0329, U+1D00-1DBF, U+1E00-1E9F, U+1EF2-1EFF, U+2020, U+20A0-20AB, U+20AD-20C4, U+2113, U+2C60-2C7F, U+A720-A7FF;
}

/* ==== static/tokens.css ==== */
/* Design tokens, defined once for the whole site.
 *
 * These used to be copy-pasted into a :root block in each of 14 page
 * templates, which is how the styling drifted apart. base.html links this
 * first, so pages inherit the palette and only declare a token when they
 * genuinely differ from it.
 *
 * Page-level :root blocks still win, because a page's own <style> is parsed
 * after this file. Two pages rely on that today:
 *   journal_post      --main-text: #e8e8e8   (slightly brighter body copy)
 *   admin_seo_analysis --card: #1e1e1e       (darker cards)
 *
 * Deliberately NOT defined here: --text-secondary. Six pages reference it
 * without defining it, so their text currently inherits the body colour
 * instead of going muted. Defining it here would silently restyle 35
 * elements, which is a design decision rather than a consolidation, so it is
 * being handled separately.
 *
 * The short names (--text, --card, --border, --muted) are the vocabulary the
 * admin templates use; the long ones are what the public pages use. They are
 * kept as-is here rather than renamed, since renaming would mean touching
 * every rule that references them.
 */

/* Every page already applied this -- 14 templates declared it inline and the
   other 5 inherit it from styles.css or admin.css -- so hoisting it here
   changes nothing and removes 14 copies. */
* {
    box-sizing: border-box;
}

:root {
    /* Core palette */
    --main-dark: #121212;
    --main-text: #e0e0e0;
    --accent-teal: #5bc8d7;
    --accent-dark-teal: #3a9ba9;
    --accent-warm: #ff9a76;
    --card-bg: #232323;
    --header-bg: #2c2c2c;
    --border-color: #3a3a3a;

    /* Short aliases, used by the admin templates */
    --bg: #1a1a1a;
    --text: #e0e0e0;
    --card: #232323;
    --border: #3a3a3a;
    --muted: #999;

    /* Text roles.
       These were referenced across the site but defined nowhere, so every
       `color: var(--text-secondary)` silently fell back to the inherited body
       colour and the text never went muted. --text-primary and --text-color
       resolve to the same value the text was already inheriting, so only
       --text-secondary changes anything on screen. */
    --text-primary: #e0e0e0;
    --text-color: #e0e0e0;
    --text-secondary: #999;

    /* Status colours */
    --good: #7ed957;
    --bad: #e57373;
    --danger: #e57373;
    --error: #ef4444;
}

/* ==== static/site-header.css ==== */
/* Site topbar (templates/_site_header.html): one compact band, wordmark left,
 * nav right. Replaces the earlier two-band masthead-above-nav layout — chosen
 * because the centered wordmark left large empty space either side and cost
 * ~46px of extra height on every page.
 *
 * The nav's own bar styling (site-nav.css) is neutralised inside the topbar
 * via the higher-specificity .topbar .site-nav rules below, so site-nav.css
 * keeps working standalone if the nav is ever rendered outside the topbar.
 */

.topbar {
    display: flex;
    align-items: center;
    justify-content: space-between;
    /* Wraps the nav onto its own line once it no longer fits beside the
       wordmark. Without this the bar stays one line and the nav, being
       justify-content: flex-end, spills its overflow leftwards straight over
       the wordmark -- visible between roughly 770px and 1010px, i.e. any
       part-width desktop window. Wrapping is content-driven, so it keeps
       working if nav items are added or renamed. */
    flex-wrap: wrap;
    gap: 4px 24px;
    padding: 9px 22px;
    background: rgba(18, 18, 18, 0.85);
    backdrop-filter: blur(10px);
    border-bottom: 1px solid var(--border-color, #3a3a3a);
}

.topbar-logo-link,
.topbar-logo-link:hover,
.topbar-logo-link:visited {
    display: inline-flex;
    align-items: center;
    gap: 10px;
    text-decoration: none;
    color: inherit;
    flex-shrink: 0;
}

/* alt="" — the wordmark beside it already names the site, so announcing the
   mark again would just be noise for screen readers. */
.topbar-mark {
    width: auto;
    height: 30px;
    display: block;
    flex-shrink: 0;
}

.masthead-logo {
    display: inline-block;
    font-family: 'Montserrat', sans-serif;
    font-weight: 800;
    font-size: clamp(1.1rem, 2.2vw, 1.4rem);
    letter-spacing: 1.5px;
    line-height: 1.2;
    background: linear-gradient(135deg, var(--accent-teal), var(--accent-warm));
    -webkit-background-clip: text;
    background-clip: text;
    -webkit-text-fill-color: transparent;
}

.topbar .site-nav {
    background: transparent;
    backdrop-filter: none;
    border-bottom: none;
    margin: 0;
    padding: 0;
    justify-content: flex-end;
    /* No min-width: 0 here. That let the nav shrink below its content, which
       is what produced the overflow instead of a wrap. Leaving min-width at
       its auto (min-content) default is what lets .topbar wrap it. */
    flex: 1 1 auto;
}

/* ---------------------------------------------------------------------------
   Shared page heading.

   Page h1s had drifted to five different sizes -- 1.15rem on the event pages
   and up to 2.6rem on journal_post -- so the same heading role looked
   different on every page. This is the single scale; per-page h1 font-size
   overrides were removed so they all inherit it.

   `h1` and `.page-h1` are both styled: pages with a natural page title use a
   bare <h1>, while the event pages (home, city, tonight, bar hop) add the
   class to an h1 that sits above dense content.
   --------------------------------------------------------------------------- */
h1,
.page-h1 {
    font-family: 'Montserrat', sans-serif;
    font-size: clamp(1.35rem, 2.6vw, 1.8rem);
    font-weight: 700;
    line-height: 1.25;
    letter-spacing: 0.2px;
    margin: 0 0 10px;
    color: var(--main-text, #e0e0e0);
}

/* Standard intro paragraph under a page heading. */
.lead {
    font-size: 1rem;
    line-height: 1.6;
    color: #bbb;
    margin: 0 0 22px;
    max-width: 760px;
}

@media (max-width: 768px) {
    .topbar {
        flex-direction: column;
        align-items: stretch;
        gap: 6px;
        padding: 8px 10px 6px;
        /* Blur forces per-frame repaints while scrolling; same tradeoff as
           the nav and styles.css make on mobile. */
        backdrop-filter: none;
        -webkit-backdrop-filter: none;
    }

    .topbar-logo-link {
        text-align: center;
    }

    /* flex-start, not center: this selector outranks the mobile `.site-nav`
       rule in site-nav.css, and centring a horizontal scroll container parks
       the first link at a negative scroll offset that cannot be reached. The
       ::before/::after spacers in site-nav.css centre the row while it fits.
       See the comment there before changing this back. */
    .topbar .site-nav {
        justify-content: flex-start;
        flex: initial;
    }

    /* Page headings step down on phones. The clamp alone bottoms out at its
       floor here, which left long headings -- especially the home page
       tagline -- wrapping to three lines and dominating the screen. */
    h1,
    .page-h1 {
        font-size: 1.2rem;
        line-height: 1.3;
        margin-bottom: 8px;
    }

    /* .page-h1 is the descriptive line above dense content on the event
       pages, not a page title, so it goes smaller still. */
    .page-h1 {
        font-size: 1rem;
        letter-spacing: 0.3px;
    }

    .lead {
        font-size: 0.94rem;
        margin-bottom: 18px;
    }

    /* Page subtitles -- the one-line description under an h1 on about,
       support, privacy, feedback and journal posts. Each template sets its
       own size (0.9rem to 1.1rem) with no mobile step-down, so on a phone
       every one of them wrapped to two or three lines and read as body copy
       rather than as a caption under the heading.

       `p.subtitle` rather than `.subtitle`: page <style> blocks render after
       this file (see base.html), so a bare class selector would lose to them
       on source order alone. Every use of the class is on a <p>. */
    p.subtitle {
        font-size: 0.85rem;
        line-height: 1.4;
    }
}

/* "Skip to content": the first thing a keyboard reaches on every page
   (base.html). Off screen until it has focus. */
.skip-link {
    position: absolute;
    left: 8px;
    top: 8px;
    z-index: 10000;
    padding: 10px 16px;
    border-radius: 6px;
    border: 2px solid var(--accent-teal);
    background: var(--main-dark);
    color: #fff;
    font: 600 0.95rem/1.2 'Inter', sans-serif;
    text-decoration: none;
    transform: translateY(-200%);
}

.skip-link:focus {
    transform: none;
    outline: 2px solid #fff;
    outline-offset: 2px;
}

/* The link's target takes focus so the next Tab starts in the content; it
   should not draw a ring around the whole page for that. */
main:focus {
    outline: none;
}

/* ==== static/site-nav.css ==== */
/* Styling for the shared nav partial (templates/_site_nav.html).
 *
 * These rules used to live only in styles.css, which just three pages link
 * (events, city, tonight). Every other page rendered the nav as raw browser
 * links -- default blue and underlined. base.html now links this file, so the
 * nav looks the same everywhere.
 *
 * Every selector here is .site-nav* or .nav-action-*, and those class names
 * appear nowhere except the nav partial, so this file cannot affect anything
 * else on a page.
 *
 * Palette variables carry fallbacks: journal_index, journal_post and
 * venues_index define their own :root without --accent-dark-teal, and the
 * active-tab gradient needs it.
 */

.site-nav {
    display: flex;
    justify-content: center;
    align-items: center;
    gap: 8px;
    padding: 10px 20px;
    background: rgba(18, 18, 18, 0.85);
    backdrop-filter: blur(10px);
    border-bottom: 1px solid var(--border-color, #3a3a3a);
}

.site-nav a {
    color: var(--main-text, #e0e0e0);
    text-decoration: none;
    padding: 8px 18px;
    border-radius: 20px;
    font-size: 0.9rem;
    font-weight: 500;
    transition: all 0.2s ease;
    letter-spacing: 0.3px;
}

.site-nav a:hover {
    color: var(--accent-teal, #5bc8d7);
    background: rgba(91, 200, 215, 0.1);
}

.site-nav a.active {
    color: #fff;
    background: linear-gradient(135deg, var(--accent-teal, #5bc8d7), var(--accent-dark-teal, #3a9ba9));
    font-weight: 600;
}

.nav-action-buttons {
    display: flex;
    align-items: center;
    gap: 6px;
    margin-left: 12px;
    padding-left: 12px;
    border-left: 1px solid rgba(255, 255, 255, 0.1);
}

.nav-action-btn {
    display: flex;
    align-items: center;
    gap: 5px;
    background: rgba(91, 200, 215, 0.1);
    border: 1px solid rgba(91, 200, 215, 0.3);
    color: var(--accent-teal, #5bc8d7);
    border-radius: 20px;
    padding: 6px 14px;
    font-size: 0.82rem;
    font-weight: 500;
    cursor: pointer;
    transition: all 0.2s ease;
    font-family: 'Inter', sans-serif;
    white-space: nowrap;
}

.nav-action-btn:hover {
    background: rgba(91, 200, 215, 0.2);
    border-color: var(--accent-teal, #5bc8d7);
    transform: translateY(-1px);
}

.nav-action-subscribe {
    background: rgba(255, 154, 118, 0.1);
    border-color: rgba(255, 154, 118, 0.3);
    color: var(--accent-warm, #ff9a76);
}

/* Beer pill is an <a>, so double up specificity to beat the generic
   `.site-nav a` link rules (padding, color, hover background). Filled warm
   gradient marks it as the one CTA in the bar. */
.site-nav a.nav-action-beer {
    display: flex;
    align-items: center;
    gap: 5px;
    padding: 6px 14px;
    font-size: 0.82rem;
    font-weight: 600;
    border-radius: 20px;
    color: #fff;
    background: linear-gradient(135deg, var(--accent-warm, #ff9a76), #d97a52);
    border: 1px solid transparent;
    white-space: nowrap;
}

.site-nav a.nav-action-beer:hover {
    color: #fff;
    background: linear-gradient(135deg, var(--accent-warm, #ff9a76), #d97a52);
    filter: brightness(1.08);
    transform: translateY(-1px);
}

@media (max-width: 768px) {
    .site-nav {
        gap: 4px;
        padding: 6px 8px;
        flex-wrap: nowrap;
        overflow-x: auto;
        -webkit-overflow-scrolling: touch;
        scrollbar-width: none;
        /* Deliberately NOT justify-content: center. Centring a scroll
           container splits the overflow across both ends, and the leading
           half lands at a negative scroll offset that nothing can reach --
           "All Events" rendered as "ents" with no way to scroll back to it.
           The auto-margin spacers below centre the row while it fits and
           collapse to zero once it overflows (auto margins only absorb
           positive free space), so the first link always sits at
           scrollLeft 0. */
        justify-content: flex-start;
        /* Blur is dropped on mobile: it forces per-frame repaints while
           scrolling long lists. Matches the same tradeoff in styles.css. */
        backdrop-filter: none;
        -webkit-backdrop-filter: none;
    }

    .site-nav::before,
    .site-nav::after {
        content: '';
        margin: auto;
    }

    .site-nav::-webkit-scrollbar {
        display: none;
    }

    .site-nav a {
        font-size: 0.75rem;
        padding: 5px 8px;
        white-space: nowrap;
        flex-shrink: 0;
    }

    /* Fixed, not `margin-left: auto`: an auto margin here would swallow the
       free space the ::before/::after spacers need to centre the row. */
    .nav-action-buttons {
        margin-left: 8px;
        padding-left: 8px;
        flex-shrink: 0;
    }
}

/* Phones. The full nav -- five links plus the beer pill -- measures ~410px
   against a ~355px bar at 375px wide, so something has to give or the row
   scrolls on every page. Dropping the pill's text label reclaims ~80px, which
   is enough for the whole nav to fit unscrolled, and keeps the CTA visible as
   its orange pill rather than clipped mid-word. The full "Buy Us a Beer"
   wording still appears in the footer and on /support. */
@media (max-width: 480px) {
    /* Every value below is spent buying horizontal room. With the label gone
       and these paddings the row measures ~369px, which fits unscrolled on a
       modern phone (390px+ of viewport). Smaller handsets still overflow and
       scroll -- correctly, from the first link -- so nothing is ever hidden. */
    .site-nav {
        gap: 3px;
    }

    .site-nav a {
        padding: 5px 6px;
    }

    .nav-action-buttons {
        margin-left: 6px;
        padding-left: 6px;
    }

    .site-nav a.nav-action-beer {
        padding: 6px 10px;
    }

    .site-nav a.nav-action-beer .nav-beer-label {
        display: none;
    }

    .site-nav a.nav-action-beer .icon {
        width: 18px;
        height: 18px;
    }
}

/* ==== static/site-footer.css ==== */
/* Shared site footer (templates/_site_footer.html).
 *
 * Carries its own copy of the .social-links styling: the icon partial was
 * only styled inside styles.css and a few page templates, so on any other
 * page the icons rendered as bare links. With the footer now global, the
 * styling has to be too. styles.css keeps its identical copy for the three
 * pages that link it; dedupe alongside the .site-nav dedupe.
 *
 * --text-secondary carries a fallback: most pages do not define it (the
 * known dead-token issue documented in BASE_TEMPLATE_MIGRATION.md).
 */

.site-footer {
    text-align: center;
    padding: 24px 16px 30px;
    margin-top: 40px;
    border-top: 1px solid var(--border-color, #3a3a3a);
    color: var(--text-secondary, #999);
    font-size: 0.85rem;
}

.site-footer-links {
    margin: 12px 0 0;
}

.site-footer-links a {
    color: var(--accent-teal, #5bc8d7);
    text-decoration: none;
}

.site-footer-links a:hover {
    color: var(--accent-warm, #ff9a76);
}

.social-links {
    display: flex;
    justify-content: center;
    align-items: center;
    gap: 14px;
    margin: 14px 0 6px 0;
}

.social-link {
    display: inline-flex;
    align-items: center;
    justify-content: center;
    width: 38px;
    height: 38px;
    border-radius: 50%;
    color: var(--text-secondary, #999);
    background: rgba(255, 255, 255, 0.04);
    border: 1px solid rgba(255, 255, 255, 0.08);
    transition: color 0.2s, background 0.2s, transform 0.15s, border-color 0.2s;
    text-decoration: none;
}

.social-link:hover {
    color: var(--accent-teal, #5bc8d7);
    background: rgba(91, 200, 215, 0.12);
    border-color: rgba(91, 200, 215, 0.4);
    transform: translateY(-2px);
}
