/* ==========================================================================
   VacancyDubai.ae — component layer (ported from the design POC)
   Phase 1 of the POC design migration, 24 Sep 2026.

   Loaded AFTER main.css. Consumes the Palette A tokens defined in main.css
   (--uae-*, --r-*, --shadow-*) and defines no colours of its own.

   Source of truth for the visual language: C:\xampp\htdocs\vacancydubai-poc
   (poc-theme.css + poc-pages.css). Class names match the POC one for one,
   with the poc- prefix renamed to vd-, so the POC stays a usable reference.

   Not ported: the four candidate palettes, the decoration switch, the POC
   switcher chrome, the token inspector, and poc-shell.js.
   ========================================================================== */
/* ---------- 3. BASE ----------------------------------------------------- */

body.vd-page {
    margin: 0;
    background: var(--uae-sand);
    color: var(--uae-body);
    font-family: "Open Sans", system-ui, sans-serif;
    font-size: 16px;
    line-height: 1.6;
    -webkit-font-smoothing: antialiased;
}
html[dir="rtl"] body.vd-page { font-family: "IBM Plex Sans Arabic", "Open Sans", system-ui, sans-serif; }

.vd h1, .vd h2, .vd h3, .vd h4 {
    margin: 0;
    color: var(--uae-ink);
    font-family: Montserrat, system-ui, sans-serif;
    font-weight: var(--weight-heading);
    line-height: 1.25;
}
.vd h1 { font-size: 34px; }
.vd h2 { font-size: 24px; }
.vd h3 { font-size: 18px; }
.vd h4 { font-size: 15px; }
/* Link colour applies to plain text links only. A rule like `.vd a` is
   specificity 0,1,1 and would outrank every single-class component that sets
   its own colour (.vd-btn, .tile, .vd-skill, .vd-emirate, .job-card__title …),
   which painted anchor buttons primary-on-primary. */
.vd a { text-decoration: none; }
.vd a:not([class]) { color: var(--uae-primary-ink); }
.vd a:not([class]):hover { text-decoration: underline; }

.vd-eyebrow {
    display: block;
    margin-bottom: 6px;
    color: var(--uae-primary-ink);
    font-size: 11px;
    font-weight: 700;
    letter-spacing: .09em;
    text-transform: var(--eyebrow-transform);
}
.vd-muted { color: var(--uae-muted); }
.vd-wrap { max-width: 1180px; margin: 0 auto; padding: 0 20px; }
.vd-section { padding: 34px 0; border-top: 1px solid var(--uae-line); }
.vd-section:first-of-type { border-top: 0; }
.vd-grid { display: grid; gap: 16px; }
.vd-note {
    margin: 10px 0 0;
    padding: 10px 14px;
    border-left: 3px solid var(--uae-line);
    color: var(--uae-muted);
    font-size: 13px;
}

/* ---------- 4. CONTROLS ------------------------------------------------- */

.vd-btn {
    display: inline-flex;
    align-items: center;
    justify-content: center;
    gap: 8px;
    height: 44px;
    padding: 0 20px;
    border: 1px solid transparent;
    border-radius: var(--r-control);
    background: var(--uae-primary);
    color: #fff;
    font-size: 15px;
    font-weight: var(--weight-strong);
    cursor: pointer;
    transition: background .15s ease, border-color .15s ease;
}
.vd-btn:hover { background: var(--uae-primary-deep); }
.vd-btn--ghost { background: transparent; border-color: var(--uae-line); color: var(--uae-primary-ink); }
.vd-btn--ghost:hover { background: var(--uae-primary-wash); border-color: var(--uae-primary); }
.vd-btn--quiet { background: transparent; border-color: transparent; color: var(--uae-muted); }
.vd-btn--pill { border-radius: var(--r-pill); }
.vd-btn--sm { height: 36px; padding: 0 14px; font-size: 13px; }

/* anchors used as buttons: state the colour explicitly so no link rule can win.
   The hover rule has to exclude the light variants, or it would paint them
   white on their own pale hover background. */
.vd a.vd-btn { color: #fff; }
.vd a.vd-btn:hover { text-decoration: none; }
.vd a.vd-btn:not(.vd-btn--ghost):not(.vd-btn--quiet):hover { color: #fff; }
.vd a.vd-btn--ghost,
.vd a.vd-btn--ghost:hover { color: var(--uae-primary-ink); }
.vd a.vd-btn--quiet,
.vd a.vd-btn--quiet:hover { color: var(--uae-muted); }

.vd-input {
    width: 100%;
    height: 44px;
    padding: 0 14px;
    border: 1px solid var(--uae-line);
    border-radius: var(--r-control);
    background: var(--uae-surface);
    color: var(--uae-ink);
    font-size: 15px;
}
.vd-input:focus {
    outline: 0;
    border-color: var(--uae-primary);
    box-shadow: 0 0 0 3px var(--uae-primary-wash);
}

/* ---------- 5. BADGES / PILLS ------------------------------------------ */

.vd-badge {
    display: inline-flex;
    align-items: center;
    gap: 5px;
    padding: 4px 10px;
    border-radius: var(--r-pill);
    background: var(--uae-primary-wash);
    color: var(--uae-primary-ink);
    font-size: 11px;
    font-weight: 700;
    line-height: 1.5;
    white-space: nowrap;
}
.vd-badge--featured { background: var(--uae-gold-wash); color: var(--uae-gold-text); }
.vd-badge--type { background: var(--uae-sand); color: var(--uae-body); border: 1px solid var(--uae-line); }
.vd-badge--fresh { background: var(--uae-primary-wash); color: var(--uae-primary-ink); }
.vd-badge--stale { background: transparent; color: var(--uae-muted); border: 1px solid var(--uae-line); }
.vd-verified { color: var(--uae-ok); font-size: 12px; }
.vd-unverified { color: var(--uae-muted); font-size: 12px; }

.vd-skill {
    display: inline-flex;
    align-items: center;
    gap: 6px;
    padding: 4px 10px;
    border: 1px solid var(--uae-line);
    border-radius: var(--r-pill);
    color: var(--uae-muted);
    font-size: 12px;
}
/* The market chip's symbol. Smaller than the 12px label and a step back in
   opacity: it is a scanning aid, and a chip whose icon outweighs its name is
   a chip you read twice. */
.vd-skill__ico { color: var(--uae-primary-ink); font-size: 11px; opacity: .8; }

/* emirate count chips (homepage suggestion) */
.vd-emirates { display: flex; flex-wrap: wrap; gap: 8px; }
.vd-emirate {
    display: inline-flex;
    align-items: center;
    gap: 8px;
    padding: 9px 14px;
    border: 1px solid var(--uae-line);
    border-radius: var(--r-pill);
    background: var(--uae-surface);
    color: var(--uae-ink);
    font-size: 14px;
    font-weight: var(--weight-strong);
    cursor: pointer;
}
.vd-emirate span {
    min-width: 22px;
    padding: 1px 7px;
    border-radius: var(--r-pill);
    background: var(--uae-sand);
    color: var(--uae-muted);
    font-size: 11px;
    font-weight: 700;
    text-align: center;
}
.vd-emirate:hover { border-color: var(--uae-primary); }
.vd-emirate.is-on { border-color: var(--uae-primary); background: var(--uae-primary-wash); color: var(--uae-primary-ink); }
.vd-emirate.is-on span { background: var(--uae-primary); color: #fff; }

/* ---------- 6. JOB CARDS ----------------------------------------------- */

.job-card {
    display: flex;
    flex-direction: column;
    gap: 12px;
    padding: 18px;
    border: var(--card-border);
    border-radius: var(--r-card);
    background: var(--uae-surface);
    box-shadow: var(--shadow-card);
}
.job-card__head { display: flex; align-items: flex-start; gap: 12px; }
.job-card__logo {
    display: grid;
    place-items: center;
    width: 52px;
    height: 52px;
    flex: 0 0 52px;
    border: 1px solid var(--uae-line);
    border-radius: var(--r-control);
    background: var(--uae-sand);
    color: var(--uae-primary-ink);
    font-family: Montserrat, sans-serif;
    font-size: 16px;
    font-weight: 700;
}
.job-card__badges { display: flex; flex-wrap: wrap; gap: 6px; margin-left: auto; }
html[dir="rtl"] .job-card__badges { margin-left: 0; margin-right: auto; }
.job-card__title { font-size: 17px; }
.job-card__title a { color: var(--uae-ink); }
.job-card__title a:hover { color: var(--uae-primary-ink); text-decoration: none; }
.job-card__employer { display: flex; align-items: center; gap: 6px; font-size: 13px; color: var(--uae-muted); }
/* 2026-11-07: a job saved with no company still renders a card - see the
   header comment in job/partials/listing_item_card.blade.php. Muted rather
   than --uae-primary-ink, because "no employer named" is an absence and
   not a brand accent; italic so the line does not read as a company that
   is literally called "Employer not specified". Tokens only, so
   vd-theme-dark.css needs no rebuild. */
.job-card__logo--none { color: var(--uae-muted); }
.job-card__employer--none { font-style: italic; }

/* salary is the loudest thing on the card */
.job-card__salary { color: var(--uae-ink); font-size: 16px; font-weight: 700; }
.job-card__salary small { color: var(--uae-muted); font-size: 12px; font-weight: 400; }
.job-card__salary.is-hidden { color: var(--uae-muted); font-size: 14px; font-weight: 400; font-style: italic; }

.job-card__meta { display: flex; flex-wrap: wrap; gap: 14px; color: var(--uae-muted); font-size: 13px; }
.job-card__meta i { margin-right: 5px; opacity: .6; }
html[dir="rtl"] .job-card__meta i { margin-right: 0; margin-left: 5px; }
.job-card__skills { display: flex; flex-wrap: wrap; gap: 6px; }
.job-card__foot {
    display: flex;
    align-items: center;
    justify-content: space-between;
    gap: 12px;
    padding-top: 12px;
    border-top: 1px solid var(--uae-line);
}
.job-card--featured { border-color: var(--uae-gold-line); }

/* ---------- the whole card is the target (2026-10-20) ------------------
   The card holds four interactive elements, so it cannot be wrapped in an
   <a>. The title link is stretched over it instead: its ::after covers the
   card and a click anywhere activates it. The title is the right owner --
   its text is already the card's accessible name, so nothing is added for
   a screen reader and there is no second link to tab through.

   Debugging note: that overlay is a pseudo-element. It takes part in
   hit-testing but will not appear anywhere in the DOM tree. */
.job-card { position: relative; cursor: pointer; }
/* a border-colour change, which is the house hover for cards -- the lift
   was deliberately removed from these (see the decoration notes) */
.job-card:hover { border-color: var(--uae-primary); }
.job-card__title a::after {
    content: '';
    position: absolute;
    inset: 0;
    z-index: 1;
}
/* The genuine links sit above the overlay. [href] and not the tag: with
   features.company_directory off, the logo and the employer are <a> with no
   href, and lifting those would make a click on the logo do nothing instead
   of opening the job. The same test lets them take over again on their own
   if that flag is turned back on. */
.job-card a[href]:not(.job-card__title a),
.job-card button { position: relative; z-index: 2; }
/* Keyboard parity: the stretched link is still just the title, so without
   this only the title text would show focus on a card-sized target. */
.job-card:has(.job-card__title a:focus-visible) {
    border-color: var(--uae-primary);
    box-shadow: 0 0 0 3px rgba(var(--uae-primary-rgb), .18);
}

/* row variant */
.job-row { display: grid; grid-template-columns: 52px 1fr auto; gap: 16px; align-items: center; }
.job-row__cta { display: flex; flex-direction: column; align-items: flex-end; gap: 8px; }
@media (max-width: 767.98px) {
    .job-row { grid-template-columns: 44px 1fr; }
    .job-row__cta { grid-column: 1 / -1; align-items: stretch; }
}

/* ---------- 7. LISTING CHROME ------------------------------------------ */

.vd-toolbar { display: flex; align-items: flex-end; justify-content: space-between; gap: 16px; margin-bottom: 16px; }
.vd-toolbar h2 { font-size: 22px; }
.vd-sort { display: flex; align-items: center; gap: 10px; color: var(--uae-muted); font-size: 13px; }
.vd-sort select {
    height: 40px;
    min-width: 170px;
    padding: 0 12px;
    border: 1px solid var(--uae-line);
    border-radius: var(--r-pill);
    background: var(--uae-surface);
    color: var(--uae-ink);
    font-size: 14px;
    font-weight: var(--weight-strong);
}

.vd-chips { display: flex; flex-wrap: wrap; align-items: center; gap: 8px; margin-bottom: 18px; }
.vd-chip {
    display: inline-flex;
    align-items: center;
    gap: 7px;
    padding: 7px 12px;
    border: 1px solid var(--uae-line);
    border-radius: var(--r-pill);
    background: var(--uae-surface);
    color: var(--uae-body);
    font-size: 12px;
    font-weight: var(--weight-strong);
    cursor: pointer;
}
.vd-chip:hover { border-color: var(--uae-primary); color: var(--uae-primary-ink); }
.vd-chip i { opacity: .5; font-size: 10px; }
.vd-chip--clear { border-color: transparent; background: transparent; color: var(--uae-primary-ink); }

.vd-filter {
    padding: 20px;
    border: var(--card-border);
    border-radius: var(--r-card);
    background: var(--uae-surface);
    box-shadow: var(--shadow-card);
}
.vd-filter__group { margin-top: 20px; padding-top: 20px; border-top: 1px solid var(--uae-line); }
.vd-filter__group:first-of-type { margin-top: 14px; }
.vd-facet { display: flex; align-items: center; gap: 10px; padding: 7px 0; font-size: 14px; }
.vd-facet input { width: 17px; height: 17px; accent-color: var(--uae-primary); }
.vd-facet span {
    margin-left: auto;
    min-width: 26px;
    padding: 1px 7px;
    border-radius: var(--r-pill);
    background: var(--uae-sand);
    color: var(--uae-muted);
    font-size: 11px;
    font-weight: 700;
    text-align: center;
}
html[dir="rtl"] .vd-facet span { margin-left: 0; margin-right: auto; }
.vd-facet input:checked ~ span { background: var(--uae-primary-wash); color: var(--uae-primary-ink); }

/* mobile filter bar — mirrors the implementation now live on the job list */
.vd-bottombar {
    display: none;
    position: fixed;
    z-index: 1030;
    left: 0;
    right: 0;
    bottom: 0;
    padding: 10px 16px calc(10px + env(safe-area-inset-bottom));
    border-top: 1px solid var(--uae-line);
    background: rgba(255, 255, 255, .96);
    backdrop-filter: blur(6px);
}
.vd-bottombar__btn {
    display: flex;
    align-items: center;
    justify-content: center;
    gap: 9px;
    width: 100%;
    height: 48px;
    border: 0;
    border-radius: var(--r-control);
    background: var(--uae-ink-surface);
    color: #fff;
    font-size: 15px;
    font-weight: 700;
}
.vd-bottombar__btn strong {
    display: inline-flex;
    align-items: center;
    justify-content: center;
    min-width: 22px;
    height: 22px;
    padding: 0 6px;
    border-radius: var(--r-pill);
    background: var(--uae-ok);
    font-size: 11px;
}
@media (max-width: 991.98px) { .vd-bottombar { display: block; } }

/* ---------- 8. STATES -------------------------------------------------- */

.vd-empty {
    padding: 46px 24px;
    border: 1px dashed var(--uae-line);
    border-radius: var(--r-card);
    background: var(--uae-surface);
    text-align: center;
}
.vd-empty i { margin-bottom: 12px; color: var(--uae-muted); font-size: 26px; }

.vd-skeleton { padding: 18px; border: var(--card-border); border-radius: var(--r-card); background: var(--uae-surface); box-shadow: var(--shadow-card); }
.vd-sk {
    height: 12px;
    border-radius: var(--r-pill);
    background: linear-gradient(90deg, var(--uae-sand) 25%, var(--uae-line) 37%, var(--uae-sand) 63%);
    background-size: 400% 100%;
    animation: vd-shimmer 1.4s ease infinite;
}
.vd-sk + .vd-sk { margin-top: 10px; }
.vd-sk--60 { width: 60%; }
.vd-sk--35 { width: 35%; }
@keyframes vd-shimmer { 0% { background-position: 100% 0; } 100% { background-position: 0 0; } }
@media (prefers-reduced-motion: reduce) { .vd-sk { animation: none; } }

/* ---------- JOB LISTING SKELETON (2026-10-20) --------------------------
   listing-ajax-filters.js toggles `is-loading` on #listing-results-panel
   around every filter and pagination request. Nothing styled that class,
   so a filter change showed stale results and no feedback. These pieces
   reuse the .vd-sk shimmer above; the geometry matches a real card --
   18px padding, 12px radius, a 52px logo column, 16px row gap. */
#listing-results-panel.is-loading { cursor: progress; }
.vd-sk--logo { inline-size: 52px; block-size: 52px; border-radius: var(--r-control); }
.vd-sk-card {
    display: grid;
    grid-template-columns: 52px 1fr;
    gap: 16px;
    /* A real row measured 175px, but every job in the demo seed is
       featured and so carries a flags line; a plain card is nearer 150.
       150 keeps the swap short in both directions rather than matching a
       number that only the demo data produces. */
    min-block-size: 150px;
    padding: 18px;
    border: 1px solid var(--uae-line);
    border-radius: var(--r-card);
    background: var(--uae-surface);
}
/* .vd-sk + .vd-sk already carries margin-top: 10px, so the body stacks on
   that rather than a flex gap, which would double the spacing */
.vd-sk-card__body { align-self: center; }
.vd-sk-toolbar { margin-block-end: 18px; }



/* ==========================================================================
   VacancyDubai POC — page-level components
   Loaded after vd-theme.css. Consumes the same tokens, adds nothing new.
   ========================================================================== */

/* ---------- SITE CHROME ------------------------------------------------- */

/* The POC builds its own header markup in poc-shell.js, under .site-header /
   .site-nav / .site-header__actions. The live site cannot adopt those names:
   includes/header.blade.php is a Bootstrap navbar carrying the two auth
   guards, the offcanvas drawer, the account dropdowns, the language switcher
   and three modals. So the POC's values are applied to the live selectors
   here, and the .site-* rules are gone rather than sitting unused next to
   them, which is what made the header the one surface the migration missed.

   Scoped to #siteheader because the rules these have to beat include
   .navbar-expand-lg .navbar-nav .nav-item.register a (0,4,1) — an id wins
   without needing !important. Scoped to >=992px because the drawer below that
   has its own block in main.css, inside @media screen and (max-width: 990px),
   which has to keep working. */

/* The wordmark, set as type exactly as the POC does it: ink with the accent
   word in primary, over a 9px uppercase tagline. includes/header.blade.php
   builds it from site_name, so there is no image in the front-end header any
   more — the SVG stays for the admin panel and the email template, which are
   not themed by this palette. */
#siteheader .site-logo {
    /* inline-flex, not block: as a block it filled the column, putting a
       351px invisible link across the phone header, under the burger.
       inline-flex shrink-wraps the same way inline-block did. */
    display: inline-flex;
    align-items: center;
    /* The lockup's one input. Mark width is 2.3x it and the gap 0.54x it —
       the ratios from the logo system, written as arithmetic so a breakpoint
       only ever changes this number and the mark follows. Matching the mark's
       HEIGHT to Montserrat's cap height is the obvious rule and is wrong: the
       mark is 1.767:1, so its mass spreads sideways and it reads small well
       before it measures small. */
    --vd-logo-fs: 18px;
    gap: calc(var(--vd-logo-fs) * .54);
    color: var(--uae-ink);
    font-family: Montserrat, system-ui, sans-serif;
    font-size: var(--vd-logo-fs);
    font-weight: var(--weight-heading);
    line-height: 1;
}
/* The monogram. The symbol is fill="currentColor", so `color` here paints it and
   one copy of the path serves both themes.

   --uae-primary-ink, not a literal and not white. The brand kit's reversed
   lockup is a WHITE mark, but that rule is for the mark on a Palm Green field,
   where green on green is impossible — it is not a rule about dark pages. Here
   the wordmark beside it is not white either: "Dubai" is in primary ink, so a
   white mark would untie the mark from the accent word it echoes and sit at
   16.4:1 beside type at 10:1, shouting. The token already lightens at night
   (#4CAE7E), which measures 5.98:1 on the dark surface against 6.61:1 for
   #0B6B3A on white — the same presence in both themes, from one declaration.

   Sized by WIDTH; 0.567 is 567/1000, the mark's own ratio. */
#siteheader .site-logo__glyph {
    flex: none;
    width: calc(var(--vd-logo-fs) * 2.3);
    height: calc(var(--vd-logo-fs) * 2.3 * .567);
    color: var(--uae-primary-ink);
}
/* min-width:0 lets the descriptor wrap inside the column instead of forcing
   the flex row wider; the wordmark itself is nowrap below, so it never breaks. */
#siteheader .site-logo__text { min-width: 0; }
#siteheader .site-logo__mark { white-space: nowrap; }
#siteheader .site-logo:hover { color: var(--uae-ink); text-decoration: none; }
#siteheader .site-logo b { color: var(--uae-primary-ink); font-weight: inherit; }
#siteheader .site-logo small {
    display: block;
    margin-top: 4px;
    color: var(--uae-muted);
    font-family: "Open Sans", system-ui, sans-serif;
    /* 8px, not the 9px this was before the mark joined the lockup. The mark and
       its gap take 51px out of a 201px slot, so at 9px the descriptor (196px)
       could no longer set on one line at any width. */
    font-size: 8px;
    font-weight: var(--weight-strong);
    /* .14em was sized for the old 18-character line; at 34 characters the
       eyebrow became the widest thing in the lockup and wrapped under the
       wordmark from 992 to ~1350px. */
    letter-spacing: .06em;
    line-height: 1.2;
    text-transform: uppercase;
}
/* The descriptor is the widest part of the lockup and col-lg-2 is narrower at
   the tablet step, so the whole thing steps down here — through the custom
   property, which carries the mark down with it rather than leaving a 41px mark
   beside 17px type. The column is 199px at 1200 against 225px at 1440, and the
   nav has only 24px of auto-margin slack at 1200, so none of this can be solved
   by taking space from the nav: the lockup has to get smaller instead.
   The descriptor still sets on two lines below ~1400px, as it did before the
   mark existed, and costs ~3px of header height. A one-line set at every width
   needs a shorter string, not a smaller type size. */
@media (max-width: 1199.98px) and (min-width: 992px) {
    #siteheader .site-logo { --vd-logo-fs: 17px; }
    #siteheader .site-logo small { letter-spacing: .02em; }
}

/* THE MARK IS HIDDEN FROM 992 TO 1399.98 — the wordmark-only lockup, which is
   what this header was before the mark existed.

   Not a preference, a measurement. Between lg and xxl the container is pinned
   at 1140, so col-lg-2 is 169-199px however wide the window gets, and the nav
   is already at its limit inside col-lg-10:

     1024  logo column 169px, nav items within 8.8px of filling their column.
           The mark and its gap add 48px, which put the lockup's right edge
           33px INSIDE the first nav link.
     1200  the lockup cleared that link by 8.4px, against 56px before the mark.
           Moving 30px from the nav column to the logo column to buy that back
           broke every two-word nav label onto a second line and took the
           header from 62px to 82px.

   So nothing in this band can give: the nav cannot be pushed right, the column
   cannot be widened, and sizing the lockup to fit would need --vd-logo-fs:12px.
   Dropping the mark is the one move that costs nothing, because a wordmark-only
   lockup is a sanctioned variant of the logo system and a colliding one is not.

   Below 992 the mark comes back: the phone bar is the logo and a burger, with
   150px of clear space between them. */
@media (max-width: 1399.98px) and (min-width: 992px) {
    #siteheader .site-logo__glyph { display: none; }
    #siteheader .site-logo { gap: 0; }
}

/* At xxl the container jumps 1140 -> 1320 and the nav finally has room: 186px
   of slack. 30px of it goes to the logo column, which is what lets the
   descriptor set on ONE line (175px against the wordmark's 163px) instead of
   wrapping under itself — the lockup as the logo system draws it. The nav
   keeps 156px, so no label wraps. Taken off the nav column in the same breath
   so the row still sums to 100%. */
@media (min-width: 1400px) {
    #siteheader .site-logo-col { flex: 0 0 auto; width: calc(16.666667% + 30px); }
    #siteheader .site-nav-col  { flex: 0 0 auto; width: calc(83.333333% - 30px); }
}

#siteheader { border-bottom: 1px solid var(--uae-line); }
/* was 0 5px 10px rgba(0,0,0,.1) — the sticky header is the only surface on the
   site that still lifted off the page that hard */
#siteheader.issticky { box-shadow: var(--shadow-card); }

@media (min-width: 992px) {
    /* drawer-only furniture: the same <ul> is the desktop nav */
    #siteheader .nav-group,
    #siteheader .nav-foot-start,
    #siteheader .nav-ico,
    #siteheader .mobile-lang-chips { display: none; }
    /* the switcher was a 36px round <img>; a glyph needs the box drawn in CSS */
    #siteheader .mobile-lang .lang-globe {
        display: grid;
        place-items: center;
        inline-size: 36px;
        block-size: 36px;
        border: 1px solid var(--uae-line);
        border-radius: 50%;
        color: var(--uae-muted);
        font-size: 15px;
        line-height: 1;
    }
    #siteheader .mobile-lang > a:hover .lang-globe {
        border-color: var(--uae-primary);
        color: var(--uae-primary-ink);
    }
    #siteheader .navbar-nav { align-items: center; gap: 2px; }
    #siteheader .navbar-nav > li { padding: 0; }

    /* The nav pill from the POC. The legacy treatment was a 2px bottom border
       drawn white on every item and green on the active one, which is a
       different idiom from every other selected state on the site. */
    #siteheader .navbar-nav > li > .nav-link {
        padding: 8px 12px;
        border-bottom: 0;
        border-radius: var(--r-control);
        color: var(--uae-body);
        font-size: 14px;
        font-weight: var(--weight-strong);
    }
    #siteheader .navbar-nav > li > .nav-link:hover { background: var(--uae-sand); color: var(--uae-ink); }
    #siteheader .navbar-nav > li.active > .nav-link { background: var(--uae-primary-wash); color: var(--uae-primary-ink); }

    /* Sign in and Register were two solid buttons in two greens a shade apart
       (--uae-primary-deep beside --uae-primary), both 35px pills at 46px tall
       while every other button on the site is --r-control at 36-44px. One
       primary action and one quiet one, per the POC. */
    #siteheader .navbar-nav > li.loginbtn { margin-inline-start: 8px; }
    #siteheader .navbar-nav > li.loginbtn > .nav-link,
    #siteheader .navbar-nav > li.register > .nav-link,
    #siteheader .navbar-nav > li.logoutbtn > .nav-link {
        display: inline-flex;
        align-items: center;
        justify-content: center;
        gap: 8px;
        height: 36px;
        padding: 0 14px;
        border: 1px solid transparent;
        border-radius: var(--r-control);
        font-size: 14px;
        font-weight: var(--weight-strong);
    }
    #siteheader .navbar-nav > li.loginbtn > .nav-link {
        background: transparent;
        border-color: var(--uae-line);
        color: var(--uae-primary-ink);
    }
    #siteheader .navbar-nav > li.loginbtn > .nav-link:hover {
        background: var(--uae-primary-wash);
        border-color: var(--uae-primary);
        color: var(--uae-primary-ink);
    }
    #siteheader .navbar-nav > li.register > .nav-link { background: var(--uae-primary); color: #fff; }
    #siteheader .navbar-nav > li.register > .nav-link:hover { background: var(--uae-primary-deep); color: #fff; }

    /* the language switcher sits with the buttons, so it gets their height */
    #siteheader .navbar-nav > li.mobile-lang { margin-inline-start: 4px; }
    #siteheader .navbar-nav > li.mobile-lang > a { display: inline-flex; align-items: center; height: 36px; padding: 0 6px; }

    /* ---- the Visa Guides submenu ----------------------------------------
       Deliberately NOT .dropdown-menu: that class carries the account menu's
       legacy styling (right-aligned, 260px, main.css:634) and a bare
       `.navbar-nav > li:hover .dropdown-menu { display: block }` from
       main.css:558. A private class keeps this one under its own parent. */
    #siteheader .navbar-nav > li.has-sub { position: relative; }
    #siteheader .navbar-nav > li.has-sub > .nav-link { display: inline-flex; align-items: center; gap: 6px; }
    #siteheader .nav-caret { font-size: 9px; opacity: .5; }
    #siteheader .navbar-nav > li.has-sub:hover > .nav-link,
    #siteheader .navbar-nav > li.has-sub:focus-within > .nav-link { background: var(--uae-sand); color: var(--uae-ink); }
    /* The distance from a nav item's bottom to the header's bottom edge:
       .navbar carries `padding: 10px 0` from main.css:513, a legacy global
       shared with every other navbar, so it is read here rather than
       changed. The header's own 1px bottom border sits below it. */
    #siteheader { --vd-nav-gap: 10px; }
    #siteheader .nav-submenu {
        display: none;
        position: absolute;
        /* flush to the header's edge, not the item's: at 100% the panel
           started 11px high and floated over the header's hairline */
        inset-block-start: calc(100% + var(--vd-nav-gap));
        inset-inline-start: 0;
        z-index: 1200;
        min-inline-size: 248px;
        margin: 0;
        /* no inline padding: square items run the full width of the panel */
        padding: 6px 0;
        border: 1px solid var(--uae-line);
        /* the header's bottom border is the seam; a second one doubles it */
        border-block-start: 0;
        border-radius: 0;
        background: var(--uae-surface);
        box-shadow: var(--shadow-pop);
        list-style: none;
    }
    /* Bridges the gap the panel was moved down by, so the pointer can
       travel from the item to the panel without leaving the <li> and
       closing it. A child of the panel, so it exists only while the menu
       is open -- an always-present strip under each item would open a
       menu whenever the pointer crossed the header. */
    #siteheader .nav-submenu::before {
        content: '';
        position: absolute;
        inset-block-end: 100%;
        inset-inline: 0;
        block-size: var(--vd-nav-gap);
    }
    /* :focus-within as well as :hover — every other dropdown in this header
       opens on hover alone, which no keyboard can reach */
    #siteheader .navbar-nav > li.has-sub:hover > .nav-submenu,
    #siteheader .navbar-nav > li.has-sub:focus-within > .nav-submenu { display: block; }
    #siteheader .nav-submenu > li > a {
        display: block;
        /* 14px of its own, since the panel no longer insets by 6px --
           text lands 14px in against 16px before, and the hover band
           now runs edge to edge instead of being a rounded pill */
        padding: 8px 14px;
        border-radius: 0;
        color: var(--uae-body);
        font-size: 13.5px;
        line-height: 1.4;
        white-space: nowrap;
    }
    #siteheader .nav-submenu > li > a:hover,
    #siteheader .nav-submenu > li > a:focus-visible {
        background: var(--uae-primary-wash);
        color: var(--uae-primary-ink);
        text-decoration: none;
    }
    #siteheader .nav-submenu__sep { block-size: 1px; margin: 5px 0; background: var(--uae-line); }
}

/* The narrow end of the desktop range. col-lg-10 is 820px at 992px wide and the
   nav wants 863px, so Walk-in Interviews, Visa Guides, Work in UAE and Contact
   Us each broke to a second line and the header went 59px -> 82px. Tightening
   padding and gap recovers 68px, which is enough; the type size is left alone so
   the band is the same nav rather than a smaller one.

   This block has to come AFTER @media (min-width: 992px) above — the selectors
   tie on specificity, so source order is what makes it win. */
@media (min-width: 992px) and (max-width: 1199.98px) {
    /* The actual mechanism, found by measuring the <a> rather than the <li>:
       the <ul> is a flex row, so the longest items were being SHRUNK below
       their content width and their labels wrapped to a second line. Padding
       alone did not fix it — the items fit in 820px and still wrapped. A nav
       link has no business wrapping at any desktop width. */
    #siteheader .navbar-nav > li { flex: none; }
    #siteheader .navbar-nav > li > .nav-link { white-space: nowrap; }
    #siteheader .navbar-nav { gap: 1px; }
    /* 7px, not 8: with the Visa Guides submenu added the <ul> sat 6px from the
       column edge. It cannot wrap (nowrap + flex: none above), so it would
       overflow rather than break, and 6px is too thin to leave a locale or a
       font fallback to chance. 7px returns 12px across the six nav items. */
    #siteheader .navbar-nav > li > .nav-link { padding-inline: 7px; }
    #siteheader .navbar-nav > li.loginbtn > .nav-link,
    #siteheader .navbar-nav > li.register > .nav-link,
    #siteheader .navbar-nav > li.logoutbtn > .nav-link { padding-inline: 11px; }
    #siteheader .navbar-nav > li.loginbtn { margin-inline-start: 4px; }
    /* the caret is ~15px with its gap and this band had 19px spare; the
       submenu still opens on hover and focus without it */
    #siteheader .nav-caret { display: none; }
    #siteheader .navbar-nav > li.has-sub > .nav-link { gap: 0; }
}

/* The drawer is the header on phones, and it carried the same defects plus a
   set of slate/blue values from before the palette existed: the selected item
   washed #f3f7ff (blue), links #1f2937, the account row #f8fafc, and 12px
   radii. Its own rules live in main.css inside @media (max-width: 990px), so
   these match that breakpoint and beat it on load order at equal specificity. */
@media (max-width: 991.98px) {
    /* main.css reserves padding-right: 100px on .header .logo below 990px, to
       keep the old image clear of the floated burger. On a text lockup that
       padding is just 100px of invisible link reaching under the burger, so
       drop it and reserve the space as a max-width instead. */
    #siteheader .site-logo { padding-right: 0; max-width: none; min-width: 0; }

    /* The burger was "position: absolute; top: 15px; right: 15px" with nothing
       positioned above it, so it anchored to the PAGE, not the header: 15px from
       the viewport edge against the container's 12px gutter, and 15 + 46 = 61px
       against a 56px header, so it hung 5px below the header's own border. It
       was also a 54x46 #eee box on a 5px radius — the last legacy grey chip left
       in the site chrome.

       The header column is a flex row below lg now, so the button sits in flow:
       centred on the lockup, at the logo's gutter, and square. main.css styles
       it inside @media (max-width: 990px) and floats .navbar-header right, so
       both are undone here; #siteheader out-specifies them without !important. */
    #siteheader .row > div:first-child {
        display: flex;
        align-items: center;
    }
    /* main.css zeroes the navbar padding only below 990px, so at 991-991.98 the
       second column kept Bootstrap default 8px/8px and added 20px of empty
       height under the logo row. Same 990-vs-991.98 seam as the burger above. */
    #siteheader .navbar { padding: 0; }
    #siteheader .navbar-header {
        /* main.css reveals the burger only below 990px while the drawer runs to
           991.98px, so at 991-991.98 there was a drawer and no way to open it
           from the header. The bar covers that band now, but the decision was to
           keep the burger at every width below lg, so it is shown here too. */
        display: block;
        flex: none;
        float: none;
        margin: 0;
        margin-inline-start: auto;
    }
    #siteheader .navbar-toggler {
        position: static;
        display: grid;
        place-items: center;
        width: 42px;
        height: 42px;
        padding: 0;
        border: 1px solid var(--uae-line);
        border-radius: var(--r-control);
        background: var(--uae-surface);
        color: var(--uae-ink);
        font-size: 17px;
        line-height: 1;
    }
    #siteheader .navbar-toggler:hover,
    #siteheader .navbar-toggler[aria-expanded="true"] {
        background: var(--uae-sand);
        color: var(--uae-ink);
    }
    #siteheader .navbar-toggler:focus-visible {
        outline: 2px solid var(--uae-primary);
        outline-offset: 2px;
    }
    /* the empty .clearfix after the button is a third flex item at zero width;
       it only matters if someone later adds justify-content here */
    #siteheader .row > div:first-child > .clearfix { display: none; }

    #nav-main .navbar-nav > li > .nav-link { border-radius: var(--r-control); color: var(--uae-body); }
    #nav-main .navbar-nav > li.active > .nav-link,
    #nav-main .navbar-nav > li > .nav-link:hover {
        background: var(--uae-primary-wash);
        color: var(--uae-primary-ink);
    }
    #nav-main .navbar-nav > li.loginbtn > .nav-link,
    #nav-main .navbar-nav > li.register > .nav-link,
    #nav-main .navbar-nav > li.logoutbtn > .nav-link {
        border: 1px solid transparent;
        border-radius: var(--r-control) !important;
        font-size: 15px;
    }
    /* one primary action, as on desktop — these were two solid greens a shade
       apart, stacked, which read as one control split in half */
    #nav-main .navbar-nav > li.loginbtn > .nav-link {
        background: var(--uae-surface);
        border-color: var(--uae-line);
        color: var(--uae-primary-ink);
    }
    #nav-main .navbar-nav > li.register > .nav-link { background: var(--uae-primary); color: #fff; }
    #nav-main .navbar-nav > li.userbtn > a,
    #nav-main .mobile-account-toggle {
        border-radius: var(--r-card);
        border-color: var(--uae-line);
        background: var(--uae-sand);
    }
    #nav-main .mobile-account-meta strong { color: var(--uae-ink); }
    #nav-main .mobile-account-meta small { color: var(--uae-muted); }

    /* ---- OPTION A (2026-10-14): the drawer, furnished ------------------
       The panel, the slide and the backdrop already existed. What it lacked
       was a reason to open it: five lines of plain text, with the two busiest
       destinations weighted exactly like "Contact Us". It now opens on a
       search row, every item carries an icon, and the items are grouped under
       three labels. Both the icons and the labels are markup, suppressed from
       992px up, because ONE <ul> is both the desktop nav and this drawer. */

    /* the drawer title was #111827, a slate from before the palette existed */
    .mobile-drawer-head { border-block-end-color: var(--uae-line); }
    .mobile-drawer-title { color: var(--uae-ink); font-family: Montserrat, system-ui, sans-serif; font-size: 16px; }

    #nav-main .navbar-nav > li.nav-group {
        padding: 14px 14px 5px;
        color: var(--uae-muted);
        font-size: 10px;
        font-weight: var(--weight-strong);
        letter-spacing: .12em;
        line-height: 1.2;
        text-transform: uppercase;
    }
    /* the first label is the first thing in the panel now that the search row
       is gone, so it keeps the list's own top padding rather than halving it */
    #nav-main .navbar-nav > li.nav-group:first-child { padding-block-start: 4px; }

    /* the drawer keeps the flat link under GUIDES — the hub page lists all of
       this, and the grouped list was decided to stay one level deep */
    #nav-main .nav-submenu,
    #nav-main .nav-caret { display: none; }
    #nav-main .navbar-nav > li > .nav-link { gap: 12px; padding: 11px 14px; font-size: 15px; }
    #nav-main .nav-ico {
        flex: none;
        inline-size: 18px;
        color: var(--uae-muted);
        font-size: 14px;
        text-align: center;
    }
    #nav-main .navbar-nav > li.active > .nav-link .nav-ico,
    #nav-main .navbar-nav > li > .nav-link:hover .nav-ico { color: var(--uae-primary-ink); }

    /* the account block and the language switcher sit at the foot. The <ul> is
       already flex: 1 1 auto inside a flex-column #nav-main, so one auto margin
       on an empty item pushes everything after it down. */
    #nav-main .navbar-nav > li.nav-foot-start {
        margin-block-start: auto;
        padding-block-start: 10px;
    }
    /* compact, because the foot is furniture rather than content: these were
       two 48px bars plus a 56px language row, which is 152px of a 760px panel */
    #nav-main .navbar-nav > li.loginbtn,
    #nav-main .navbar-nav > li.register,
    #nav-main .navbar-nav > li.logoutbtn { margin-block-start: 6px; }
    #nav-main .navbar-nav > li.loginbtn a,
    #nav-main .navbar-nav > li.register a,
    #nav-main .navbar-nav > li.logoutbtn a {
        padding: 9px 14px !important;
        font-size: 14px;
    }
    #nav-main .navbar-nav > li.mobile-lang > a { padding-block: 9px; }

    /* The drawer switcher: chips, not the 71px avatar row. The row and its
       dropdown stay in the DOM because the forms live inside the dropdown and
       the desktop switcher needs both. */
    #nav-main .navbar-nav > li.mobile-lang { margin-block-start: 8px; padding-inline: 4px; }
    #nav-main .navbar-nav > li.mobile-lang > a.mobile-account-toggle,
    #nav-main .navbar-nav > li.mobile-lang > .dropdown-menu { display: none; }
    #nav-main .mobile-lang-globe {
        align-self: center;
        margin-inline: 8px 3px;
        color: var(--uae-muted);
        font-size: 13px;
    }
    #nav-main .mobile-lang-chips {
        display: inline-flex;
        flex-wrap: wrap;
        align-items: center;
        gap: 3px;
        padding: 3px;
        border-radius: var(--r-control);
        background: var(--uae-sand);
    }
    #nav-main .mobile-lang-chip {
        /* 9px gives a ~36px chip. 5px measured 28px, which clears WCAG 2.5.8
           (24px) but is mean for a control people hit with a thumb. The whole
           row is still ~42px against the 71px avatar block it replaced. */
        padding: 9px 14px;
        border: 0;
        border-radius: 4px;
        background: transparent;
        color: var(--uae-muted);
        font: inherit;
        font-size: 12.5px;
        line-height: 1.4;
        cursor: pointer;
    }
    #nav-main .mobile-lang-chip.is-on {
        background: var(--uae-surface);
        color: var(--uae-ink);
        font-weight: var(--weight-strong);
        box-shadow: var(--shadow-card);
    }
    #nav-main .mobile-lang-chip:focus-visible {
        outline: 2px solid var(--uae-primary);
        outline-offset: 1px;
    }

    /* ---- THE BOTTOM BAR (rebuilt 2026-10-14) ---------------------------
       Four items, the last of which opens the drawer above rather than
       repeating it. What it replaces held Home, Jobs and Login: two repeated
       the drawer, the third opened a modal, and no item ever carried an active
       state — which is the only thing a tab bar is for.

       --vd-bar-h is the contract between the bar and the cookie banner: both
       are position: fixed, so the banner cannot simply be docked above the bar
       the way the prototype does it, and it offsets by this instead. Change the
       height here and the banner follows. */
    .mobilenav {
        --vd-bar-h: 58px;
        display: block;
        position: fixed;
        inset-block-end: 0;
        inset-inline: 0;
        z-index: 999;
        block-size: var(--vd-bar-h);
        padding-block: 6px 4px;
        padding-inline: 6px;
        background: var(--uae-surface);
        border-block-start: 1px solid var(--uae-line);
        box-shadow: 0 -2px 10px rgba(19, 26, 36, .06);
    }
    .mobilenav ul {
        display: grid;
        grid-auto-flow: column;
        grid-auto-columns: 1fr;
        gap: 2px;
        margin: 0;
        padding: 0;
        list-style: none;
        block-size: 100%;
    }
    .mobilenav ul li { margin: 0; padding: 0; }
    .mobilenav ul li > a,
    .mobilenav__menu {
        display: grid;
        justify-items: center;
        align-content: center;
        gap: 3px;
        inline-size: 100%;
        block-size: 100%;
        padding: 0 2px;
        border: 0;
        border-radius: var(--r-control);
        background: transparent;
        color: var(--uae-muted);
        font-family: inherit;
        font-size: 10.5px;
        font-weight: 500;
        letter-spacing: .01em;
        line-height: 1.2;
        text-align: center;
        text-decoration: none;
        cursor: pointer;
    }
    .mobilenav ul li > a i,
    .mobilenav__menu i { font-size: 21px; line-height: 1; }
    /* Sprite icons replaced the Font Awesome glyphs here (see
       includes/icon_sprite.blade.php). An SVG takes no size from
       font-size, so it needs explicit dimensions or it collapses to 0.
       21px matches the optical weight the solid glyphs had. */
    .mobilenav ul li > a .vd-ico,
    .mobilenav__menu .vd-ico { width: 21px; height: 21px; }
    /* The prototype marks the current tab by WEIGHT as well as colour,
       which survives being looked at in a hurry better than hue alone. */
    .mobilenav ul li > a.is-on .vd-ico { stroke-width: 2.2; }
    .mobilenav ul li > a:hover,
    .mobilenav__menu:hover { background: var(--uae-sand); color: var(--uae-body); }
    /* the active state the old bar never had */
    .mobilenav ul li > a.is-on,
    .mobilenav ul li > a.is-on i { color: var(--uae-primary-ink); }
    .mobilenav ul li > a:focus-visible,
    .mobilenav__menu:focus-visible { outline: 2px solid var(--uae-primary); outline-offset: -2px; }

    /* the footer clears the bar; this moved from main.css's 767px block */
    .copyright { padding-block-end: calc(58px + 20px); }

    /* The banner used to sit on top of the bar on a first visit — z-index 99999
       against the bar's 999, both anchored to bottom: 0.

       Targeted by ID, not by .cookie-consent-banner: that class is styled in an
       inline <style> inside includes/cookie_consent.blade.php, which comes after
       the head stylesheets in document order and therefore wins at equal
       specificity. The same trap CLAUDE.md records for the admin tables. */
    #cookieConsentBanner { inset-block-end: 58px; }
}

/* The POC's .site-footer rules lived here and had no callers either: the live
   footer is includes/footer.blade.php on .footerWrap + .copyright, with a
   four-column Bootstrap grid, the app banner and the social row. It is
   tokenised in place in main.css (it was #31363e with 50%-white links at
   4.33:1, now --uae-ink at 5.19:1), so there is nothing left for a second,
   unused footer style to do. */

/* ---------- PAGE FURNITURE --------------------------------------------- */

.vd-breadcrumb { display: flex; flex-wrap: wrap; gap: 8px; padding: 14px 0; color: var(--uae-muted); font-size: 13px; }
.vd-breadcrumb a { color: var(--uae-muted); }
.vd-breadcrumb i { opacity: .45; font-size: 9px; align-self: center; }
/* The separator is a fa-chevron-right in the markup, which an icon font will
   not flip from `dir` alone, so in Arabic the trail read right-to-left with
   arrows pointing left-to-right. `.taxonomy-breadcrumb i` was already mirrored
   in main.css; this class — job detail, job/company directories — was missed.
   Added 2026-10-15. */
html[dir="rtl"] .vd-breadcrumb i { transform: scaleX(-1); }

.vd-pagetitle { padding: 24px 0; border-bottom: 1px solid var(--uae-line); background: var(--uae-surface); }

.section-head { display: flex; align-items: flex-end; justify-content: space-between; gap: 20px; margin-bottom: 20px; }
.section-head p { margin: 6px 0 0; color: var(--uae-muted); font-size: 14px; }

.vd-pagination { display: flex; justify-content: center; gap: 6px; margin-top: 26px; }
.vd-pagination a, .vd-pagination span {
    display: grid;
    place-items: center;
    min-width: 38px;
    height: 38px;
    padding: 0 10px;
    border: 1px solid var(--uae-line);
    border-radius: var(--r-control);
    background: var(--uae-surface);
    color: var(--uae-body);
    font-size: 14px;
}
.vd-pagination a:hover { border-color: var(--uae-primary); text-decoration: none; }
.vd-pagination .is-current { border-color: var(--uae-primary); background: var(--uae-primary); color: #fff; font-weight: 700; }

.vd-tabs { display: flex; flex-wrap: wrap; gap: 4px; border-bottom: 1px solid var(--uae-line); margin-bottom: 20px; }
.vd-tabs button {
    padding: 11px 15px;
    border: 0;
    border-bottom: 2px solid transparent;
    background: transparent;
    color: var(--uae-muted);
    font-size: 14px;
    font-weight: var(--weight-strong);
    cursor: pointer;
}
.vd-tabs button.is-active { border-bottom-color: var(--uae-primary); color: var(--uae-primary-ink); }

.vd-card {
    padding: 20px;
    border: var(--card-border);
    border-radius: var(--r-card);
    background: var(--uae-surface);
    box-shadow: var(--shadow-card);
}
.vd-card__head { display: flex; align-items: center; justify-content: space-between; gap: 14px; margin-bottom: 14px; padding-bottom: 14px; border-bottom: 1px solid var(--uae-line); }
.vd-card__head h3 { font-size: 16px; }

.vd-alert {
    display: flex;
    gap: 12px;
    padding: 14px 16px;
    border: 1px solid var(--uae-line);
    border-left: 3px solid var(--uae-primary);
    border-radius: var(--r-control);
    background: var(--uae-primary-wash);
    color: var(--uae-body);
    font-size: 14px;
}
html[dir="rtl"] .vd-alert { border-left-width: 1px; border-right: 3px solid var(--uae-primary); }
.vd-alert--warn { border-left-color: var(--uae-gold); background: var(--uae-gold-wash); }

/* ---------- CONTENT CARDS ---------------------------------------------- */

/*
   2026-10-26: matched to the .vd-bcc trade card, because the homepage runs
   "Jobs by trade" straight into "Popular job markets" and the two grids were
   measurably different: 230px/14px gap laid 12 cards out 5 to a row -- 5, 5, 2,
   a ragged last row -- against the trade grid's neat 6 and 6 at 190px/12px.
   The card itself was 18px padding against 16, and its h3 carried weight 700
   plus a 10px bottom margin that the trade card's 600-weight name does not,
   so it sat taller with dead space under the label.

   Both .tile users change together, which is the point: .tile-grid is this
   section and the industries section directly below it. Restyling only the
   hubs would have fixed one mismatch by creating another two sections down.

   Two differences remain and are in the DATA, not the CSS: a trade card has a
   family line under the name and a per-family icon tint, and a hub has neither
   a family nor anything true to put on a second line. So a trade card stays
   about one line taller and its icons stay more colourful. */
.tile-grid { display: grid; grid-template-columns: repeat(auto-fill, minmax(190px, 1fr)); gap: 12px; }

.tile {
    display: block;
    padding: 16px;
    border: var(--card-border);
    border-radius: var(--r-card);
    background: var(--uae-surface);
    box-shadow: var(--shadow-card);
    color: var(--uae-ink);
}
.tile:hover { border-color: var(--uae-primary); text-decoration: none; }
.tile__ico {
    display: grid;
    place-items: center;
    width: 42px;
    height: 42px;
    margin-bottom: 11px;
    border-radius: var(--r-control);
    background: var(--uae-primary-wash);
    color: var(--uae-primary-ink);
    font-size: 16px;
}
/* margin: 0 because the theme gives h3 a bottom margin and the trade card's
   name has none; weight and line-height match .vd-bcc__name exactly. */
.tile h3 { margin: 0; font-size: 15px; font-weight: 600; line-height: 1.3; }
/* The trade card's family line is 3px/12.5px; this is the same line in the
   same position, so it takes the same values. */
.tile p { margin: 3px 0 0; color: var(--uae-muted); font-size: 12.5px; }

.employer-card { display: flex; gap: 14px; align-items: flex-start; padding: 18px; border: var(--card-border); border-radius: var(--r-card); background: var(--uae-surface); box-shadow: var(--shadow-card); }
.employer-card__logo {
    display: grid;
    place-items: center;
    width: 56px;
    height: 56px;
    flex: 0 0 56px;
    border: 1px solid var(--uae-line);
    border-radius: var(--r-control);
    background: var(--uae-sand);
    color: var(--uae-primary-ink);
    font: 700 16px/1 Montserrat, sans-serif;
}

.trust-strip { display: flex; flex-wrap: wrap; gap: 30px; padding: 18px 22px; border: var(--card-border); border-radius: var(--r-card); background: var(--uae-surface); box-shadow: var(--shadow-card); }
.trust-strip > div { display: flex; align-items: center; gap: 11px; font-size: 14px; color: var(--uae-muted); }
.trust-strip b { display: block; color: var(--uae-ink); font: 700 19px/1.2 Montserrat, sans-serif; }
.trust-strip i { color: var(--uae-primary-ink); font-size: 17px; }

.blog-card { border: var(--card-border); border-radius: var(--r-card); background: var(--uae-surface); box-shadow: var(--shadow-card); overflow: hidden; }
.blog-card__thumb { height: 126px; background: var(--uae-primary-wash); display: grid; place-items: center; color: var(--uae-primary-ink); font-size: 22px; }
.blog-card__body { padding: 16px; }
.blog-card h3 { font-size: 15px; margin-bottom: 6px; }

/* ---------- JOB DETAIL ------------------------------------------------- */

.jd-head { display: flex; gap: 18px; align-items: flex-start; }
.jd-meta-grid { display: grid; grid-template-columns: repeat(auto-fill, minmax(175px, 1fr)); gap: 1px; border: 1px solid var(--uae-line); border-radius: var(--r-card); overflow: hidden; background: var(--uae-line); margin: 0; }
.jd-meta-grid > div { padding: 14px 16px; background: var(--uae-surface); }
.jd-meta-grid dt { color: var(--uae-muted); font-size: 11px; font-weight: 700; letter-spacing: .06em; text-transform: uppercase; }
.jd-meta-grid dd { margin: 4px 0 0; color: var(--uae-ink); font-size: 15px; font-weight: var(--weight-strong); }

.jd-prose { color: var(--uae-body); font-size: 15px; }
.jd-prose h3 { margin: 24px 0 10px; font-size: 17px; }
.jd-prose ul { margin: 0 0 12px; padding-left: 20px; }
html[dir="rtl"] .jd-prose ul { padding-left: 0; padding-right: 20px; }
.jd-prose li { margin-bottom: 6px; }

/* The apply box sticks, not the whole sidebar. Sticking the sidebar looks right
   but does nothing: it is the only child of its column, so at 892px inside a
   950px column it has 58px of travel and is itself taller than the viewport
   below the header (808px), meaning the CTA scrolls away regardless. The box
   alone is 209px, so it fits and gets ~740px of travel — it stays with the
   reader through the description, which is the point.
   92px = the 72px .header.issticky (fixed from ~200px of scroll) plus a gap. */
.jd-apply { position: static; }
.jd-apply__box { position: sticky; top: 92px; padding: 20px; border: var(--card-border); border-radius: var(--r-card); background: var(--uae-surface); box-shadow: var(--shadow-card); }
.jd-apply__box .vd-btn { width: 100%; }
.jd-applybar { display: none; }
@media (max-width: 991.98px) {
    /* the fixed bar carries the CTA on phones, so nothing needs to stick */
    .jd-apply__box { position: static; }
    .jd-applybar {
        display: grid;
        grid-template-columns: 1fr auto;
        gap: 12px;
        align-items: center;
        position: fixed;
        z-index: 1030;
        left: 0;
        right: 0;
        bottom: 0;
        padding: 10px 16px calc(10px + env(safe-area-inset-bottom));
        border-top: 1px solid var(--uae-line);
        background: rgba(255, 255, 255, .97);
    }
}

/* ---------- DASHBOARD SHELL -------------------------------------------- */

.dash { display: grid; grid-template-columns: 252px 1fr; gap: 24px; align-items: start; }
.dash-rail { position: sticky; top: 92px; padding: 18px; border: var(--card-border); border-radius: var(--r-card); background: var(--uae-surface); box-shadow: var(--shadow-card); }
.dash-rail__user { display: flex; gap: 12px; align-items: center; padding-bottom: 16px; margin-bottom: 12px; border-bottom: 1px solid var(--uae-line); }
.dash-rail__menu { margin: 0; padding: 0; list-style: none; }
.dash-rail__menu a {
    display: flex;
    align-items: center;
    gap: 10px;
    padding: 10px 12px;
    border-radius: var(--r-control);
    color: var(--uae-body);
    font-size: 14px;
    font-weight: var(--weight-strong);
}
.dash-rail__menu a:hover { background: var(--uae-sand); text-decoration: none; }
.dash-rail__menu a.is-active { background: var(--uae-primary-wash); color: var(--uae-primary-ink); }
.dash-rail__menu i { width: 16px; opacity: .7; text-align: center; }
.dash-rail__menu em {
    margin-left: auto;
    padding: 1px 7px;
    border-radius: var(--r-pill);
    background: var(--uae-primary);
    color: #fff;
    font-size: 11px;
    font-style: normal;
    font-weight: 700;
}
html[dir="rtl"] .dash-rail__menu em { margin-left: 0; margin-right: auto; }

.avatar {
    display: grid;
    place-items: center;
    width: 44px;
    height: 44px;
    flex: 0 0 44px;
    border-radius: 50%;
    background: var(--uae-primary-wash);
    color: var(--uae-primary-ink);
    font: 700 15px/1 Montserrat, sans-serif;
}
.avatar--sm { width: 34px; height: 34px; flex-basis: 34px; font-size: 12px; }

.stat-tiles { display: grid; grid-template-columns: repeat(auto-fit, minmax(168px, 1fr)); gap: 14px; }
.stat-tile { display: flex; gap: 13px; align-items: center; padding: 16px; border: var(--card-border); border-radius: var(--r-card); background: var(--uae-surface); box-shadow: var(--shadow-card); }
.stat-tile__ico { display: grid; place-items: center; width: 40px; height: 40px; flex: 0 0 40px; border-radius: var(--r-control); font-size: 15px; }
.stat-tile b { display: block; color: var(--uae-ink); font: 700 22px/1.1 Montserrat, sans-serif; }
.stat-tile span { color: var(--uae-muted); font-size: 13px; }
.stat-tile--ok .stat-tile__ico { background: var(--uae-primary-wash); color: var(--uae-primary-ink); }
.stat-tile--gold .stat-tile__ico { background: var(--uae-gold-wash); color: var(--uae-gold-text); }
.stat-tile--ink .stat-tile__ico { background: var(--uae-sand); color: var(--uae-ink); }
.stat-tile--line .stat-tile__ico { background: var(--uae-surface); border: 1px solid var(--uae-line); color: var(--uae-muted); }

.ring { display: grid; place-items: center; width: 92px; height: 92px; margin: 0 auto 12px; border-radius: 50%; background: var(--uae-primary-wash); color: var(--uae-primary-ink); font: 700 20px/1 Montserrat, sans-serif; }

@media (max-width: 991.98px) {
    .dash { grid-template-columns: 1fr; }
    .dash-rail { position: static; }
}

/* ---------- TABLES + FORMS --------------------------------------------- */

.vd-table--data th { background: var(--uae-sand); }
.vd-table--data td { color: var(--uae-body); font-size: 14px; vertical-align: middle; }
.vd-table--data tbody tr:hover td { background: var(--uae-sand); }

.field { margin-bottom: 16px; }
.field > label { display: block; margin-bottom: 6px; color: var(--uae-ink); font-size: 13px; font-weight: var(--weight-strong); }
.field small { display: block; margin-top: 5px; color: var(--uae-muted); font-size: 12px; }
.field-row { display: grid; grid-template-columns: 1fr 1fr; gap: 16px; }
select.vd-input, textarea.vd-input { height: auto; padding: 11px 14px; }
textarea.vd-input { min-height: 118px; }
.field--error .vd-input { border-color: var(--uae-danger); }
.field--error small { color: var(--uae-danger); }
.form-steps { display: flex; flex-wrap: wrap; gap: 14px; margin-bottom: 22px; }
.form-steps > div { display: flex; align-items: center; gap: 8px; color: var(--uae-muted); font-size: 13px; }
.form-steps i { display: grid; place-items: center; width: 24px; height: 24px; border: 1px solid var(--uae-line); border-radius: 50%; font-size: 11px; font-style: normal; }
.form-steps .is-on { color: var(--uae-primary-ink); font-weight: 700; }
.form-steps .is-on i { border-color: var(--uae-primary); background: var(--uae-primary); color: #fff; }
@media (max-width: 767.98px) { .field-row { grid-template-columns: 1fr; } }

/* ---------- PRICING + AUTH --------------------------------------------- */

.price-grid { display: grid; grid-template-columns: repeat(auto-fit, minmax(250px, 1fr)); gap: 16px; }
.price-card { display: flex; flex-direction: column; padding: 24px; border: var(--card-border); border-radius: var(--r-card); background: var(--uae-surface); box-shadow: var(--shadow-card); }
.price-card--featured { border: 1px solid var(--uae-primary); }
.price-card__amount { margin: 10px 0 4px; color: var(--uae-ink); font: 700 33px/1 Montserrat, sans-serif; }
.price-card__amount small { color: var(--uae-muted); font-size: 13px; font-weight: 400; }
.price-card ul { margin: 18px 0; padding: 0; list-style: none; }
.price-card li { display: flex; gap: 9px; margin-bottom: 9px; color: var(--uae-body); font-size: 14px; }
.price-card li i { color: var(--uae-primary-ink); font-size: 12px; margin-top: 4px; }
.price-card .vd-btn { margin-top: auto; }

.auth-split { display: grid; grid-template-columns: 1fr 1fr; border: var(--card-border); border-radius: var(--r-card); background: var(--uae-surface); box-shadow: var(--shadow-card); overflow: hidden; }
.auth-split__aside { padding: 40px; background: var(--uae-ink-surface); color: #fff; }
.auth-split__aside h1, .auth-split__aside h2 { color: #fff; }
.auth-split__aside ul { margin: 22px 0 0; padding: 0; list-style: none; }
.auth-split__aside li { display: flex; gap: 10px; margin-bottom: 12px; color: rgba(255, 255, 255, .88); font-size: 14px; }
.auth-split__form { padding: 40px; }
.auth-choice { display: grid; grid-template-columns: 1fr 1fr; gap: 10px; margin-bottom: 22px; }
.auth-choice button { padding: 14px; border: 1px solid var(--uae-line); border-radius: var(--r-control); background: var(--uae-surface); color: var(--uae-body); font-size: 14px; font-weight: var(--weight-strong); cursor: pointer; }
.auth-choice button.is-on { border-color: var(--uae-primary); background: var(--uae-primary-wash); color: var(--uae-primary-ink); }
@media (max-width: 991.98px) {
    .auth-split { grid-template-columns: 1fr; }
    .auth-split__aside { display: none; }
    .auth-split__form { padding: 26px; }
}


.vd-filter__actions { display: none; }

@media (max-width: 991.98px) {
    .offcanvas-lg > .vd-filter {
        height: 100%;
        margin: 0;
        padding: 20px;
        border: 0;
        border-radius: 0;
        box-shadow: none;
        overflow-y: auto;
        -webkit-overflow-scrolling: touch;
    }
    .vd-filter__actions {
        display: grid;
        grid-template-columns: 1fr 2fr;
        gap: 10px;
        position: sticky;
        bottom: 0;
        z-index: 2;
        margin: 20px -20px 0;
        padding: 12px 20px calc(12px + env(safe-area-inset-bottom));
        border-top: 1px solid var(--uae-line);
        background: var(--uae-surface);
    }
    .vd-filter__actions .btn {
        height: 48px;
        border: 1px solid var(--uae-line);
        border-radius: var(--r-control);
        background: var(--uae-surface);
        color: var(--uae-primary-ink);
        font-weight: 700;
    }
    .vd-filter__actions .btn:last-child { border-color: var(--uae-primary); background: var(--uae-primary); color: #fff; }
}

/* ---------- LISTING PAGE GLUE (Phase 3) --------------------------------
   Small helpers the live listing needs that the POC expressed with
   Bootstrap utility classes inline.
   ---------------------------------------------------------------------- */

ul.vd-results { margin: 0; padding: 0; list-style: none; }
ul.vd-results > li { list-style: none; margin-bottom: 16px; }

.job-card__flags { display: flex; flex-wrap: wrap; gap: 6px; margin-bottom: 8px; }
.job-card__actions { display: flex; gap: 8px; }
.job-card__actions .vd-btn { white-space: nowrap; }

/* the row card puts the logo in a fixed first column */
.job-row > .job-card__logo { align-self: flex-start; }

@media (max-width: 767.98px) {
    .job-card__actions { width: 100%; }
    .job-card__actions .vd-btn:last-child { flex: 1 1 auto; }
}

/* toolbar stacks below 576px: label + full-width select */
@media (max-width: 575.98px) {
    .vd-toolbar { display: block; }
    .vd-toolbar h2 { font-size: 22px; }
    .vd-sort { display: block; margin-top: 12px; }
    .vd-sort__label { margin-bottom: 5px; }
    .vd-sort select { width: 100%; min-width: 0; }
}

/* ---------- STACKED CARD VARIANT (homepage showcase) -------------------
   Same partial as the search results; .job-card without .job-row lays the
   logo beside the content and drops the salary/actions row to the bottom.
   ---------------------------------------------------------------------- */

.vd-results--grid > li { margin-bottom: 20px; }

.job-card:not(.job-row) {
    display: grid;
    grid-template-columns: 52px minmax(0, 1fr);
    gap: 8px 14px;
    align-items: start;
    height: 100%;
}
.job-card:not(.job-row) > .job-row__cta {
    grid-column: 1 / -1;
    flex-direction: row;
    align-items: center;
    justify-content: space-between;
    gap: 12px;
    margin-top: auto;
    padding-top: 14px;
    border-top: 1px solid var(--uae-line);
}
.job-card:not(.job-row) .job-card__salary { font-size: 15px; }

@media (max-width: 575.98px) {
    .job-card:not(.job-row) > .job-row__cta { display: grid; }
    .job-card:not(.job-row) .job-card__actions { width: 100%; }
}

/* ==========================================================================
   HOMEPAGE (Phase 3b)
   ========================================================================== */

/* Hero: centred copy over a flat ink fill */
.vd-hero { padding: 66px 0 58px; background: var(--uae-ink-surface); color: #fff; }
/* --vd-hero-h1 is the heading scale, declared once so the h1 and the accent
   line beneath it cannot drift apart -- and so a second hero can adopt the
   whole block by taking this class. The Emirate browse pages do exactly that:
   job/taxonomy_landing.blade.php wraps its hero copy in .vd-hero__copy rather
   than restating any of these values. */
.vd-hero__copy {
    --vd-hero-h1: clamp(30px, 4.4vw, 46px);
    max-width: 780px;
    margin: 0 auto;
    text-align: center;
}
.vd-hero__copy h1 {
    margin: 0 0 12px;
    color: #fff;
    font-size: var(--vd-hero-h1);
    line-height: 1.12;
}

/*
   The accent as a SIBLING of the h1, for a page whose h1 text is owned by SEO.

   On the homepage the accent is a span INSIDE the h1, because there it
   completes the sentence -- "Find your next job" + "in the UAE" -- and that
   whole phrase is the h1 a crawler should read. An Emirate page's h1 is
   $title from TaxonomyController, which is ALSO the <title> tag, the SEO
   keywords and the JSON-LD name, so nothing may be added inside it; a
   rotating market name in there would read "Jobs in DubaiOil & Gas".
*/
.vd-hero__accent {
    display: block;
    margin: 0 0 12px;
    color: var(--uae-primary-on-dark);
    font-size: var(--vd-hero-h1);
    line-height: 1.12;
    font-weight: 700;
}
/* nowrap so the accent phrase never breaks mid-name. It used to be what kept
   375px from setting "Find your next job in / the UAE" and orphaning "in" on
   the first line; since 2026-10-26 the phrase is its own line anyway (see
   below), so this now only matters for the long names the rotation added --
   "in Ras Al Khaimah", "in Umm Al Quwain". */
.vd-hero__copy h1 span { color: var(--uae-primary-on-dark); white-space: nowrap; }

/* ---- the hero's rotating accent phrase (2026-10-26) -------------------- */

/*
   The accent phrase is its own LINE, not an inline tail, and that is a
   measurement rather than a preference. At the hero's 46px against the 780px
   copy column, "Find your next job in Umm Al Quwain" sets to 904px and
   "in Ras Al Khaimah" to 888px, so an inline phrase would flip the heading
   between one and two lines as it cycled. On its own line the widest phrase is
   453px and the box never reflows. It is also how the hero this was modelled
   on -- business.google.com's Local Service Ads page -- does it: its
   `.headline--animated span` is display:block for the same reason.

   Declared here rather than only in the JS-built markup so the heading is two
   lines from the first paint. The script swaps one block span for a grid of
   them, both one line tall, so enhancing it shifts nothing.
*/
.vd-hero__copy h1 > span {
    display: block;
}

/*
   Every phrase in the same grid cell: the box is one line tall and as wide as
   the widest phrase, so nothing on the page moves as the text changes. This is
   Google's `.headline-container { display: grid }` + `.headline { grid-area: 1/1 }`.
*/
/*
   align-items: center matters only where the phrases differ in line count.
   The homepage's are all one line, so the box is one line and this changes
   nothing there. An Emirate page's market names are longer -- six of Dubai's
   twelve wrap at 375px -- so the row is two lines tall and the short names
   would otherwise sit at the top of it with the slack underneath.
*/
.vd-rotate {
    display: grid;
    justify-items: center;
    align-items: center;
}

/*
   The resting state is BELOW the line and transparent; is-current lifts it into
   place and is-leaving carries it up and out, so a swap reads as the next
   phrase arriving rather than a crossfade. .45em keeps the travel proportional
   to the clamped font size instead of pinning it to Google's 30px, which would
   be most of a line at the 30px mobile size.

   The duration must stay in step with SWAP in public/js/vd-hero-rotate.js --
   that timer is what takes is-leaving off again.
*/
.vd-rotate__item {
    grid-area: 1 / 1;
    opacity: 0;
    transform: translateY(.45em);
    transition: opacity .48s ease, transform .48s cubic-bezier(.22, .61, .36, 1);
}

.vd-rotate__item.is-current {
    opacity: 1;
    transform: none;
}

.vd-rotate__item.is-leaving {
    opacity: 0;
    transform: translateY(-.45em);
}

/*
   Belt and braces: the script already returns before building anything when
   reduced motion is set, so this only matters if the preference is turned on
   after the stack exists -- a media query re-evaluates, a script that already
   ran does not.
*/
@media (prefers-reduced-motion: reduce) {
    .vd-rotate__item {
        transition: none;
        transform: none;
    }
    .vd-rotate__item:not(.is-current) {
        visibility: hidden;
    }
}
/* balance so the two lines come out even and "No fees" is not split across them
   -- the natural break left "No" orphaned at the end of line one. Ignored by
   browsers that do not support it, which simply get the natural break back. */
.vd-hero__copy p {
    margin: 0 auto;
    max-width: 62ch;
    color: rgba(255, 255, 255, .8);
    text-wrap: balance;
}

/* The search form include keeps its own markup; this is the pill shell.
   The ported POC rule for .vd-hero__search is a 1fr/1fr/auto grid, which
   assumed the POC DOM where the three controls were direct children. Here
   they arrive wrapped in form > .searchbar > .input-group, so the wrapper
   goes back to a plain block and the pill styling moves to .input-group. */
.vd-hero__search {
    display: block;
    max-width: 940px;
    margin: 26px auto 0;
    padding: 0;
    background: transparent;
    border-radius: 0;
    box-shadow: none;
}
.vd-hero__search form, .vd-hero__search .searchbar { width: 100%; margin: 0; }
.vd-hero__search .input-group {
    display: flex;
    align-items: center;
    gap: 6px;
    padding: 7px;
    border-radius: var(--r-card);
    background: var(--uae-surface);
    box-shadow: var(--shadow-card);
}
.vd-hero__search .jp-hero-search__field { position: relative; flex: 1 1 52%; min-width: 0; }
.vd-hero__search .jp-hero-search__field--select { flex-basis: 30%; border-inline-start: 1px solid var(--uae-line); }
.vd-hero__search .jp-hero-search__field > i {
    position: absolute;
    z-index: 2;
    inset-inline-start: 16px;
    top: 50%;
    transform: translateY(-50%);
    color: var(--uae-muted);
    font-size: 14px;
}
.vd-hero__search .form-control {
    height: 50px;
    min-height: 50px;
    padding-inline: 44px 14px;
    border: 0;
    background: transparent;
    box-shadow: none;
}
.vd-hero__search .form-control:focus { box-shadow: none; }
.vd-hero__search .jp-hero-search__btn {
    flex: 0 0 auto;
    min-width: 54px;
    height: 50px;
    border: 0;
    border-radius: var(--r-control);
    background: var(--uae-primary);
    color: #fff;
}
.vd-hero__search .jp-hero-search__btn:hover { background: var(--uae-primary-deep); color: #fff; }

.vd-hero__popular {
    display: flex;
    flex-wrap: wrap;
    align-items: center;
    justify-content: center;
    gap: 10px;
    margin-top: 18px;
    color: rgba(255, 255, 255, .6);
    font-size: 13px;
}
.vd-hero__popular a { color: #fff; text-decoration: underline; text-underline-offset: 3px; }

/* Trust strip sits between the hero and the first section */
.vd-trust { margin-top: -28px; position: relative; z-index: 2; }
.vd-trust .trust-strip { justify-content: space-between; }

/* Emirate count chips */
.vd-emirates { display: flex; flex-wrap: wrap; gap: 10px; }
.vd-emirate {
    display: inline-flex;
    align-items: center;
    gap: 9px;
    padding: 10px 16px;
    border: 1px solid var(--uae-line);
    border-radius: var(--r-pill);
    background: var(--uae-surface);
    color: var(--uae-ink);
    font-size: 15px;
    font-weight: var(--weight-strong);
}
.vd-emirate:hover { border-color: var(--uae-primary); color: var(--uae-primary-ink); text-decoration: none; }
.vd-emirate span {
    min-width: 24px;
    padding: 1px 8px;
    border-radius: var(--r-pill);
    background: var(--uae-sand);
    color: var(--uae-muted);
    font-size: 12px;
    font-weight: 700;
    text-align: center;
}
.vd-emirate:hover span { background: var(--uae-primary-wash); color: var(--uae-primary-ink); }

/* Industry tiles and section rhythm */
.uae-industries-section, .uae-emirates-section, .uae-jobs-section, .topemployers, .homeblogposts { padding: 60px 0; }
.uae-emirates-section, .topemployers { background: var(--uae-surface); }
.uae-industries-section, .uae-jobs-section, .homeblogposts { background: var(--uae-sand); }

/* Blog cards */
.blog-card__thumb { display: block; overflow: hidden; }
.blog-card__thumb img { width: 100%; height: 100%; object-fit: cover; }
.blog-card__cats { display: flex; flex-wrap: wrap; gap: 6px; margin-bottom: 9px; }
.blog-card h3 a { color: var(--uae-ink); }
.blog-card h3 a:hover { color: var(--uae-primary-ink); text-decoration: none; }
.blog-card p { margin: 0; font-size: 13px; }

/* Employer cards on the homepage grid */
.employer-card h3 { font-size: 15px; margin: 0; }
.employer-card h3 a { color: var(--uae-ink); }
.employer-card h3 a:hover { color: var(--uae-primary-ink); text-decoration: none; }
.employer-card p { margin: 3px 0 9px; font-size: 13px; }
.employer-card__logo { overflow: hidden; }
.employer-card__logo img { max-width: 100%; max-height: 100%; object-fit: contain; }

@media (max-width: 767.98px) {
    .vd-hero { padding: 42px 0 40px; }
    .section-head { display: block; }
    .section-head .vd-btn { margin-top: 14px; }
    .vd-hero__search .input-group { display: grid; gap: 6px; }
    .vd-hero__search .jp-hero-search__field--select { border-inline-start: 0; border-top: 1px solid var(--uae-line); }
    .vd-hero__search .jp-hero-search__btn { width: 100%; }
    .vd-trust { margin-top: 0; }
    .vd-trust .trust-strip { gap: 18px; }
    .uae-industries-section, .uae-emirates-section, .uae-jobs-section, .topemployers, .homeblogposts { padding: 42px 0; }
}

/* ---------- the emirate select in the hero pill ------------------------
   The select carries data-no-search="1", so jp-select2.js leaves it as a
   native control (see includes/search_form.blade.php). Styling it directly
   avoids fighting the select2 widget, whose label collapses inside a flex
   pill, and the caret below uses a logical inset so it flips in RTL.
   ---------------------------------------------------------------------- */

/* Padding, appearance and the caret all come from the legacy
   .jp-hero-search__field* rules in main.css, which carry !important and now
   use logical properties. Adding a second caret here produced two chevrons. */
.vd-hero__search select.form-control { cursor: pointer; }

/* if select2 ever does enhance a select in here, keep it inside the pill */
.vd-hero__search .select2-container { width: 100% !important; }
.vd-hero__search .select2-container--default .select2-selection--single {
    height: 50px;
    min-height: 50px;
    border: 0 !important;
    background: transparent;
}

/* ==========================================================================
   JOB DETAIL (Phase 3c)
   The jd-* base rules came across with the POC; these are the pieces the live
   page needs on top: button modifiers, the header card, the employer panel,
   the skills list rendered by Job::getJobSkillsList(), and the mobile bar.
   ========================================================================== */

.vd-btn--block { width: 100%; }
.vd-btn--disabled, .vd-btn--applied {
    background: var(--uae-sand);
    border-color: var(--uae-line);
    color: var(--uae-muted);
    cursor: default;
    pointer-events: none;
}
.vd-btn--applied { background: var(--uae-primary-wash); border-color: var(--uae-primary-wash); color: var(--uae-primary-ink); }

.jd-headcard { margin-bottom: 20px; }
.jd-head__logo { width: 64px; height: 64px; flex: 0 0 64px; font-size: 19px; }
.jd-head__main { flex: 1 1 auto; min-width: 0; }
.jd-head__main h1 { margin: 0; color: var(--uae-ink); font-size: clamp(22px, 2.6vw, 28px); line-height: 1.2; }
.jd-head__employer { margin-top: 6px; font-size: 14px; }
.jd-head__salary { margin-top: 12px; font-size: 20px; }
.jd-head__main .job-card__meta { margin-top: 10px; }
.jd-head__actions { flex: 0 0 210px; flex-direction: column; gap: 8px; }

.jd-prose { margin-top: 20px; }
.jd-prose h2 { font-size: 19px; margin: 0 0 12px; }
.jd-prose p { margin: 0 0 12px; }
.jd-prose ul:not(.jd-skills) { margin: 0 0 12px; padding-inline-start: 20px; }

/* getJobSkillsList() emits <li><a>…</a></li>; present them as pills */
ul.jd-skills { display: flex; flex-wrap: wrap; gap: 7px; margin: 0; padding: 0; list-style: none; }
ul.jd-skills li { list-style: none; }
ul.jd-skills li a {
    display: inline-flex;
    padding: 5px 11px;
    border: 1px solid var(--uae-line);
    border-radius: var(--r-pill);
    color: var(--uae-body);
    font-size: 12px;
}
ul.jd-skills li a:hover { border-color: var(--uae-primary); color: var(--uae-primary-ink); text-decoration: none; }

.jd-apply__box .vd-btn { margin-top: 10px; }
.jd-apply__note { margin: 14px 0 0; font-size: 13px; }

.jd-employer, .jd-map { margin-top: 16px; }
.jd-employer__about { margin: 12px 0; font-size: 13px; }
.jd-employer .vd-btn { margin-top: 4px; }
.jd-map .gmap, .jd-map iframe { width: 100%; height: 190px; border: 0; border-radius: var(--r-control); display: block; }

.jd-related { margin-top: 34px; }

.jd-applybar-spacer { display: none; }
@media (max-width: 991.98px) {
    /* Height comes from the bar itself (see the script in job/detail.blade.php):
       the bar wraps at narrow widths and adds the safe-area inset, so it is
       84-120px in practice. The fallback covers the tallest case for the
       no-JS path, where a little extra run-off is harmless. */
    .jd-applybar-spacer { display: block; height: var(--jd-applybar-h, 120px); }
    .jd-head { flex-wrap: wrap; }
    .jd-head__main h1 { font-size: 21px; }
}

/* ---------- INDUSTRIES HUB (job/categories.blade.php) ------------------- */

.vd-pagetitle h1 { margin: 0; font-size: 26px; }
.vd-pagetitle__sub { margin: 6px 0 0; font-size: 14px; }
/* break between counts, never inside one: a segment split across lines reads
   as if it belongs to its neighbour, which is worse in RTL */
.vd-pagetitle__sub bdi { white-space: nowrap; }

.vd-taxonomy-search { margin-bottom: 22px; }
.vd-taxonomy-search .field { margin-bottom: 0; }
/* auto width on the button so its label is never squeezed; the input takes
   the rest. Stacks below 560px, where a side-by-side pair gets too tight. */
.vd-taxonomy-search__row { display: grid; grid-template-columns: 1fr auto; gap: 10px; }
@media (max-width: 559.98px) {
    .vd-taxonomy-search__row { grid-template-columns: 1fr; }
}

.vd-tabs__count {
    margin-inline-start: 6px;
    padding: 1px 7px;
    border-radius: var(--r-pill);
    background: var(--uae-sand);
    color: var(--uae-muted);
    font-size: 11px;
    font-weight: var(--weight-strong);
}
.vd-tabs button.is-active .vd-tabs__count { background: var(--uae-primary-wash); color: var(--uae-ok); }

/* Panels are visible in the markup and hidden by the tab script, so the page
   still reads as three sections when the script does not run. [hidden] needs
   the explicit display:none because .vd-panel sets one. */
.vd-panel { display: block; margin-bottom: 34px; }
.vd-panel[hidden] { display: none; }

.vd-hubs { display: grid; gap: 14px; }
.vd-hub {
    padding: 18px;
    border: var(--card-border);
    border-radius: var(--r-card);
    background: var(--uae-surface);
    box-shadow: var(--shadow-card);
}
.vd-hub__head { display: flex; align-items: center; gap: 12px; margin-bottom: 14px; }
.vd-hub__head h3 { margin: 0; font-size: 16px; }
.vd-hub__head p { margin: 2px 0 0; font-size: 13px; }
.vd-hub__sectors { display: flex; flex-wrap: wrap; gap: 8px; }
/* the sector pills are links, so they get the interactive treatment the
   read-only .vd-skill pill does not have */
a.vd-skill:hover { border-color: var(--uae-primary); color: var(--uae-primary-ink); text-decoration: none; }

/* main.css already flips this arrow in RTL via
   html[dir="rtl"] .taxonomy-link-grid a > i:last-child, so only the push to
   the inline end is needed here. */
.vd-taxonomy-arrow { margin-inline-start: auto; }

/* ---------- HOMEPAGE AUDIENCE ROWS ------------------------------------- */

/* Its two rows carry g-lg-5, which sets --bs-gutter-x: 3rem on the row and so
   gives it -24px side margins. .container derives its own padding from the
   same variable, but the class is on the row, so the container keeps 12px and
   the row ends up 12px wider than the viewport — the homepage scrolls
   sideways at the lg step (12px at 1024). Setting the variable on the
   container too restores the pairing and keeps the 48px column gap. */
@media (min-width: 992px) {
    .home-audience > .container { --bs-gutter-x: 3rem; }
}

/* ---------- EMPLOYERS DIRECTORY (company/listing.blade.php) ------------- */

.vd-employer-filter { margin-bottom: 20px; }
.vd-employer-filter .field { margin-bottom: 0; }

/* the POC carries this as an inline flex:1 1 auto on the card's second child.
   min-width: 0 so a long employer name shrinks instead of pushing the card. */
.employer-card__body { flex: 1 1 auto; min-width: 0; }
.employer-card__flags { display: flex; flex-wrap: wrap; gap: 6px; }
/* the open-roles badge is a link on this page */
a.vd-badge:hover { text-decoration: none; border-color: var(--uae-primary); }
/* .employer-card is a flex row, so it needs telling to fill its grid cell,
   or cards in a row end up different heights */
.vd-results--grid .employer-card { height: 100%; }

.vd-results-count { margin: 14px 0 0; text-align: center; font-size: 13px; }

/* ---------- EMPLOYER PROFILE (company/detail.blade.php) ----------------- */

/* the POC header logo is 72px against the card's 56px */
.employer-card__logo--lg { width: 72px; height: 72px; flex: 0 0 72px; font-size: 21px; }
.emp-tick { font-size: 18px; vertical-align: middle; }
.emp-meta { margin: 6px 0 0; font-size: 14px; }
.emp-flags { margin-top: 12px; }

/* the verification lines: icon and text side by side, text wrapping under
   itself rather than under the icon */
.emp-check { display: flex; gap: 10px; margin: 0 0 14px; font-size: 14px; }
.emp-check > i { margin-top: 3px; flex: 0 0 auto; }
.emp-check small { display: block; margin-top: 2px; font-size: 12px; line-height: 1.45; }

.emp-facts, .jd-map { margin-top: 16px; }
.emp-facts .vd-table { margin: 0; }
/* a label column that does not stretch, so the values line up */
.emp-facts .vd-table td:first-child { width: 42%; font-size: 13px; }
.emp-facts .vd-table td { padding: 7px 0; border-bottom: 1px solid var(--uae-line); vertical-align: top; }
.emp-facts .vd-table tr:last-child td { border-bottom: 0; }

@media (max-width: 767.98px) {
    /* the actions column sits beside the lockup on desktop and below it here */
    .jd-headcard .jd-head__actions { width: 100%; }
    .employer-card__logo--lg { width: 56px; height: 56px; flex-basis: 56px; font-size: 17px; }
}

/* ---------- JOB FILTER SIDEBAR FACETS ---------------------------------- */

/* The rows in includes/job_list_side_bar.blade.php are .vd-facet labels now,
   but they still sit inside .optionlist, whose legacy rules fight the flex
   row: the real checkbox is display:none (a sibling <label> was drawn as the
   box), the li reserves 30px for it, and the count is absolutely positioned.
   Undone here rather than deleted, because .optionlist is still used by the
   jobseeker sidebar and two admin screens. */
.vd-facets li { position: static; margin-bottom: 0; padding: 0; }
.vd-facets li input[type="checkbox"] { display: inline-block; }
.vd-facets li span { position: static; top: auto; }
/* the whole row is the click target now */
.vd-facets .vd-facet { cursor: pointer; }
.vd-facets .vd-facet:hover { color: var(--uae-ink); }

/* ---------- SECTOR DIRECTORY (/sectors) -------------------------------- */
/* One row per sector: the name, its primary browse hub, and how many roles
   the map places there. A list rather than the .vd-hub__sectors pill wrap,
   because these rows carry three pieces of information each and pills only
   read well with one. */
.vd-sector-list { list-style: none; margin: 0; padding: 0; }
.vd-sector-list li {
    display: flex;
    align-items: baseline;
    flex-wrap: wrap;
    gap: 8px;
    padding: 8px 0;
    border-block-end: 1px solid var(--uae-line);
}
.vd-sector-list li:last-child { border-block-end: 0; }
.vd-sector-list li > a:first-child { font-weight: 600; color: var(--uae-ink); }
.vd-sector-list li > a:first-child:hover { color: var(--uae-primary-ink); text-decoration: none; }
/* pushed to the inline end so the role counts form a column the eye can scan,
   and logical so it follows the page direction without an RTL override */
.vd-sector-list li > small { margin-inline-start: auto; white-space: nowrap; }
.vd-sector-list__hub { font-size: .78em; }

/* Browse symbols on the Emirate pages, 2026-11-03. The <i> sits INSIDE the
   anchor -- `li > a:first-child` carries the row's weight and ink, so an icon
   placed beside the anchor would take that position and leave the industry
   name styled as the count next to it. See the note in
   job/partials/emirate_browse.blade.php.

   A fixed em width so forty names start on one line, and primary ink at .85 so
   the column reads as a rail the eye can run down rather than forty decorations
   competing with the names. */
.vd-sector-list li > a:first-child { display: inline-flex; align-items: baseline; gap: 9px; }
.vd-sector-list__ico { flex: 0 0 auto; width: 1.05em; color: var(--uae-primary-ink); font-size: .95em; opacity: .85; text-align: center; }
/* Eleven hubs hold 11+ sectors (/property has 19) against a median of 4, so the
   long lists go two-up on anything wider than a phone. Grid rather than CSS
   columns because each row is a flex line with a border, and columns would cut
   one in half across the gap. */
@media (min-width: 720px) {
    .vd-sector-list--two-col { display: grid; grid-template-columns: 1fr 1fr; column-gap: 32px; }
}

/* ---------- HUB SECTORS (a hub's own contents) -------------------------- */
/* The borrowed sectors are set apart rather than merged into the list above:
   they belong to another hub, and saying so is the point. */
.taxonomy-landing__sectors .section-head { margin-block-end: 8px; }
.taxonomy-landing__also {
    margin-block-start: 28px;
    padding-block-start: 20px;
    border-block-start: 1px solid var(--uae-line);
}
.taxonomy-landing__also h3 { margin: 0; font-size: 15px; }
.taxonomy-landing__also > p { margin: 4px 0 10px; font-size: 13px; }

/* The Emirate the visitor is already in: a pill that is not a link, so the row
   keeps its shape and says where they are. .vd-alpha carries its own is-active
   rule, so this one is written for the pill rows that are not the A-Z nav. */
.taxonomy-landing__elsewhere .vd-skill.is-active {
    background: var(--uae-primary);
    border-color: var(--uae-primary);
    color: #fff;
    cursor: default;
}
.taxonomy-landing__elsewhere-emirates { margin-block-start: 28px; }

/* ---------- A-Z NAV (/roles) ------------------------------------------- */
/* Letters with nothing behind them render as .is-empty rather than being
   omitted, so the alphabet keeps its shape and the gaps are legible. */
.vd-alpha { display: flex; flex-wrap: wrap; gap: 6px; margin-block-end: 24px; }
.vd-alpha .vd-skill { min-width: 34px; text-align: center; font-weight: 600; }
.vd-alpha .is-active { background: var(--uae-primary); color: #fff; border-color: var(--uae-primary); }
.vd-alpha .is-empty { opacity: .35; cursor: default; }

/* ---------- FOLLOW ON EMPLOYER CARDS (2026-10-10) ----------------------- */
.employer-card__actions { display: flex; gap: 8px; margin-top: 12px; }
.employer-card__actions .vd-btn { flex: none; }
.topemployers .employer-card__actions { margin-top: 10px; }
@media (max-width: 575.98px) { .employer-card__actions .vd-btn { flex: 1; justify-content: center; } }


/* ---------- SEARCH SUGGESTION SPINNER (2026-10-20) ---------------------- */
/*
   The /jobs-autocomplete lookup is a server round trip and the field said
   nothing while it ran, so a visitor typing into the hero box saw a dead
   input and no reason to wait. layouts/app.blade.php pins this ring to the
   INPUT's own trailing edge rather than to a wrapper, because the same
   id="jbsearch" sits inside five different wrappers across the site — the
   hero field, .jp-hero-search__field, .taxonomy-search-input,
   .vd-taxonomy-search__row and a bare Bootstrap .input-group — and the
   input's own box is the only thing that is the same shape in all of them.
   That is also why `left` and `top` arrive as inline px from JS: the class
   below only supplies the positioning context and the look.
*/
.vd-ac-host { position: relative; }

.vd-ac-spinner {
    position: absolute;
    z-index: 3;
    width: 18px;
    height: 18px;
    transform: translate(-50%, -50%);
    opacity: 0;
    visibility: hidden;
    pointer-events: none;
    transition: opacity .15s ease;
}
.vd-ac-host.is-searching .vd-ac-spinner { opacity: 1; visibility: visible; }

/* A conic sweep masked into a ring: one element, no SVG, and it inherits the
   brand colour instead of hardcoding one. */
.vd-ac-spinner__ring {
    display: block;
    width: 100%;
    height: 100%;
    border-radius: 50%;
    background: conic-gradient(from 90deg,
        rgba(var(--uae-primary-rgb), 0) 0%,
        rgba(var(--uae-primary-rgb), .18) 40%,
        var(--uae-primary) 100%);
    -webkit-mask: radial-gradient(farthest-side, #0000 calc(100% - 2.5px), #000 calc(100% - 2.5px));
            mask: radial-gradient(farthest-side, #0000 calc(100% - 2.5px), #000 calc(100% - 2.5px));
    animation: vd-ac-spin .7s linear infinite;
}
@keyframes vd-ac-spin { to { transform: rotate(360deg); } }

/* Keep a long query from running under the ring. !important is needed, not
   decorative: .jp-hero-search__field and .uae-search-hero__field both set
   their padding with an !important SHORTHAND, which beats a plain longhand
   however specific it is. Only the trailing side moves, so the text start and
   the caret stay where they are. */
.vd-ac-host > input { transition: padding-inline-end .15s ease; }
.vd-ac-host.is-searching > input { padding-inline-end: 36px !important; }

/* The ring is decorative; the state reaches screen readers as words. */
.vd-ac-live {
    position: absolute;
    width: 1px;
    height: 1px;
    padding: 0;
    margin: 0;
    border: 0;
    overflow: hidden;
    white-space: nowrap;
    clip-path: inset(50%);
}

@media (prefers-reduced-motion: reduce) {
    .vd-ac-spinner__ring { animation: vd-ac-fade 1.2s ease-in-out infinite; }
    @keyframes vd-ac-fade { 0%, 100% { opacity: .3; } 50% { opacity: 1; } }
}


/* ==========================================================================
   Job alert modal  (.vd-alert)
   --------------------------------------------------------------------------
   The markup is resources/views/job/partials/job_alert_modal.blade.php, which
   carries the reasoning for the content changes. This file carries the look.

   It lives here rather than in main.css because this sheet is linked AFTER
   main.css in layouts/app.blade.php, and three of the rules below have to beat
   an equal-specificity rule already in main.css: .modal-title (231),
   .modal-body (7162) and .modal.fade .modal-dialog (8068). Equal specificity is
   decided by source order, so being the later sheet is what wins it -- no
   !important needed anywhere in this block.
   ========================================================================== */

.vd-alert .modal-dialog {
    max-width: 468px;
}

.vd-alert .modal-content {
    border: 0;
    border-radius: var(--r-card);
    box-shadow: var(--shadow-pop);
    /* clips the illustration band to the bottom corners */
    overflow: hidden;
}

/* ---- header ---- */

.vd-alert__head {
    display: flex;
    align-items: center;
    gap: 12px;
    padding: 18px 20px 14px;
    border-bottom: 0;
}

.vd-alert__badge {
    display: inline-flex;
    align-items: center;
    justify-content: center;
    flex: 0 0 auto;
    inline-size: 40px;
    block-size: 40px;
    border-radius: var(--r-pill);
    background: var(--uae-primary-wash);
    color: var(--uae-primary-ink);
}

.vd-alert__badge svg {
    inline-size: 21px;
    block-size: 21px;
}

.vd-alert__head-text {
    display: flex;
    flex-direction: column;
    gap: 1px;
    min-inline-size: 0;
}

/* Beats .modal-title { font-size: 20px } in main.css by source order. */
.vd-alert__eyebrow {
    font-size: 12px;
    font-weight: 700;
    letter-spacing: .09em;
    text-transform: uppercase;
    color: var(--uae-primary-ink);
    line-height: 1.2;
}

.vd-alert__head-sub {
    font-size: 12.5px;
    color: var(--uae-muted);
    line-height: 1.3;
}

/*
   Bootstrap sets `margin: calc(-.5 * ...) ... auto` on .modal-header .btn-close.
   That trailing `auto` is a PHYSICAL margin-left, so in RTL it absorbed the free
   space on the wrong side and parked the x next to the title instead of out at
   the far edge. The logical property does the same job in both directions.

   TWO class names, not one. `.modal-header .btn-close` is (0,2,0) and a single
   `.vd-alert__close` is (0,1,0), so the first attempt lost outright and the
   computed margin stayed `margin-left: 188.675px`. Matching the specificity is
   enough to win it, because this sheet is linked after bootstrap.min.css.
*/
.vd-alert__head .vd-alert__close {
    margin: 0;
    margin-inline-start: auto;
    flex: 0 0 auto;
    opacity: .45;
}

.vd-alert__head .vd-alert__close:hover,
.vd-alert__head .vd-alert__close:focus-visible {
    opacity: 1;
}

/* ---- body ---- */

/* Beats .modal-body { padding: 30px } in main.css by source order. */
.vd-alert__body {
    padding: 2px 20px 20px;
}

.vd-alert__title {
    margin: 0 0 14px;
    font-size: 21px;
    line-height: 1.33;
    font-weight: 600;
    color: var(--uae-ink);
}

.vd-alert__title strong {
    font-weight: 700;
    color: var(--uae-primary-ink);
}

.vd-alert__points {
    list-style: none;
    margin: 0 0 18px;
    padding: 0;
    display: grid;
    gap: 7px;
}

.vd-alert__points li {
    position: relative;
    padding-inline-start: 26px;
    font-size: 13.5px;
    line-height: 1.45;
    color: var(--uae-body);
}

/*
   The tick is a pseudo-element rather than an <svg> per row: three identical
   marks in the markup would be three copies of the same path, and the list
   reads as plain sentences to a screen reader this way.
*/
.vd-alert__points li::before {
    content: '';
    position: absolute;
    inset-inline-start: 0;
    inset-block-start: 2px;
    inline-size: 17px;
    block-size: 17px;
    border-radius: var(--r-pill);
    background: var(--uae-primary-wash)
        url("data:image/svg+xml,%3Csvg xmlns='http://www.w3.org/2000/svg' viewBox='0 0 24 24' fill='none' stroke='%230b6b3a' stroke-width='3.4' stroke-linecap='round' stroke-linejoin='round'%3E%3Cpath d='m5 13 4 4 10-10'/%3E%3C/svg%3E")
        center / 11px 11px no-repeat;
}

/* ---- the field ---- */

.vd-alert__label {
    display: block;
    margin: 0 0 6px;
    font-size: 12.5px;
    font-weight: 600;
    color: var(--uae-body);
}

/*
   Block, not inline: jQuery Validate's default errorPlacement does
   error.insertAfter(element), so its <label class="error"> lands INSIDE this
   wrapper, after the input. A block wrapper lets that label fall underneath
   instead of being squeezed onto the same line as the field.
*/
.vd-alert__input-wrap {
    display: block;
    position: relative;
}

.vd-alert__input-icon {
    position: absolute;
    inset-inline-start: 13px;
    inset-block-start: 14px;
    inline-size: 18px;
    block-size: 18px;
    color: var(--uae-muted);
    pointer-events: none;
}

.vd-alert__input-wrap .form-control {
    block-size: 46px;
    padding-inline: 40px 14px;
    border: 1px solid var(--uae-line);
    border-radius: var(--r-control);
    font-size: 14.5px;
    color: var(--uae-ink);
    box-shadow: none;
}

.vd-alert__input-wrap .form-control::placeholder {
    color: var(--uae-muted);
}

.vd-alert__input-wrap .form-control:focus {
    border-color: var(--uae-primary);
    box-shadow: 0 0 0 3px rgba(var(--uae-primary-rgb), .14);
}

/*
   The shorthand, not border-color, and one class more than the base rule
   above. jQuery Validate puts `error` on the input itself, and a bare
   `border-color` at (0,3,0) did not paint -- the field stayed --uae-line
   while the message below it went red. A shorthand cannot be half-overridden
   by a later `border` shorthand, which is what the stack of .form-control
   rules across bootstrap, main.css and vd-primitives.css is full of.
*/
.vd-alert .vd-alert__input-wrap .form-control.error {
    border: 1px solid var(--uae-danger);
}

.vd-alert__input-wrap label.error {
    display: block;
    margin: 6px 0 0;
    font-size: 12.5px;
    font-weight: 500;
    color: var(--uae-danger);
}

/* ---- the actions ---- */

/*
   The submit is full width and directly under the field it submits. The old
   footer row held Close and Submit side by side, Close first, and styled it
   `btn btn-default` -- a Bootstrap 3 class, absent from Bootstrap 5, which left
   it white with green text and reading as the primary action.
*/
.vd-alert__submit {
    display: block;
    inline-size: 100%;
    margin-block-start: 14px;
    block-size: 46px;
    border: 0;
    border-radius: var(--r-control);
    font-size: 15px;
    font-weight: 600;
}

.vd-alert__later {
    display: block;
    inline-size: 100%;
    margin-block-start: 10px;
    padding: 6px 0;
    border: 0;
    background: none;
    font-size: 13px;
    font-weight: 500;
    color: var(--uae-muted);
}

.vd-alert__later:hover,
.vd-alert__later:focus-visible {
    color: var(--uae-ink);
    text-decoration: underline;
}

/* ---- the illustration ---- */

.vd-alert__art {
    margin: 0;
    border-block-start: 1px solid var(--uae-line);
    background: var(--uae-sand);
    /* kills the inline-element descender gap under the svg */
    line-height: 0;
}

.vd-alert__art svg {
    display: block;
    inline-size: 100%;
    block-size: auto;
}

.vd-alert__art-hill { fill: var(--uae-primary-wash); }

.vd-alert__art-ticks path {
    fill: none;
    stroke: var(--uae-primary);
    stroke-width: 3;
    stroke-linecap: round;
    opacity: .26;
}

.vd-alert__art-card rect {
    fill: var(--uae-surface);
    stroke: var(--uae-line);
    stroke-width: 1.5;
}

.vd-alert__art-card rect.vd-alert__art-chip {
    fill: var(--uae-primary);
    stroke: none;
}

.vd-alert__art-card rect.vd-alert__art-line {
    fill: var(--uae-line);
    stroke: none;
}

/*
   Both panels are the same green; the opening is read from the SHADE over the
   part of the back wall the front panel's V leaves exposed. Colouring the back
   --uae-primary-deep and the front --uae-primary was the first attempt and
   failed: #00732f against #0b6b3a is a 3% luminance difference, so the
   envelope rendered as one flat slab with no mouth. A translucent ink wash
   reads as shadow at any size and keeps working if the green ever changes.
*/
.vd-alert__art-back { fill: var(--uae-primary); }
.vd-alert__art-front { fill: var(--uae-primary); }
.vd-alert__art-mouth { fill: rgba(var(--uae-ink-rgb), .34); }

/* Gold, because this is the palette's one "premium / attention" accent and red
   is reserved for errors. */
.vd-alert__art-bell-bg { fill: var(--uae-gold); }

.vd-alert__art-bell {
    stroke: var(--uae-surface);
    fill: none;
}

/* ---- small screens ---- */

@media (max-width: 575.98px) {
    .vd-alert__head { padding: 16px 16px 12px; }
    .vd-alert__body { padding: 2px 16px 16px; }
    .vd-alert__title { font-size: 19px; }
}

@media (prefers-reduced-motion: reduce) {
    /* Beats .modal.fade .modal-dialog { transform: translate(0, 10px) } in
       main.css by source order, so the panel appears without the slide. */
    .vd-alert.fade .modal-dialog { transform: none; }
}


/* =========================================================================
   Phone top-bar actions — theme switch + notifications
   =========================================================================
   These sit to the left of the burger in .navbar-header, which main.css only
   shows below 990px (it is display:none above that, where the desktop nav
   takes over). The burger itself is position:absolute { top:15px; right:15px }
   and is NOT in flow, so these cannot simply be floated next to it: they are
   absolutely positioned against the same ancestor and offset clear of it.

   `right` is physical rather than logical on purpose — the burger uses
   `right` too, so in RTL both stay on the same side and keep their pairing.
   ========================================================================= */

.vd-hdr-acts { display: none; }

@media screen and (max-width: 990px) {
    .vd-hdr-acts {
        position: absolute;
        top: 5px;   /* centres the 44px buttons on the 42px burger, which
                        sits at y=6 here, not at the top:15px its own rule
                        claims - it resolves against a different ancestor */
        right: 72px;
        z-index: 2;
        display: flex;
        align-items: center;
        gap: 2px;
    }
}

.vd-hdr-act {
    position: relative;
    display: grid;
    place-items: center;
    width: 44px;              /* the tap-target floor used across the phone UI */
    height: 44px;
    padding: 0;
    border: 0;
    background: transparent;
    border-radius: var(--r-pill);
    color: var(--uae-body);
    font-size: 18px;
    line-height: 1;
    text-decoration: none;
}

.vd-hdr-act:hover,
.vd-hdr-act:focus-visible {
    background: var(--uae-primary-wash);
    color: var(--uae-primary-ink);
}

.vd-hdr-act i { pointer-events: none; }

/* The unread count. Capped at "9+" by the view, so the pill never grows wide
   enough to collide with the burger. */
.vd-hdr-badge {
    position: absolute;
    top: 4px;
    right: 2px;
    min-width: 17px;
    height: 17px;
    padding: 0 4px;
    border-radius: var(--r-pill);
    background: var(--uae-danger);
    border: 2px solid var(--uae-surface);
    box-sizing: content-box;
    color: #fff;
    font-size: 10px;
    font-weight: 700;
    line-height: 17px;
    text-align: center;
}


/* The desktop copy of the night-mode switch, an <li> of the main nav.
   That <ul> doubles as the mobile drawer, so this is hidden below 992px —
   the navbar-expand-lg breakpoint, where the nav collapses and .vd-hdr-acts
   in the phone bar takes over. Anchoring it to 992 rather than main.css's
   990px .navbar-header query is deliberate: the nav is what decides whether
   this <li> is a toolbar button or a drawer row. */
.vd-theme-li { display: none; }

@media (min-width: 992px) {
    .vd-theme-li {
        display: flex;
        align-items: center;
    }

    /* The nav sets its own type scale on .nav-link; this is a button, not a
       link, so it needs the icon size restated. */
    .vd-theme-li .vd-hdr-act {
        width: 40px;
        height: 40px;
        font-size: 17px;
    }
}


/* Sprite icons — the stroke set ported from the prototype.
   resources/views/includes/icon_sprite.blade.php holds the symbols.

   An inline <svg> has no intrinsic size the way an icon font does, so without
   a width and height it lays out at 0x0 and the row looks like it lost its
   icon. This is the floor; each component overrides it. currentColor does the
   rest, so these need no colour rule and work in both themes untouched. */
.vd-ico {
    width: 18px;
    height: 18px;
    flex: none;
    display: inline-block;
    vertical-align: -0.18em;
}

/* Top-bar icons are sprite icons too (theme switch + bell). 21px is the size
   the prototype gives its appbar actions; the desktop copy sits in a 40px
   button rather than 44px, so it drops a notch to stay in proportion. */
.vd-hdr-act .vd-ico { width: 21px; height: 21px; vertical-align: 0; }

@media (min-width: 992px) {
    .vd-theme-li .vd-hdr-act .vd-ico { width: 19px; height: 19px; }
}

/* The burger. .navbar-toggler sized its glyph by font-size, which an inline
   SVG ignores. 20px matches the 21px actions beside it once the toggler's own
   padding is accounted for. */
.navbar-toggler .vd-ico { width: 20px; height: 20px; vertical-align: 0; }


/* =========================================================================
   Phone wordmark — smaller, one line
   =========================================================================
   Measured at 375px before this: the logo block was 197px wide of 375 (53%
   of the bar) and left a 5px gap before the theme and bell buttons, so the
   top bar read as crowded rather than composed.

   Two causes, and the subtitle is the bigger one. At 9px it is below any
   legible size — decoration, not information — and it is what forces the
   block onto two lines and up to 35px tall. It stays on desktop, where it has
   the room and the type size to be read.

   The prototype's appbar is the reference: one line, 17px, no subtitle.
   The .ae is kept, though the prototype drops it — the domain is the brand,
   and that is not a decision for a stylesheet to make quietly.

   Breakpoint is Bootstrap's lg, matching .vd-theme-li, because this is the
   same question: below lg the header is a phone bar, above it is a nav.
   ========================================================================= */

@media (max-width: 991.98px) {
    /* #siteheader-scoped, because that is how the rules being overridden are
       written: `#siteheader .site-logo small` carries an ID and beats a plain
       class selector whatever the source order. */
    #siteheader .site-logo small { display: none; }

    /* The bar's 56px height came from the two-line logo plus its 10px
       margins. With one line that would collapse to ~40px and the burger,
       which is 42px tall, would overhang it. Hold the height here.

       The margins are 17px rather than 18px because the mark is now the
       tallest thing in the link: 17 * 2.3 * .567 = 22.2px against 17px of
       type, so 18px margins would have pushed the bar to 58px. */
    #siteheader .site-logo {
        --vd-logo-fs: 17px;
        margin-top: 17px;
        margin-bottom: 17px;
    }
}


/* =========================================================================
   Results toolbar: Filter beside Sort  (2026-10-24)
   =========================================================================
   The mobile filter trigger used to be .uae-filter-bottombar — a fixed,
   full-width bar at the foot of the viewport. Stacked on the 58px tab bar it
   cost 127px of an 812px phone, 16% of the screen, permanently, to hold one
   button. Filter and Sort narrow the same list, so they now share a row.

   The toolbar is sticky, which is the only thing the fixed bar genuinely
   bought: Filter stays reachable part-way down a long list.
   ========================================================================= */

.vd-toolbar__acts { display: flex; align-items: center; gap: 10px; }

.vd-filter-btn {
    display: inline-flex;
    align-items: center;
    gap: 8px;
    min-height: 40px;
    padding: 0 14px;
    border: 1px solid var(--uae-line);
    border-radius: var(--r-control);
    background: var(--uae-surface);
    color: var(--uae-ink);
    font-size: 13.5px;
    font-weight: 600;
    white-space: nowrap;
}

.vd-filter-btn:hover,
.vd-filter-btn:focus-visible { border-color: var(--uae-primary); color: var(--uae-primary-ink); }

.vd-filter-btn i { font-size: 13px; color: var(--uae-muted); }

/* The count. Hidden by the view when zero, and kept honest after AJAX by
   refreshFilterCount() in listing-ajax-filters.js, which writes to every
   [data-filter-count] on the page. */
.vd-filter-btn strong {
    display: inline-grid;
    place-items: center;
    min-width: 18px;
    height: 18px;
    padding: 0 5px;
    border-radius: var(--r-pill);
    background: var(--uae-primary);
    color: #fff;
    font-size: 11px;
    line-height: 1;
}

.vd-filter-btn strong[hidden] { display: none; }

@media (max-width: 991.98px) {
    .vd-toolbar {
        position: sticky;
        /* 57px is the header's height; .header.issticky is position:fixed at
           top:0 past 500px of scroll, so anything less hides under it. */
        top: 57px;
        z-index: 8;
        margin-inline: -16px;
        padding: 10px 16px;
        background: var(--uae-surface);
        border-block-end: 1px solid var(--uae-line);
    }

    /* The count block shrinks so the row fits one line on a 375px screen. */
    .vd-toolbar h2 {
        font-size: 16px;
        /* Hard ceiling of two lines. The heading now names the search term
           and the place, so it is no longer a fixed-length count: measured
           at 320px, a 40-char query in Ras Al Khaimah ran to three lines and
           took this STICKY bar to 147px. The PHP caps the query at 28, which
           holds it to two; this is the guarantee for whatever that cap does
           not foresee - a longer place name, or Arabic. */
        display: -webkit-box;
        -webkit-box-orient: vertical;
        -webkit-line-clamp: 2;
        overflow: hidden;
    }
    .vd-toolbar .vd-eyebrow,
    .vd-toolbar small { display: none; }

    /* The control states its own value, so the "Sort by" label is redundant
       here. Scoped to __label and NOT to `.vd-sort span`, which it used to
       be: that also matched the value inside the button, the visually-hidden
       name screen readers get, and every option's text in the menu. */
    .vd-sort__label { display: none; }
}

/* ---- LANGUAGE SWITCHER: LINKS ON LOCALE-PREFIXED PAGES (2026-10-26) -------
   On the 21 /{locale}/ routes the switcher offers each language's own URL
   instead of POSTing set-locale, which the URL overrode on the next request
   (see the note in includes/header.blade.php). So a chip is sometimes an <a>
   and sometimes a <span>, and both need the <button>'s box back: the rule
   above sets font and colour but relies on the UA's inline-block, and an
   anchor also arrives underlined.

   Appended at EOF, outside the drawer's media query, so it wins on order at
   equal specificity for the properties it restates and nothing else moves.
   Tokens only — no literal colours for build_dark_theme.php to map. */
#nav-main a.mobile-lang-chip,
#nav-main span.mobile-lang-chip {
    display: inline-block;
    text-decoration: none;
}

/* The language a page has no translation for: present, so the reader can see
   the site has it, but plainly not a control. The knowledgebase is the only
   tier in this state today — English-only guides, P3. */
#nav-main .mobile-lang-chip.is-off,
#siteheader .mobile-lang .dropdown-menu .nav-link[aria-disabled="true"] {
    opacity: .55;
    cursor: not-allowed;
}

/* BEGIN blue-collar family palette — generated by scripts/blue_collar_css.php, do not edit by hand */

.vd-bcc--build {
    --bcc-ink: #9A3412;
    --bcc-tint: #FFEDD5;
    --bcc-line: #9A3412;
    --bcc-fill: #EA7317;
    --bcc-pop: #FFEDD5;
    --bcc-alt: #EA7317;
}
.vd-bcc--mep {
    --bcc-ink: #1D4ED8;
    --bcc-tint: #DBEAFE;
    --bcc-line: #1D4ED8;
    --bcc-fill: #3B82F6;
    --bcc-pop: #DBEAFE;
    --bcc-alt: #3B82F6;
}
.vd-bcc--move {
    --bcc-ink: #0F766E;
    --bcc-tint: #CCFBF1;
    --bcc-line: #0F766E;
    --bcc-fill: #14B8A6;
    --bcc-pop: #CCFBF1;
    --bcc-alt: #14B8A6;
}
.vd-bcc--food {
    --bcc-ink: #BE123C;
    --bcc-tint: #FFE4E6;
    --bcc-line: #BE123C;
    --bcc-fill: #F43F5E;
    --bcc-pop: #FFE4E6;
    --bcc-alt: #F43F5E;
}
.vd-bcc--fm {
    --bcc-ink: #0369A1;
    --bcc-tint: #E0F2FE;
    --bcc-line: #0369A1;
    --bcc-fill: #0EA5E9;
    --bcc-pop: #E0F2FE;
    --bcc-alt: #0EA5E9;
}
.vd-bcc--retail {
    --bcc-ink: #6D28D9;
    --bcc-tint: #EDE9FE;
    --bcc-line: #6D28D9;
    --bcc-fill: #8B5CF6;
    --bcc-pop: #EDE9FE;
    --bcc-alt: #8B5CF6;
}
.vd-bcc--prod {
    --bcc-ink: #4338CA;
    --bcc-tint: #E0E7FF;
    --bcc-line: #4338CA;
    --bcc-fill: #6366F1;
    --bcc-pop: #E0E7FF;
    --bcc-alt: #6366F1;
}
.vd-bcc--care {
    --bcc-ink: #0B6B3A;
    --bcc-tint: #D7F0E2;
    --bcc-line: #0B6B3A;
    --bcc-fill: #10B981;
    --bcc-pop: #D7F0E2;
    --bcc-alt: #10B981;
}
/* END blue-collar family palette */

/* ---------- BLUE-COLLAR CATEGORY CARDS ---------------------------------- */

/*
   The trade grid on the homepage and the walk-in hub. Related to .tile above
   but deliberately not the same component: .tile carries one brand-green wash
   for every item, and the whole point here is that the wash differs by family.

   The family class sets --bcc-ink / --bcc-tint and the three colours the
   IconPark sprite draws with; the generated palette block further up this file
   holds the values, and dark-theme-manual.css restates them for night.

   Colour is a grouping signal, not decoration. The icon is aria-hidden and the
   trade is always spelled out next to it, so nothing here is carried by hue
   alone — which is also why the mid-tone fill is allowed to sit at low contrast
   against its own tile. The dark outline is what makes the glyph readable.
*/

.vd-bcc-grid {
    display: grid;
    grid-template-columns: repeat(auto-fill, minmax(190px, 1fr));
    gap: 12px;
}

.vd-bcc {
    display: block;
    padding: 16px;
    border: var(--card-border);
    border-radius: var(--r-card);
    background: var(--uae-surface);
    box-shadow: var(--shadow-card);
    color: var(--uae-ink);
}

.vd-bcc:hover,
.vd-bcc:focus-visible {
    border-color: var(--bcc-ink);
    text-decoration: none;
}

.vd-bcc__ico {
    display: grid;
    place-items: center;
    width: 42px;
    height: 42px;
    margin-bottom: 11px;
    border-radius: var(--r-control);
    background: var(--bcc-tint);
}

.vd-bcc__ico svg { width: 26px; height: 26px; }

.vd-bcc__name {
    display: block;
    margin: 0;
    font-size: 15px;
    font-weight: 600;
    line-height: 1.3;
}

.vd-bcc__fam {
    display: block;
    margin-top: 3px;
    color: var(--uae-muted);
    font-size: 12.5px;
}

/*
   The walk-in hub shows all 32 rather than a homepage twelve, so the cards go
   down a size there and drop the family line — at that count the tint is doing
   the grouping on its own and repeating it in words is noise.
*/
.vd-bcc-grid--compact { grid-template-columns: repeat(auto-fill, minmax(146px, 1fr)); gap: 10px; }
.vd-bcc-grid--compact .vd-bcc { padding: 12px; }
.vd-bcc-grid--compact .vd-bcc__ico { width: 36px; height: 36px; margin-bottom: 9px; }
.vd-bcc-grid--compact .vd-bcc__ico svg { width: 22px; height: 22px; }
.vd-bcc-grid--compact .vd-bcc__name { font-size: 13.5px; }

@media (max-width: 575.98px) {
    .vd-bcc-grid { grid-template-columns: repeat(auto-fill, minmax(150px, 1fr)); }
    .vd-bcc-grid--compact { grid-template-columns: repeat(auto-fill, minmax(124px, 1fr)); }
}

/* ---- the photo card  (.vd-bcc--photo, 2026-10-31) ------------------------

   The homepage trade row shows a PHOTOGRAPH of the trade instead of its icon:
   a transparent cutout of a worker in uniform standing in the bottom trailing
   corner of a card washed in the family tint, with the trade name over the
   clear corner opposite. Built by scripts/blue_collar_card_images.php — read
   that file before regenerating anything, it is where the framing decisions
   live.

   THE TITLE OVERLAYS THE PHOTO; IT IS NOT A BAND UNDER IT. This shipped as a
   band for a few hours on 2026-10-31 and it was wrong twice over. The figures
   are drawn flush to one side with the opposite corner left clear precisely so
   a title can go there — a band throws that composition away. And because the
   image then had to end where the band began, every figure was visibly
   chopped off at the shins by a white rule, which reads as a photograph
   cropped badly rather than as a design.

   THE PHOTO CARD IS THE HOMEPAGE ROW ONLY, and that is a coverage fact rather
   than a style preference. There are twelve photographs and the walk-in hub
   renders all 32 trades; a 32-card grid where 20 cards fell back to an icon at
   photo-card height would read as 20 broken cards. The icon card above is
   untouched and is still what every other caller gets — the modifier is opt-in
   from includes/blue_collar_grid.blade.php, which also falls back to the icon
   per card when a photo is missing, so a thirteenth trade can be added to the
   row before its art arrives.

   NO LITERAL COLOUR, which matters more here than usual: the title is the
   family's own ink on the family's own tint, a pair the palette already
   defines for both themes (scripts/dark-theme-manual.css, generated by
   blue_collar_css.php). So night mode needs nothing from
   build_dark_theme.php and nothing added by hand, and the colour coding
   survives the theme without a second palette to maintain. A cutout on a dark
   tint still reads: the figures are lit, not silhouettes. */

.vd-bcc--photo {
    position: relative;
    padding: 0;
    overflow: hidden;
    /* The card's own wash. The image is a cutout with no background of its
       own, so this is what the figure stands on — and it is also what fills
       any slack the flex row hands the card; see the note on the image. */
    background: var(--bcc-tint);
    /* The frame the build script writes. The card reserves its height before
       the lazy image arrives, so the drifting row cannot reflow mid-scroll. */
    aspect-ratio: 3 / 4;
    /* Keeps the image's corners inside the card's radius on Safari, which does
       not clip a transformed child to an ancestor's border-radius. */
    isolation: isolate;
}

/* THE IMAGE FILLS THE CARD, which is the fix for the gap that showed up on a
   phone. The card is a flex item in .vd-mq__track, so it is STRETCHED to the
   tallest card in the row — and when the title wrapped to an extra line on one
   narrow card, every other card grew with it while the image kept its own 3:4
   height. The leftover sat as a strip of nothing at the foot of the card,
   which is the "not sticking to the card" to avoid reintroducing.

   Absolute + inset:0 means the image is always exactly the card, whatever the
   row does to it. `contain` with a bottom-trailing anchor then spends any
   slack at the TOP, where there is only tint to look at — never at the bottom,
   where it would lift the figure off the card's edge. */
.vd-bcc__photo {
    position: absolute;
    inset: 0;
    inline-size: 100%;
    block-size: 100%;
    object-fit: contain;
    object-position: 100% 100%;
    transition: transform .45s cubic-bezier(.22, .61, .36, 1);
}

/* In RTL the title moves to the right-hand corner, so the figure has to move
   out from under it. The art is not mirrored — these are photographs of people
   and flipping them flips watch hands, buttoning and lettering — it is only
   re-anchored to the other corner. */
[dir="rtl"] .vd-bcc__photo { object-position: 0% 100%; }

/* The same small creep the hub photos make, and the same reason: the two rows
   sit next to each other on the homepage, and one that moves on hover beside
   one that does not reads as a fault. The origin is the corner the figure is
   anchored to, so it grows INTO the card and stays planted on both edges —
   scaling from the centre would lift it off them. */
.vd-bcc--photo:hover .vd-bcc__photo,
.vd-bcc--photo:focus-visible .vd-bcc__photo {
    transform: scale(1.055);
    transform-origin: 100% 100%;
}
[dir="rtl"] .vd-bcc--photo:hover .vd-bcc__photo,
[dir="rtl"] .vd-bcc--photo:focus-visible .vd-bcc__photo { transform-origin: 0% 100%; }

/* The title block, over the clear corner. z-index because the image is
   positioned and would otherwise paint over it on equal footing.

   The build script gives the figure the bottom 68% of the frame, so this box
   has the top 32% to itself — 87px on the narrowest phone card (203x271)
   against the ~53px the name and the family line measure to at that size. It
   held three lines until 2026-11-01, when the CTA moved to the foot, and the
   slack it has now is why SUBJECT_H was NOT raised back: the figure growing
   would take the foot's clear strip, which the CTA now depends on, and give
   the top band room it no longer needs. One number, two constraints, and the
   tighter one moved to the bottom of the card.

   The phone card is the binding case for either band, not the desktop one:
   the type clamps bottom out before the card does, so the block stops
   shrinking while the card keeps going. */
.vd-bcc__cap {
    position: absolute;
    inset-block-start: 0;
    inset-inline: 0;
    z-index: 2;
    padding: 12px 14px 0;
    color: var(--bcc-ink);
}

/* THE TYPE SCALES WITH THE CARD, not with the viewport — the same expression
   .tile__cap uses, for the reason documented there: --vd-mq-w is the measured
   card width, so one rule covers every breakpoint and any per-view count set
   later. The clamp ends hold it readable if the script never runs. */
.vd-bcc--photo .vd-bcc__name {
    font-size: clamp(13.5px, calc(var(--vd-mq-w, 190px) * .068), 18px);
    font-weight: 700;
    color: inherit;
}
/* NO OPACITY ON THIS LINE, and no --uae-muted either. A grey second line next
   to a coloured first one reads as two unrelated pieces of text, so it wants
   to be the family's own ink held back — but measured on a clean light load,
   the worst family (move: #0F766E on #CCFBF1) is 4.86:1 at FULL strength, so
   there is no headroom to hold back with: .78 took it to 3.26:1 and even .92
   only reached 4.17:1, both failures. Size and weight carry the hierarchy
   instead, which costs nothing. Re-check this with the real numbers if a
   family tint is ever re-toned; it has less margin than it looks. */
.vd-bcc--photo .vd-bcc__fam {
    margin-top: 1px;
    font-size: clamp(11.5px, calc(var(--vd-mq-w, 190px) * .055), 14px);
    font-weight: 500;
    color: inherit;
}

/* "View jobs →". The card has been a link since it shipped and nothing on it
   said so — a photograph with a name over it reads as a picture, so people
   were being asked to guess that a trade tile goes somewhere.

   IT SITS IN THE CARD'S BOTTOM-LEADING CORNER, where the owner asked for it
   on 2026-11-01. That corner is not clear by construction the way the top one
   is: the build script anchors every figure to the bottom TRAILING corner, so
   what is left at the foot is whatever that particular figure did not need.
   Measured over the twelve at SUBJECT_H 0.68, the clear strip runs from 72.9%
   of the card width (construction labourer) down to 21.2% (heavy driver, who
   is sitting in a truck cab that reaches well over to the left), against the
   ~37% this text and its padding need. Eleven clear it; the heavy driver does
   not, which is what the ::after below exists for.

   SO RAISING SUBJECT_H NOW COSTS TWICE — it eats the title band at the top
   and this strip at the foot. At 0.80 the worst foot was 7% clear, and no
   scrim saves a line of text laid across a man's knees.

   Underlined on hover rather than coloured or filled: it is an affordance
   inside a link, not a second button, and a pill here would be a second
   filled object on a card that is already a block of colour. */
.vd-bcc__cta {
    position: absolute;
    inset-block-end: 0;
    inset-inline-start: 0;
    z-index: 2;
    display: inline-flex;
    align-items: center;
    gap: .4em;
    padding: 0 14px 12px;
    font-size: clamp(11.5px, calc(var(--vd-mq-w, 190px) * .052), 13.5px);
    font-weight: 600;
    color: var(--bcc-ink);
}

/* The patch of tint the CTA stands on. It is the card's OWN --bcc-tint, so on
   the eleven cards whose foot is already clear it paints tint over tint and
   is invisible — nothing to see and nothing to go wrong. It earns its place
   on the twelfth, where the truck cab comes to 21% of the width and the arrow
   would otherwise land on a wing mirror. A thirteenth trade whose art reaches
   further left is covered without anyone having to notice.

   IT IS SIZED OFF THE TEXT, NOT OFF THE CARD, and that is the whole point of
   putting it on a pseudo-element of the CTA rather than a corner gradient on
   the card. A card-percentage ellipse looks right on the widest card and
   fails on the narrowest: the type clamps stop scaling down while the card
   keeps shrinking, so "View jobs →" is 32% of a 266px card and 42% of a 190px
   one, and an ellipse tuned to the first leaves the arrow hanging off the
   edge of the second. Measured that way in dark mode, two cards came out at
   2.62:1 and 2.69:1. Anchored to the text it is 4.86:1 light and 8.27:1 dark
   everywhere, which is the plain tint — i.e. nothing shows through at all.

   AN ELLIPSE AROUND THE TEXT, NOT A BAND ACROSS THE FOOT. A full-width band
   would wash out the one thing the composition rests on — the figure standing
   ON the card's bottom edge. -32px of bleed with the opaque stop at 62% puts
   the text's own corners inside the solid part with room to spare and still
   leaves ~26px of falloff, which is long enough not to draw a rim where it
   crosses the cab; anything the bleed pushes past the card is cut by the
   card's overflow. No literal colour here either, so build_dark_theme.php
   stays out of it. */
.vd-bcc__cta::before {
    content: "";
    position: absolute;
    inset: -32px;
    z-index: -1;
    background: radial-gradient(farthest-side, var(--bcc-tint) 62%, transparent 100%);
}

.vd-bcc__cta i {
    font-size: .85em;
    transition: transform .25s ease;
}

/* The arrow must point the way the text runs, so it is mirrored off the
   inline axis rather than swapped for a second glyph — the same treatment
   .vd-mq__nav i gets. */
[dir="rtl"] .vd-bcc__cta i { transform: scaleX(-1); }

.vd-bcc--photo:hover .vd-bcc__cta,
.vd-bcc--photo:focus-visible .vd-bcc__cta { text-decoration: underline; }
.vd-bcc--photo:hover .vd-bcc__cta i { transform: translateX(3px); }
[dir="rtl"] .vd-bcc--photo:hover .vd-bcc__cta i { transform: scaleX(-1) translateX(3px); }

/* ---- how many photo cards fit ----

   Five across, where the icon card fitted six: the card is now a portrait
   photograph rather than a 42px glyph, so it needs the width. (0,2,0) beats
   the base .vd-mq rules at (0,1,0) wherever they sit in the file, which is why
   every breakpoint is restated here rather than only the ones that differ —
   inheriting the base 6 at desktop is exactly what this is overriding.

   The fractional counts below 992px are deliberate: a clipped last card is
   what says "this scrolls" on a phone, where the arrows are hidden.

   1.8 on a phone, not 2.1. At 2.1 the card came out 172px wide, which is a
   230px card — and 144px of usable title width, three pixels under what
   "Construction Labourer" needs at this type size, so the longest name in the
   row wrapped to two lines and pushed the family label down onto the figure's
   hard hat. 1.8 gives a 208px card, the name fits on one line, and the figure
   gets back the 47px of height it lost. */
.uae-bluecollar-section .vd-mq { --vd-mq-per: 5; }
@media (max-width: 1199.98px) { .uae-bluecollar-section .vd-mq { --vd-mq-per: 4; } }
@media (max-width: 991.98px)  { .uae-bluecollar-section .vd-mq { --vd-mq-per: 3.2; } }
@media (max-width: 767.98px)  { .uae-bluecollar-section .vd-mq { --vd-mq-per: 1.8; } }

@media (prefers-reduced-motion: reduce) {
    .vd-bcc__photo,
    .vd-bcc__cta i { transition: none; }
    .vd-bcc--photo:hover .vd-bcc__photo,
    .vd-bcc--photo:focus-visible .vd-bcc__photo { transform: none; }
    /* The underline still appears; only the arrow's slide is dropped. The
       RTL mirror is a static transform, not motion, so it must survive. */
    .vd-bcc--photo:hover .vd-bcc__cta i { transform: none; }
    [dir="rtl"] .vd-bcc--photo:hover .vd-bcc__cta i { transform: scaleX(-1); }
}

/* ---------------------------------------------------------------------------
   Hub card photos and the marquee  (.vd-mq / .tile--photo, 2026-10-30)

   "Popular job markets" is a single row of photo cards that drifts on its own,
   stops when you point at it, and carries two small arrows on desktop. The art
   is commissioned PORTRAIT (600x1000) and the card shows it whole at its own
   proportions -- scripts/hub_card_images.php resizes and never crops.

   .tile itself is NOT changed, because .tile-grid has a second user -- the
   industries section directly below -- and restyling the base class would drag
   that section along with it. Everything here is .vd-mq, .tile--photo or
   .uae-hubs-section scoped. The hubs section no longer uses .tile-grid at all.

   WHY THE CAPTION SURVIVES NIGHT MODE WITH NO GENERATED RULES, which is the
   part to understand before editing any colour here:

   - The scrim is rgba(var(--vd-scrim-rgb), a), defaulting to the brand green.
     scripts/dark-theme-manual.css pins it to the DAY green at night; the note
     there explains why a scrim is neither a surface nor a label.
   - The caption text is a literal #fff, safe on purpose rather than by luck:
     build_dark_theme.php's mapText() returns null above 0.5 luminance -- its
     own comment says "white labels on primary fills must stay white" -- so the
     generator leaves it alone. Do not "fix" it to a token: --uae-surface is
     white by day and #19202a at night, which would turn the label black on a
     green fill.
   - A var() carries no hex, so the gradient gives the generator nothing to map.
   --------------------------------------------------------------------------- */

.vd-mq { position: relative; --vd-mq-gap: 12px; --vd-mq-per: 6; }

/* The scroll container. overflow-x works with no JavaScript at all, so the row
   is swipeable before vd-marquee.js has loaded or if it never does -- the same
   additive contract vd-search.js follows. The script adds the drift, the clones,
   the arrows and the card width on top of a row that already works. */
.vd-mq__vp {
    overflow-x: auto;
    overscroll-behavior-x: contain;
    -webkit-overflow-scrolling: touch;
    scrollbar-width: none;
}
.vd-mq__vp::-webkit-scrollbar { display: none; }

.vd-mq__track {
    display: flex;
    gap: var(--vd-mq-gap);
    inline-size: max-content;
    /* The cards carry a hairline and a shadow; without this the row clips them
       against the scroll box. */
    padding-block: 2px;
}

/* --vd-mq-w is MEASURED AND WRITTEN BY vd-marquee.js, not computed in CSS.
   It was `calc((100cqi - ...) / var(--vd-mq-per))` with container-type on the
   viewport, which is the tidier thing to write.

   VERIFIED: the container-query form resolves correctly on first layout (card
   211px against an expected 211px at a 1326px container).
   NOT VERIFIED: whether it then follows a container RESIZE. The track is
   `inline-size: max-content`, so its width comes from its children, whose width
   would come from the container, and an engine is entitled to break that cycle
   by resolving 100cqi once. Measurements that appeared to show exactly that
   were taken in a throttled browser -- an unfocused tab stops delivering
   ResizeObserver notifications and nearly stops requestAnimationFrame, which
   also produced several other false readings -- so treat it as an open
   question, not as a finding.

   The JS form is kept because it is explicit and directly testable either way,
   not because the CSS one is known to be broken, and it IS verified: in a
   focused window it follows the container through 600 / 900 / 1100 / 700 /
   1248px, in both directions, landing on the expected width every time. If you
   revisit the CSS form, measure it in a FOCUSED window -- a throttled one will
   lie to you in both directions.

   190px is the no-JS fallback: the same column floor .tile-grid used, so the
   row degrades to roughly what this section looked like before. */
.vd-mq__track > * { flex: 0 0 var(--vd-mq-w, 190px); }

/* Arrows. Rendered with [hidden] and unhidden by the script, so a page with no
   JavaScript never shows a control that cannot do anything. */
.vd-mq__nav {
    position: absolute;
    inset-block-start: 50%;
    z-index: 2;
    display: grid;
    place-items: center;
    inline-size: 34px;
    block-size: 34px;
    padding: 0;
    transform: translateY(-50%);
    border: var(--card-border);
    border-radius: var(--r-pill);
    background: var(--uae-surface);
    box-shadow: var(--shadow-pop);
    color: var(--uae-ink);
    font-size: 13px;
    cursor: pointer;
    transition: border-color .18s ease, color .18s ease;
}
.vd-mq__nav:hover { border-color: var(--uae-primary); color: var(--uae-primary-ink); }
.vd-mq__nav:focus-visible { outline: 2px solid var(--uae-primary); outline-offset: 2px; }
.vd-mq__nav--prev { inset-inline-start: -8px; }
.vd-mq__nav--next { inset-inline-end: -8px; }
/* The chevrons must point outward in both directions, so the pair is mirrored
   from the inline axis rather than each glyph being hardcoded. */
[dir="rtl"] .vd-mq__nav i { transform: scaleX(-1); }

/* ---- the card ---- */

.tile--photo {
    position: relative;
    padding: 0;
    overflow: hidden;
    /* The caption is absolutely positioned, so the image is the only thing in
       flow and the card takes its height. isolation keeps the scrim's stacking
       context inside the card. */
    isolation: isolate;
}

.tile__img {
    display: block;
    inline-size: 100%;
    block-size: auto;
    aspect-ratio: 3 / 5;
    object-fit: contain;
    /* Also the band while a lazy image is still arriving, so the card does not
       flash white inside its own hairline. */
    background: var(--uae-sand);
    transition: transform .45s cubic-bezier(.22, .61, .36, 1);
}

/* The hover move, deliberately small: the photograph creeps in and the scrim
   grows a little taller so the caption gains air. No lift -- translateY on
   hover was removed site-wide in the Palette A pass, and bringing it back on
   one section would reintroduce the inconsistency that removal fixed.

   The IMAGE scales, not the card, so nothing reflows and the row cannot jitter
   while it is drifting. */
.tile--photo:hover .tile__img,
.tile--photo:focus-visible .tile__img { transform: scale(1.055); }
.tile--photo:focus-visible { outline: 2px solid var(--uae-primary); outline-offset: 2px; }

/* The caption, over the foot of the photo.

   THE FADE IS MEASURED IN PIXELS FROM THE TOP, NOT IN PERCENTAGES, and that is
   the one thing to preserve here. Percentage stops are relative to the caption
   box, which GROWS when a title wraps -- so a hold at "the lower 58%" is a
   different absolute height on a one-line card than on a three-line one, while
   padding-block-start stays fixed. Measured against the real photographs, that
   put the first line of "Hospitals & Healthcare Providers" at alpha 0.70 over a
   bright hospital interior: 3.5:1, a fail, while every one-line card passed.

   calc(100% - 34px) instead pins the fade to the top padding, the only part of
   the box no text can occupy whatever the line count. Everything from the text
   down is held at 0.94 or above -- the floor that keeps white at 4.5:1 even
   against a pure white photograph (measured over the real art: 5.08:1 at 0.88,
   4.27:1 at 0.80). Verified at 5.81:1 for one, two and three line titles.

   The hover state grows padding-block-start to 52px, which moves the fade's
   start with it and leaves the text in the same held band. Do not animate the
   gradient stops instead; that is what would break the floor. */
.tile__cap {
    position: absolute;
    inset-inline: 0;
    inset-block-end: 0;
    padding: 38px 12px 12px;
    /* Indirected through a token of its own so the night value is ONE line in
       scripts/dark-theme-manual.css instead of a second copy of the gradient. */
    --vd-scrim-rgb: var(--uae-primary-rgb);
    background: linear-gradient(
        to top,
        rgba(var(--vd-scrim-rgb), .96) 0,
        rgba(var(--vd-scrim-rgb), .94) calc(100% - 34px),
        rgba(var(--vd-scrim-rgb), 0) 100%
    );
    color: #fff;
    transition: padding-block-start .45s cubic-bezier(.22, .61, .36, 1);
}
.tile--photo:hover .tile__cap,
.tile--photo:focus-visible .tile__cap { padding-block-start: 52px; }

/* (0,2,1) so these beat the .tile h3 / .tile p rules above, which set the muted
   colour and the old margins. Colour is inherited from .tile__cap.

   THE TYPE SCALES WITH THE CARD, not with the viewport. --vd-mq-w is the card
   width in px, so one expression covers every breakpoint and any per-view count
   somebody sets later: a 14px label that is right on a 198px desktop card is
   lost on a 230px phone card, and tying it to vw would miss that the same
   viewport holds different card sizes at different breakpoints. The clamp ends
   hold it readable if --vd-mq-w is ever unset (no JS) or extreme. */
.tile__cap h3 {
    margin: 0;
    font-size: clamp(14px, calc(var(--vd-mq-w, 190px) * .072), 20px);
    font-weight: 600;
    line-height: 1.3;
    color: inherit;
}
.tile__cap p {
    margin: 3px 0 0;
    font-size: clamp(12px, calc(var(--vd-mq-w, 190px) * .058), 15px);
    color: inherit;
    opacity: .85;
}

/* The fallback for a hub with no photo: the hub's Font Awesome glyph on the
   wash .tile__ico used to use, at the same 3:5 geometry so the row stays even. */
.tile__img--icon {
    display: grid;
    place-items: center;
    background: var(--uae-primary-wash);
    color: var(--uae-primary-ink);
    font-size: 40px;
}

/* ...and its caption is NOT the white-on-green treatment, because there is no
   photograph under it -- white on the pale primary wash is unreadable. Dark
   text on the surface, the way the card read before the photos landed. */
.tile--noimg .tile__cap { background: var(--uae-surface); padding-block-start: 12px; }
.tile--noimg:hover .tile__cap,
.tile--noimg:focus-visible .tile__cap { padding-block-start: 12px; }
.tile--noimg .tile__cap h3 { color: var(--uae-ink); }
.tile--noimg .tile__cap p { color: var(--uae-muted); opacity: 1; }

/* ---- how many fit, and how far the row reaches ---- */

@media (max-width: 1199.98px) { .vd-mq { --vd-mq-per: 5; } }
@media (max-width: 991.98px)  { .vd-mq { --vd-mq-per: 4; } }
@media (max-width: 767.98px)  { .vd-mq { --vd-mq-per: 2.4; } }

/* The hubs row carries 3:5 PHOTOGRAPHS, so fewer fit comfortably than the
   defaults above, which are sized for a small card like the trade tile. The
   section states its own counts rather than the base class carrying one
   section's needs for everybody: (0,2,0) beats (0,1,0), so this wins wherever
   it sits in the file. */
@media (max-width: 991.98px) { .uae-hubs-section .vd-mq { --vd-mq-per: 3.2; } }
@media (max-width: 767.98px) { .uae-hubs-section .vd-mq { --vd-mq-per: 1.6; } }

/* EDGE TO EDGE BELOW THE DESKTOP BREAKPOINT.

   The row is inside .container, which insets it by 32px at 375px (a 20px outer
   offset plus 12px of container padding). That gutter is right for a block of
   prose and wrong for a carousel: on a phone it reads as a boxed widget rather
   than the app-style rail this is meant to be, and it costs 64px of the 375 a
   card could be using.

   --vd-mq-bleed is MEASURED by vd-marquee.js (the distance from the viewport
   edge to the container content box) rather than hardcoded here, so it cannot
   drift from whatever the container padding becomes, and it follows a resize
   with everything else. It is written unconditionally; this media query is what
   decides to spend it, which is why desktop is unaffected without the script
   needing to know about breakpoints.

   No vw units on purpose -- 100vw includes the scrollbar on a desktop browser
   at tablet width and would overflow the page by its width.

   Opt-in, via .vd-mq--bleed on the wrapper, rather than named after a section:
   two rows use the marquee now and a third would otherwise mean a third
   selector here. */
@media (max-width: 991.98px) {
    .vd-mq--bleed { margin-inline: calc(-1 * var(--vd-mq-bleed, 0px)); }

    /* The arrows sit at -8px, which hangs them in the container gutter. Once
       the row is bled to the screen there IS no gutter, so that -8px put them
       OFF the screen -- measured at 768px: prev at x=-8, next ending at 768
       against a 760px layout width. Inside the edge instead, overlapping the
       end cards the way a carousel normally does. */
    .vd-mq--bleed .vd-mq__nav--prev { inset-inline-start: 8px; }
    .vd-mq--bleed .vd-mq__nav--next { inset-inline-end: 8px; }
}

/* No arrows on a phone -- the row is swiped, and a 34px control sits over a
   good part of the card at that size. The fractional per-view counts above are
   the other half of this: a clipped last card is what says "this scrolls"
   when there is no scrollbar and no arrows to say it. */
@media (max-width: 767.98px) {
    .vd-mq__nav { display: none; }
}

/* ---- motion ---- */

/* The drift itself is stopped in JavaScript when this matches; these are the
   decorative transitions, which have no business running either. */
@media (prefers-reduced-motion: reduce) {
    .tile__img,
    .tile__cap,
    .vd-mq__nav { transition: none; }
    .tile--photo:hover .tile__img,
    .tile--photo:focus-visible .tile__img { transform: none; }
    .tile--photo:hover .tile__cap,
    .tile--photo:focus-visible .tile__cap { padding-block-start: 38px; }
}

/* Section headings on small screens  (2026-10-30)

   main.css:277 sets `h2, .h2 { font-size: 30px }` and nothing scales it down,
   so every section title is 30px on a 375px phone -- 8% of the screen width,
   against the 14px body text under it. On the hubs section that pushed the
   title onto two lines and ate a third of the first screenful before any
   content.

   Scoped to .section-head h2 rather than fixing the global rule: that one is
   (0,0,1) and reaches article bodies, page titles and the admin panel, none of
   which were measured here. This is the section-header ROLE, used the same way
   by 20 views (29 instances, measured), so they all improve together and none
   of them disagree with each other afterwards. .section-header and
   .kb-section-head are DIFFERENT classes and are untouched; a substring grep
   conflates all three. Specificity is (0,1,1) and this file loads after
   main.css, so it wins without !important.

   The clamp reaches 30px at about 484px wide, so tablets and desktop are
   untouched and only phones change. */
.section-head h2 { font-size: clamp(23px, 6.2vw, 30px); line-height: 1.25; }

/* ===================================================================
   "Before you accept a job" — the recruitment-fee warning (2026-11-01)

   One strip above the job list on a role page; the markup and the
   reasoning for its placement are in
   resources/views/job/partials/kb_fee_notice.blade.php.

   NOT red. Palette A keeps red for errors so it never sits beside the
   green success state, and this is something a visitor acts on rather
   than a mistake they made — so it is the primary wash with a leading
   rule, the same treatment the walk-in module's trust lines use.

   No literal colour in this block, which is the whole reason it needs
   nothing from scripts/build_dark_theme.php: every value resolves
   through a --uae-* token that already has a night value. Verified by
   re-running the generator — vd-theme-dark.css came out byte-identical.
   Measured on a fresh load of /en/uae/roles/chef-jobs, light then
   dark: title 15.44 / 13.40, body 10.94 / 11.09, links and icon 5.83
   / 5.71, and the leading rule 3.09 against its own wash at night.

   MEASURE AFTER A RELOAD, not after flipping data-theme in the
   console. Doing the latter reported the link at 2.37:1 — the pane
   serves a stale computed colour for some declarations while the
   token itself already reads dark, the same artefact the marquee's
   flex-basis showed on 2026-11-01. Reloading with the theme already
   set gave 5.71 and nothing in the CSS had to change.

   Logical properties throughout: rtl-style.css knows nothing about
   these class names and does not need to. The arrow is the one thing
   that cannot flip on its own.
   =================================================================== */
.vd-fee {
    display: flex;
    align-items: flex-start;
    gap: 14px;
    margin-block-end: 28px;
    padding: 16px 18px;
    border: 1px solid var(--uae-line);
    border-inline-start: 3px solid var(--uae-primary);
    border-radius: var(--r-card);
    background: var(--uae-primary-wash);
}

.vd-fee__ico {
    flex: 0 0 auto;
    margin-block-start: 3px;
    font-size: 20px;
    color: var(--uae-primary-ink);
}

.vd-fee__title {
    margin: 0 0 5px;
    font-size: 16px;
    font-weight: 700;
    color: var(--uae-ink);
}

.vd-fee__text {
    margin: 0;
    font-size: 14px;
    line-height: 1.6;
    color: var(--uae-body);
}

/* A row on desktop, a column on a phone: two links of this length wrap
   into four ragged lines at 375px, which reads as four links. */
.vd-fee__links {
    display: flex;
    flex-wrap: wrap;
    gap: 6px 22px;
    margin: 10px 0 0;
}

.vd-fee__links a {
    font-size: 14px;
    font-weight: 600;
    color: var(--uae-primary-ink);
}

.vd-fee__links i {
    margin-inline-start: 5px;
    font-size: .8em;
}

/* inline-block so the mirror has a box to act on — transform does
   nothing to an inline element. */
[dir="rtl"] .vd-fee__links i {
    display: inline-block;
    transform: scaleX(-1);
}

@media (max-width: 575.98px) {
    .vd-fee {
        gap: 11px;
        padding: 14px;
    }

    .vd-fee__ico { font-size: 17px; }
    .vd-fee__title { font-size: 15px; }

    .vd-fee__links {
        flex-direction: column;
        gap: 7px;
    }
}

/* ---------------------------------------------------------------------------
   .vd-walkin — "Walk-in interviews hiring <trade> now", on a role page.
   resources/views/job/partials/walkin_link.blade.php, step 2 of
   documentation/2026-11-01-ROLE-PAGE-BLUE-COLLAR-PLAN.md.

   Sits directly above .vd-fee, so the two are deliberately different shapes:
   this one is a tappable CARD with a border and a chevron, that one is a
   borderless wash. A reader scanning the page has to be able to tell the
   opportunity from the warning without reading either.

   NO LITERAL COLOUR, same contract as .vd-fee. scripts/build_dark_theme.php
   maps literals only, so a token-only block needs no regeneration and no
   entry in dark-theme-manual.css — verified, the generated sheet came out
   byte-identical after this landed.

   Not gold: gold is Featured/Premium in Palette A. Not red: red is errors.
   Primary is the fill-safe token in both themes (6.61:1 by day, 5.18:1 at
   night on its own wash).

   Measured on the live page, both themes, after a RELOAD in each — flipping
   data-theme in the console reports stale computed colours on this pane and
   cost a false 2.37:1 reading on .vd-fee the day before.
   Light: title 15.44:1, meta 6.00:1, icon and chevron 5.83:1.
   Dark:  title 13.40:1, meta 7.07:1, icon and chevron 5.71:1.
--------------------------------------------------------------------------- */

.vd-walkin {
    display: flex;
    align-items: center;
    gap: 14px;
    padding: 15px 18px;
    margin-block-end: 16px;
    border: 1px solid var(--uae-line);
    border-inline-start: 3px solid var(--uae-primary);
    border-radius: var(--r-card);
    background: var(--uae-surface);
    text-decoration: none;
    transition: border-color .15s ease, background-color .15s ease;
}

/* Border change, not a lift: translateY on hover was removed site-wide in
   the Palette A decoration pass. */
.vd-walkin:hover,
.vd-walkin:focus-visible {
    border-color: var(--uae-primary);
    background: var(--uae-primary-wash);
    text-decoration: none;
}

.vd-walkin__ico {
    flex: none;
    font-size: 20px;
    color: var(--uae-primary-ink);
}

.vd-walkin__body {
    flex: 1 1 auto;
    min-width: 0;
}

.vd-walkin__title {
    display: block;
    font-size: 16px;
    font-weight: 600;
    line-height: 1.35;
    color: var(--uae-ink);
}

.vd-walkin__meta {
    display: block;
    margin-block-start: 3px;
    font-size: 13.5px;
    line-height: 1.45;
    color: var(--uae-muted);
}

.vd-walkin__go {
    flex: none;
    font-size: 13px;
    color: var(--uae-primary-ink);
}

/* inline-block so the mirror has a box to act on — transform does
   nothing to an inline element. */
[dir="rtl"] .vd-walkin__go {
    display: inline-block;
    transform: scaleX(-1);
}

@media (max-width: 575.98px) {
    .vd-walkin {
        gap: 11px;
        padding: 13px 14px;
    }

    .vd-walkin__ico { font-size: 18px; }
    .vd-walkin__title { font-size: 15px; }
    .vd-walkin__meta { font-size: 13px; }

    /* The chevron is decoration and the whole card is the target, so it is
       the first thing to go when the title needs the room. */
    .vd-walkin__go { display: none; }
}

/* ---------------------------------------------------------------------------
   Job detail: the job's own browse links (2026-11-04)

   Rendered by job/detail.blade.php from JobController@jobBrowseLinks. Token-only
   by design, exactly like vd-search.css: build_dark_theme.php maps the LITERAL
   colours in this sheet to dark counterparts, so a rule that states no literal
   needs no counterpart and night mode works with no regeneration. Do not write
   a hex here.

   --uae-primary-ink, not --uae-primary, for the link text -- see the night-mode
   notes in CLAUDE.md: the fill token measures ~3.1:1 as text on a dark surface.
   --------------------------------------------------------------------------- */
.jd-browse {
    margin-block-start: 18px;
}

.jd-browse h3 {
    margin: 0 0 12px;
    font-size: 1rem;
}

.jd-browse__list {
    display: flex;
    flex-wrap: wrap;
    gap: 8px;
    margin: 0;
    padding: 0;
    list-style: none;
}

.jd-browse__pill {
    display: inline-block;
    padding: 7px 14px;
    border: 1px solid var(--uae-line);
    border-radius: var(--r-pill);
    background: var(--uae-sand);
    color: var(--uae-primary-ink);
    font-size: .875rem;
    line-height: 1.35;
    text-decoration: none;
}

.jd-browse__pill:hover,
.jd-browse__pill:focus-visible {
    border-color: var(--uae-primary);
    background: var(--uae-primary-wash);
    text-decoration: none;
}

/* ------------------------------------------------------------------
   WhatsApp CTA (2026-11-12) — includes/whatsapp_cta.blade.php, on every
   walk-in page and every job page.

   Tokens only, no literal colour. This file is one of the four
   build_dark_theme.php generates the night layer from, so a hex here would
   need that script re-run before it looked right after dark; a token is
   already themed in both. That is why this is NOT WhatsApp's own #25D366 --
   the brand green has no dark counterpart and is outside Palette A. The
   glyph is what carries the recognition.
   ------------------------------------------------------------------ */
.vd-wa {
    display: flex;
    align-items: flex-start;
    gap: 12px;
    padding: 16px;
    border: 1px solid var(--uae-line);
    border-radius: var(--r-card);
    background: var(--uae-surface);
}
.vd-wa__ico {
    display: grid;
    flex: 0 0 auto;
    place-items: center;
    width: 38px;
    height: 38px;
    border-radius: var(--r-pill);
    background: var(--uae-primary-wash);
    color: var(--uae-primary-ink);
    font-size: 20px;
}
.vd-wa__body { min-width: 0; }
.vd-wa__title { margin: 2px 0 4px; color: var(--uae-ink); font-size: 15px; line-height: 1.3; }
.vd-wa__line { margin: 0 0 11px; color: var(--uae-muted); font-size: 13px; line-height: 1.45; }
/* wrap, not a grid: the two buttons sit side by side in a 360px sidebar and
   stack by themselves in a narrower one, in either direction */
.vd-wa__acts { display: flex; flex-wrap: wrap; gap: 8px; margin: 0; }
.vd-wa__btn {
    display: inline-flex;
    /* grow and share the row: side by side they come out equal halves, and
       when the rail is too narrow for both each fills its own row instead of
       leaving a ragged left-aligned stack */
    flex: 1 1 140px;
    align-items: center;
    justify-content: center;
    gap: 7px;
    padding: 9px 14px;
    border: 1px solid var(--uae-primary);
    border-radius: var(--r-control);
    background: var(--uae-primary);
    color: #fff;
    font-size: 13px;
    font-weight: 700;
    text-decoration: none;
    transition: background-color .15s ease, border-color .15s ease, color .15s ease;
}
.vd-wa__btn:hover, .vd-wa__btn:focus-visible { background: var(--uae-primary-deep); border-color: var(--uae-primary-deep); color: #fff; text-decoration: none; }
/* The group is the secondary ask: joining one exposes your number to every
   other member, so it does not get the button that looks like the default. */
.vd-wa__btn--ghost { background: transparent; border-color: var(--uae-line); color: var(--uae-primary-ink); }
.vd-wa__btn--ghost:hover, .vd-wa__btn--ghost:focus-visible { background: var(--uae-primary-wash); border-color: var(--uae-primary); color: var(--uae-primary-ink); }
/* Full-width column (the guide page): the card has the room to breathe. */
.vd-wa--wide { padding: 20px 22px; }
.vd-wa--wide .vd-wa__ico { width: 44px; height: 44px; font-size: 23px; }
.vd-wa--wide .vd-wa__title { font-size: 17px; }
.vd-wa--wide .vd-wa__line { font-size: 14px; }

/* The end-of-content band (2026-11-12): the knowledgebase pages and the five
   browse pages carry the card above the footer. Capped and centred rather
   than stretched: .container runs to 1350px here and a 1350px card with a
   44px disc at one end and two 140px buttons at the other is a rule with
   writing on it, not a card. 720px is the width the card was designed at on
   the walk-in guide page. */
.vd-wa-band { padding-block: 4px 44px; }
.vd-wa-band .vd-wa { max-width: 720px; margin-inline: auto; }

/* The footer column (2026-11-12). NOT the card: this is one of five columns
   in the footer row, so it has to read as a sibling of Quick Links rather
   than as a panel dropped among them. No box, no icon disc, and the heading
   is an <h5> that inherits .footerWrap h5 -- the 12px uppercase treatment is
   stated once, there, and this variant only adds the glyph beside it.

   The footer band is dark in BOTH themes (it is painted with
   --uae-ink-surface), so this variant must not use a token that flips at
   night or the light theme gets night’s colours. That is the same trap the
   --uae-ink / --uae-ink-surface split exists for; see the night-mode notes.

   Hence rgba literals rather than hexes or tokens for every surface and every
   piece of text here: vd-components.css is one of the four sheets
   build_dark_theme.php reads, and it maps HEX literals by property -- a
   `color: #fff` would be darkened for night and vanish on a footer that was
   dark to begin with. rgba() is not a hex and is left alone, which is why
   `.footerWrap .social a` is written the same way.

   --uae-primary stays on the filled button: it is a FILL and its white label
   is 6.61:1 on it by day and 5.06:1 at night, so the one button that has to
   look like the primary action keeps the brand green on a dark band. */
.vd-wa--onfoot {
    display: block;
    padding: 0;
    border: 0;
    background: none;
    box-shadow: none;
}
/* Only the glyph and the layout. Size, weight, colour, letter-spacing and the
   18px below it come from .footerWrap h5, which is what keeps this heading on
   the same baseline as the three columns beside it. */
.vd-wa--onfoot .vd-wa__title {
    display: flex;
    align-items: center;
    gap: 7px;
}
.vd-wa--onfoot .vd-wa__title i { font-size: 14px; opacity: .85; }
.vd-wa--onfoot .vd-wa__line {
    margin-bottom: 14px;
    color: rgba(255, 255, 255, .72);
    font-size: 13px;
}
/* Stacked, full width, in column order. The base rule’s flex:1 1 140px would
   do this by itself at these widths -- two 140px buttons plus the gap need
   287px and the column has 160-229 -- but stating 100% means the pair cannot
   come out side by side and ragged if the grid is ever widened. */
.vd-wa--onfoot .vd-wa__acts { gap: 8px; }
.vd-wa--onfoot .vd-wa__btn {
    flex: 1 1 100%;
    padding: 8px 14px;
    font-size: 12.5px;
}
.vd-wa--onfoot .vd-wa__btn--ghost { border-color: rgba(255, 255, 255, .26); color: rgba(255, 255, 255, .92); }
.vd-wa--onfoot .vd-wa__btn--ghost:hover,
.vd-wa--onfoot .vd-wa__btn--ghost:focus-visible { border-color: rgba(255, 255, 255, .5); background: rgba(255, 255, 255, .08); color: rgba(255, 255, 255, .96); }
/* At md the column runs full width under the other four, so the two buttons
   have room to sit side by side; they should not stretch to half the footer. */
@media (min-width: 768px) and (max-width: 991.98px) {
    .vd-wa--onfoot .vd-wa__btn { flex: 0 0 auto; }
}

/* ---------------------------------------------------------------------------
   The early WhatsApp card (2026-11-12)

   The rail placement is correct on desktop and useless on a phone: the rail
   stacks AFTER the article, so on live the card measured 4.6 screens down on
   a category page and 20.0 on a guide. kb/_wa_early.blade.php renders a
   second copy just under the intro, and these rules show exactly ONE per
   width. There is never a second visible card.

   NO HEX IN HERE. vd-components.css is one of the four sheets
   build_dark_theme.php reads and it maps hex by property; every colour below
   is a token, which is already themed in both. The card sits on the light
   body - never inside .taxonomy-landing__hero, which is --uae-ink-surface
   and dark in both themes - so the base .vd-wa light styling is right.

   The display toggle lives on the WRAPPER (.vd-wa-early) for a main-level
   caller and on .vd-wa--early-bare for one inside an <article>. It must NOT
   live on .vd-wa--early itself: that class is on the card in both shapes, so
   a display:none there would also blank the card inside a --all wrapper,
   which is the no-rail page's only in-page card.
   --------------------------------------------------------------------------- */
.vd-wa-early { display: none; margin-block: 26px 0; }
.vd-wa-early > .container > .vd-wa { max-width: 720px; margin-inline: auto; }
.vd-wa--early-bare { display: none; margin-block: 20px 26px; }

/* A page with NO rail shows it at every width, because it replaced that
   page's end-of-content band - which was rendering 25px above the identical
   footer column at desktop. */
.vd-wa-early--all { display: block; }
.vd-wa--early-bare.vd-wa--early-all { display: flex; }

@media (max-width: 991.98px) {
    .vd-wa-early { display: block; }
    .vd-wa--early-bare { display: flex; }

    /* Hide the rail copy ONLY on a page that actually carries an early card.
       An unscoped `.kb-side .vd-wa { display: none }` would strip the mobile
       CTA from the four tool pages and the other rail views that have not
       been given one, leaving them with nothing but the footer column. The
       :has() keeps the two in step; where it is unsupported the rule drops
       and both show, thousands of px apart, which is the old behaviour. */
    main:has(.vd-wa--early) .kb-side .vd-wa:not(.vd-wa--early),
    main:has(.vd-wa--early) .kb-hub__side .vd-wa:not(.vd-wa--early) { display: none; }
}

/* ---- THE SORT CONTROL (2026-11-13) ---------------------------------------
   See resources/views/includes/vd_sort.blade.php and public/js/vd-sort.js.

   Three things this file cannot do differently:

   - NO HEX. vd-components.css is one of the four sheets build_dark_theme.php
     reads, and the generator maps a hex literal by the property it sits on.
     Tokens and rgba() are already right in both themes, so night mode needs
     no rebuild of the generated sheet.
   - Logical properties throughout. rtl-style.css predates every vd-* class
     and knows nothing about these, so the control has to flip on dir alone.
   - `html.vd-sortjs` gates the swap. Without the script the native select is
     what shows, which is a working control and not a broken-looking one. */

.vd-sort__btn,
.vd-sort__menu { display: none; }

html.vd-sortjs .vd-sort__native { display: none; }
html.vd-sortjs .vd-sort__btn { display: inline-flex; }

.vd-sort { position: relative; }

/* On the job list this control is a flex item in .vd-toolbar__acts, beside
   the Filters button. The <576px rule that makes a standalone .vd-sort stack
   under the heading gives it margin-top: 12px, which pushed it 6px below its
   neighbour - two 40px pills side by side, one of them lower. The employer
   directory has no __acts wrapper and still wants that stacking margin. */
.vd-toolbar__acts .vd-sort { margin-top: 0; }

.vd-sort__btn {
    align-items: center;
    gap: 8px;
    height: 40px;
    max-width: 100%;
    padding-inline: 14px;
    border: 1px solid var(--uae-line);
    border-radius: var(--r-pill);
    background: var(--uae-surface);
    color: var(--uae-ink);
    font-size: 14px;
    font-weight: var(--weight-strong);
    line-height: 1;
    cursor: pointer;
    transition: border-color .15s ease, background-color .15s ease;
}
.vd-sort__btn:hover { border-color: var(--uae-primary); }
.vd-sort__btn:focus-visible { outline: 2px solid var(--uae-primary); outline-offset: 2px; }

/* The value can be a long translated string in a narrow toolbar; it is the
   only part allowed to give way, so the two icons never get squeezed off. */
.vd-sort__value { overflow: hidden; text-overflow: ellipsis; white-space: nowrap; }

.vd-sort__btn-ico { flex: 0 0 auto; font-size: 13px; color: var(--uae-primary-ink); }
.vd-sort__chev {
    flex: 0 0 auto;
    font-size: 11px;
    color: var(--uae-muted);
    transition: transform .15s ease;
}
.vd-sort.is-open .vd-sort__btn { border-color: var(--uae-primary); }
.vd-sort.is-open .vd-sort__chev { transform: rotate(180deg); }

.vd-sort__menu {
    position: absolute;
    z-index: 20;                 /* the sticky toolbar is 8 */
    inset-inline-end: 0;
    top: calc(100% + 6px);
    min-width: 232px;
    padding: 6px;
    border: 1px solid var(--uae-line);
    border-radius: var(--r-card);
    background: var(--uae-surface);
    box-shadow: var(--shadow-pop);
}
html.vd-sortjs .vd-sort__menu:not([hidden]) { display: block; }

.vd-sort__opt {
    display: flex;
    align-items: center;
    gap: 10px;
    width: 100%;
    padding: 9px 10px;
    border: 0;
    border-radius: var(--r-control);
    background: none;
    color: var(--uae-body);
    font-size: 14px;
    text-align: start;
    cursor: pointer;
}
.vd-sort__opt:hover { background: var(--uae-sand); }
.vd-sort__opt:focus-visible { outline: 2px solid var(--uae-primary); outline-offset: -2px; }
.vd-sort__opt.is-on { background: var(--uae-primary-wash); color: var(--uae-ink); font-weight: var(--weight-strong); }

/* 16px of fixed gutter, so the four labels start on one vertical line
   however wide each glyph draws. */
.vd-sort__opt-ico { flex: 0 0 16px; font-size: 13px; text-align: center; color: var(--uae-muted); }
.vd-sort__opt.is-on .vd-sort__opt-ico { color: var(--uae-primary-ink); }
.vd-sort__opt-text { flex: 1 1 auto; }
.vd-sort__tick { flex: 0 0 auto; font-size: 11px; color: var(--uae-primary-ink); visibility: hidden; }
.vd-sort__opt.is-on .vd-sort__tick { visibility: visible; }

@media (max-width: 991.98px) {
    /* It stands directly beside the Filters button in .vd-toolbar__acts, so
       it keeps that button's 40px height - measured, not assumed: at 36 the
       two pills sat 4px apart in height and 8px apart at the top, which
       reads as one of them being wrong. Only the padding and the type give
       way, because the toolbar is a sticky one-line row here. */
    .vd-sort__btn { padding-inline: 12px; font-size: 13px; }
    .vd-sort__value { max-width: 124px; }
    .vd-sort__menu { min-width: 210px; }
}
