/* Pitmeadow Farm - site-level design tokens + type scale.
   Values taken from source/DEV/pitmeadow-style-sheet.txt (colours,
   type scale) - see that file's own "NOTES FOR DEVELOPMENT" section
   for caveats not resolved here (marked TODO below). Layered on top
   of simpl-cms's default frontend.css via templates/base.html.twig's
   stylesheets block. */

@font-face {
    font-family: "Rodetta";
    src: url("/fonts/rodetta/rodetta.woff2") format("woff2"),
         url("/fonts/rodetta/rodetta.otf") format("opentype");
    font-weight: 400;
    font-style: normal;
    font-display: swap;
}

@font-face {
    font-family: "Rodetta Stamp";
    src: url("/fonts/rodetta/rodetta-stamp.woff2") format("woff2"),
         url("/fonts/rodetta/rodetta-stamp.otf") format("opentype");
    font-weight: 400;
    font-style: normal;
    font-display: swap;
}
/* .woff2 converted 2026-09-03 via a throwaway fontTools+brotli venv
   (rodetta.otf 352KB -> 85KB, rodetta-stamp.otf 5.2MB -> 1.16MB - the
   Stamp face is used for every heading/nav item sitewide, so this is a
   real page-weight win). .otf kept as the fallback src for any browser
   without woff2 support - harmless, never actually requested by a
   modern browser given format() hinting. */

:root {
    /* Core */
    --colour-heading: #253117;  /* forest green */
    --colour-brand: #AFA067;    /* gold / khaki - primary buttons & accents */
    --colour-body-text: #000000;
    --colour-white: #FFFFFF;

    /* Backgrounds */
    --bg-cream: #FAF4DC;
    --bg-off-white: #F4F3EE;
    --bg-pale-pink: #FAE9E1;

    /* Accents */
    --accent-amber: #F0AD4F;
    --accent-olive: #524923;
    --accent-slate-blue: #38486A;
    /* Confirmed final (not wireframe placeholders) 2026-09-02 - used on
       the Events "This month/Next month" filter pills and the Farm
       Safety anchor-link pills. */
    --accent-light-blue: #ADCCFF;
    --accent-pink: #FFBBBB;

    /* Neutrals */
    --grey-mid: #888889;
    --grey-warm: #A9A2A2;
    --grey-light: #D9D9D9;  /* image placeholders */
    --overlay-shadow: rgba(68, 67, 67, 0.30);  /* #444343 @ 30% over photos */

    /* Fonts */
    /* NOTE: the source style sheet's own CSS block sets --font-display
       to "Rodetta", but its descriptive text says headings use the
       "Stamp" style specifically, and the rendered designs show a
       visibly textured/stamped heading face - so this points at
       "Rodetta Stamp" (rodetta-stamp.otf), not plain Rodetta. Plain
       "Rodetta" (rodetta.otf) is loaded above and available as
       --font-display-plain if a non-stamped instance is ever needed. */
    --font-display: "Rodetta Stamp", Georgia, serif;
    --font-display-plain: "Rodetta", Georgia, serif;
    --font-body: "Poppins", system-ui, sans-serif;
}

/* Type scale - desktop */
.h1     { font-family: var(--font-display); font-weight: 400; font-size: 34px; line-height: 1.1; }
.h2     { font-family: var(--font-display); font-weight: 400; font-size: 28px; line-height: 32px; }
.h3     { font-family: var(--font-display); font-weight: 400; font-size: 24px; line-height: 32px; }
.intro  { font-family: var(--font-body); font-weight: 400; font-size: 24px; line-height: 34px; }
.body   { font-family: var(--font-body); font-weight: 400; font-size: 21px; line-height: 30px; }
.button { font-family: var(--font-body); font-weight: 500; font-size: 18px; line-height: 1.1; }
.date   { font-family: var(--font-body); font-weight: 700; font-size: 18px; line-height: 20px; }
/* Resolved 2026-09-04: checked directly against the full design page
   renders (not just the source style sheet's own sampled values) -
   the real header nav is unambiguously Rodetta Stamp, bold uppercase,
   matching this type-scale entry. The real header nav CSS (below,
   #navbarSupportedContent a) sets its own size (16px, not this scale's
   18px) to fit the design's actual proportions - this utility class is
   kept for any other genuinely `.nav`-styled UI text, currently none. */
.nav    { font-family: var(--font-display); font-weight: 400; font-size: 18px; line-height: 1.1; }

/* Type scale - mobile */
@media (max-width: 640px) {
    .h1    { font-size: 34px; line-height: 36px; }
    .intro { font-size: 21px; line-height: 28px; }
    .body  { font-size: 18px; line-height: 25px; }
}

/* Removed on request 2026-09-04 - the paper-grain texture (below) was
   showing through in the small top-margin gap every content item has
   above it, reading as an unwanted background image rather than the
   plain white Tom wants there. Body background is now flat white, no
   image. See [[pitmeadow-farm-content-model]] memory for the fuller
   history - public/img/paper-texture.jpg itself is left in place
   (unused) in case a future design pass wants it back in a more
   targeted spot rather than sitewide. */
body {
    background: var(--colour-white);
}

/* CTA button - CKEditor "button" Style (cc_styles in fos_ckeditor.yaml)
   applies class="btn-pill" to a plain <a>. Styled here to match the
   style sheet's .button type + the brand/gold colour. */
a.btn-pill {
    display: inline-flex;
    align-items: center;
    gap: 0.5em;
    font-family: var(--font-body);
    font-weight: 500;
    font-size: 18px;
    line-height: 1.1;
    color: var(--colour-white);
    background-color: var(--colour-brand);
    border-radius: 999px;
    padding: 0.75em 1.5em;
    text-decoration: none;
}

a.btn-pill:hover {
    background-color: var(--accent-olive);
}

/* Contact form block (tpl_section/content_item/contact_form.html.twig,
   2026-11-14). Same pill button as a.btn-pill, text fields in the site's
   own body font on white. No width, margin or padding of its own (removed
   2026-11-16, on request): like every other content item, those come from
   the block's own "display properties" - the wrapper cc_content.html.twig
   renders around it carries the editor's background/content width,
   padding and margin classes, and the fields below are width:100% so the
   form simply fills whatever width that wrapper gives it. The honeypot is
   moved off-screen rather than display:none - a few scripts skip fields
   hidden that way, none skip one that is merely positioned away. */
.contact-form {
    font-family: var(--font-body);
}

.contact-form__row {
    margin-bottom: 1.25rem;
}

.contact-form label {
    display: block;
    font-weight: 500;
    margin-bottom: 0.35rem;
}

.contact-form__optional {
    font-weight: 400;
    opacity: 0.7;
}

.contact-form input[type="text"],
.contact-form input[type="email"],
.contact-form input[type="tel"],
.contact-form textarea {
    display: block;
    width: 100%;
    box-sizing: border-box;
    font: inherit;
    font-size: 18px;
    padding: 0.7em 0.9em;
    color: inherit;
    background: var(--colour-white);
    border: 1px solid #8a8a8a;
    border-radius: 4px;
}

.contact-form input:focus,
.contact-form textarea:focus {
    outline: 3px solid var(--accent-slate-blue);
    outline-offset: 1px;
}

.contact-form__row.has-error input,
.contact-form__row.has-error textarea {
    border-color: #b3261e;
}

.contact-form__error {
    color: #b3261e;
    margin: 0.35rem 0 0;
    font-size: 0.9em;
}

.contact-form__notice {
    padding: 0.9em 1.1em;
    margin: 0 0 1.5rem;
    border-radius: 4px;
    border-left: 4px solid;
}

.contact-form__notice--ok {
    background: #eef3e2;
    border-color: var(--accent-olive);
}

.contact-form__notice--error {
    background: #fbe9e7;
    border-color: #b3261e;
}

.contact-form__privacy {
    font-size: 0.9em;
    opacity: 0.8;
}

.contact-form__privacy a {
    color: var(--accent-slate-blue);
}

.contact-form__submit {
    font-family: var(--font-body);
    font-weight: 500;
    font-size: 18px;
    line-height: 1.1;
    color: var(--colour-white);
    background-color: var(--colour-brand);
    border: 0;
    border-radius: 999px;
    padding: 0.75em 1.5em;
    cursor: pointer;
}

.contact-form__submit:hover,
.contact-form__submit:focus-visible {
    background-color: var(--accent-olive);
}

.contact-form__hp {
    position: absolute;
    left: -9999px;
    width: 1px;
    height: 1px;
    overflow: hidden;
}

/* Site plan block (tpl_section/content_item/site_plan.html.twig) -
   the auto-generated nested page list. */
.site-plan {
    max-width: 960px;
    margin-inline: auto;
    padding: 2rem 1rem;
    font-family: var(--font-body);
}

.site-plan ul {
    list-style: none;
    margin: 0;
    padding-left: 1.5rem;
}

.site-plan > ul {
    padding-left: 0;
}

.site-plan li {
    margin: 0.4rem 0;
}

.site-plan a {
    color: var(--accent-slate-blue);
}

/* Text block centring removed sitewide on request (2026-09-05) - was
   `.ci-content--text { text-align: center; }`, per Tom's earlier
   2026-09-02 call. Left-aligned is now the default; JustifyCenter in
   the CKEditor toolbar still works as a manual per-paragraph override,
   same as before. */

/* Text block's own readability-width cap (640px, centred) removed on
   request (2026-09-05) - now just fills its parent's own width
   instead, same as every other block type. */
.ci-content--text .ci--text-content {
    max-width: 100%;
}

/* 'Centred narrow text (max 640px)' block class (simpl_cms.yaml's
   ci_block_classes) - a per-block opt-in recreating the look every
   Text block had by default before 2026-09-05 (centred, capped at
   640px wide), for anyone who still wants it on a specific block (e.g.
   the homepage's own "Welcome to Pitmeadow Farm" panel). blockClass
   renders on the outer .cc-content-container (cc_content.html.twig's
   contentrowstart macro), not on .ci--text-content itself, hence the
   descendant selector. */
.cc-content-container.cb-text-narrow-centred .ci--text-content {
    max-width: 640px;
    margin-inline: auto;
    text-align: center;
}

.ci-content--text h1, .ci-content--text h2, .ci-content--text h3 {
    color: var(--colour-heading);
}

/* Headings sitewide use the display font/colour by default - matches
   every h2/h3 seen across the design (section titles, Text_and_image
   titles). */
h1, h2, h3 {
    font-family: var(--font-display);
    font-weight: 400;
    color: var(--colour-heading);
}

/* An image-only Banner block (no body text) has nothing in-flow to give
   it height - the package's own cc_content_item_banner.html.twig sets
   its background-image via a scoped <style> block on .cc-content, but
   that element's height still comes from its children in normal block
   flow, and renders 0px tall with no text at all. Confirmed via a real
   screenshot, not assumed - the hero was genuinely invisible without
   this. */
.ci-content-container--banner {
    min-height: 60vh;
}

/* Sub-entry headings within a long Text block (e.g. Local Info's "The
   Kirkstyle Inn") - the style sheet only ever defined h1-h3, but the
   design shows a genuine third, smaller heading level for these. */
h4 {
    font-family: var(--font-body);
    font-weight: 700;
    font-size: 18px;
    color: var(--accent-olive);
}

/* Farm Safety's 3 anchor jump-links (real <a href="#..."> pills, not a
   JS filter - see [[pitmeadow-farm-content-model]] memory). */
html {
    scroll-behavior: smooth;
}

.pill-nav {
    display: flex;
    justify-content: center;
    gap: 0.75rem;
    flex-wrap: wrap;
}

.pill-link {
    display: inline-block;
    background-color: var(--accent-light-blue);
    color: var(--colour-body-text);
    font-family: var(--font-body);
    font-weight: 500;
    padding: 0.5em 1.25em;
    border-radius: 999px;
    text-decoration: none;
}

.pill-link:hover {
    background-color: var(--accent-slate-blue);
    color: var(--colour-white);
}

/* "What's On" All/This month/Next month filter (public/js/site.js) -
   distinct from .pill-link (Farm Safety's plain anchor jump-links):
   these are stateful buttons, each with its own real colour when
   active/hovered, greyscale otherwise - per Tom's own spec ("inactive
   buttons appear greyscaled, the selected ones appear in the
   corresponding colour, also hover"). */
.filter-pills {
    display: flex;
    justify-content: center;
    gap: 0.75rem;
    flex-wrap: wrap;
    margin-bottom: 2rem;
}

.filter-pill {
    display: inline-block;
    border: none;
    cursor: pointer;
    font-family: var(--font-body);
    font-weight: 500;
    padding: 0.5em 1.25em;
    border-radius: 999px;
    background-color: var(--grey-light);
    color: var(--colour-body-text);
    filter: grayscale(1);
}

.filter-pill[data-filter="all"] { background-color: var(--accent-amber); }
.filter-pill[data-filter="this-month"] { background-color: var(--accent-pink); }
.filter-pill[data-filter="next-month"] { background-color: var(--accent-light-blue); }

.filter-pill:hover,
.filter-pill.is-active {
    filter: none;
}

/* (A 2-column "content left / boxed Notes right" layout for a second
   'sidebar' content zone lived here from 2026-09-05 until 2026-09-30,
   when that zone was removed sitewide - see simpl_cms.yaml's own
   comment. Nothing renders .cc-zone--sidebar any more.) */

/* Collection block heading (What's On / Stay teasers) centring removed
   sitewide on request (2026-09-05) - was `.sh-collection-intro {
   text-align: center; }`. See [[pitmeadow-farm-content-model]] memory
   for the earlier CKEditor-ACF-stripping context this rule was built to
   work around, still relevant if centring is ever wanted back. */

/* Teaser-card grids (Collection blocks) - Event ("What's On") and
   Accommodation ("Stay") both use the same 3-up grid + .teaser-card
   design, not per-type CSS. */
.sh-collection--event,
.sh-collection--accommodation {
    display: grid;
    grid-template-columns: repeat(3, 1fr);
    gap: 1.5rem;
}

@media (max-width: 768px) {
    .sh-collection--event,
    .sh-collection--accommodation {
        grid-template-columns: 1fr;
    }
}

.teaser-card {
    position: relative;
    display: block;
    aspect-ratio: 4 / 3;
    border-radius: 4px;
    overflow: hidden;
    background-color: var(--grey-light);
    color: var(--colour-white);
    text-decoration: none;
}

.teaser-card::after {
    content: "";
    position: absolute;
    inset: 0;
    background: linear-gradient(to top, rgba(68, 67, 67, 0.6), rgba(68, 67, 67, 0) 60%);
    pointer-events: none;
}

.teaser-card__image {
    position: absolute;
    inset: 0;
    width: 100%;
    height: 100%;
    object-fit: cover;
    transition: filter 0.2s ease;
}

/* Real bug found live: hovering an event/accommodation listing card
   turned its title blue, matching a screenshot-confirmed computed-style
   check (rgb(255,255,255) -> rgb(10,88,202), Bootstrap's default
   $link-hover-color) - .teaser-card never set its own hover colour, so
   Bootstrap's global `a:hover{color:...}` won (a:hover's specificity,
   one type + one pseudo-class, still beats .teaser-card's own base
   `color` declaration, which only has a class selector to its name) and
   cascaded down via inheritance to both the title span (no colour of
   its own) and the arrow icon's `stroke="currentColor"`. Fixed by
   pinning the colour on :hover explicitly - `.teaser-card:hover`'s two
   class-level selectors (class + pseudo-class) outrank a:hover's
   type+pseudo-class pairing regardless of source order, so this is a
   permanent fix, not a specificity coin-toss. Replaced with the actual
   design ask instead: a very slight darkening of the image itself. */
.teaser-card:hover {
    color: var(--colour-white);
}

.teaser-card:hover .teaser-card__image {
    filter: brightness(0.9);
}

.teaser-card__date {
    position: absolute;
    top: 1rem;
    left: 1rem;
    z-index: 1;
    background-color: var(--accent-amber);
    color: var(--colour-body-text);
    font-family: var(--font-body);
    font-weight: 700;
    font-size: 14px;
    padding: 0.25em 0.75em;
    border-radius: 999px;
}

.teaser-card__title {
    position: absolute;
    left: 1rem;
    right: 1rem;
    bottom: 1rem;
    z-index: 1;
    font-family: var(--font-display);
    font-size: 22px;
}

.teaser-card__arrow {
    position: absolute;
    right: 1rem;
    bottom: 1rem;
    z-index: 1;
    width: 2rem;
    height: 2rem;
    display: flex;
    align-items: center;
    justify-content: center;
    border: 1px solid var(--colour-white);
    border-radius: 999px;
}

/* ------------------------------------------------------------------
   Header/nav - matches the design's two header treatments (see design
   page renders + [[pitmeadow-farm-content-model]] memory): a solid
   brand-colour bar on every page except the homepage, which instead
   gets a transparent header sitting directly on top of its hero photo
   (confirmed with Tom - a deliberate, homepage-only difference, not an
   inconsistency to reconcile). `header--home` comes from
   templates/header/default_header.html.twig's own site-level override
   (app.request.pathinfo == '/').

   Desktop-only for now (>=992px, matching Bootstrap's existing lg nav
   breakpoint) - the design's centred-logo/split-nav layout hasn't been
   checked against the mobile design pages (source/DEV/pages/m_13-16.pdf)
   yet, since rendering those needs poppler-utils and Tom asked not to
   install anything without asking first. Below 992px this deliberately
   falls back to the package's plain default (logo left, hamburger
   right) rather than guessing at a mobile treatment - flagged as a
   follow-up, not forgotten. */
/* padding removed on request ("hover state background needs to extend
   to the top of the screen") - #header's own padding was a gap no
   descendant's background could ever reach into, however tall a
   hovered item's own box was made. Equivalent visual breathing room now
   comes from #header .container's min-height (below) instead, with
   align-items: stretch letting a hovered item's box span that entire
   height, edge to edge - #header itself starts at the literal top of
   the page on the homepage (position: absolute; top: 0), so a box
   spanning #header's full height reaches the true top of the screen
   there, not just the nav row's own inset content area. */
#header {
    background: var(--colour-brand);
    border-bottom: none;
    padding: 0;
    position: relative;
    z-index: 20;
}

#header.header--home {
    background: transparent;
    position: absolute;
    top: 0;
    left: 0;
    right: 0;
    border-top: 4px solid var(--colour-brand);
}

/* Removed outright sitewide, on request ("`.cc-content-container` have
   top and bottom padding set in the css - please remove this") -
   supersedes the narrower, incrementally-scoped attempts this same
   padding went through earlier the same day (first just :first-child's
   own padding-top, then a back-and-forth over banner blocks'
   padding-bottom specifically - see git history/memory for that story
   if it matters later). Tom's own instruction here is the simple,
   general one: no content block anywhere gets this structural
   top/bottom padding from the vendor's own _layout.scss default
   ($cc-padding-default, 2rem) any more - each block's own admin-set
   "Padding top"/"Padding bottom" display properties (a separate,
   independent mechanism, `.ci-content-container.pt-*`/`.pb-*`) are
   unaffected by this and still work normally. */
.cc-content-container {
    padding-top: 0;
    padding-bottom: 0;
}

/* Bumped on request ("increase logo size", comparing against the
   homepage design) - the design's own logo reads noticeably larger
   relative to the header/nav than the original 48px. A pixel-diff
   measurement (the same cap-height technique used to size the nav text
   itself) proved unreliable here - the two-line "Pitmeadow"/"Farm"
   lockup's inter-line gap is narrow enough that anti-aliasing never
   fully returns to the background colour, merging both lines' bounding
   boxes into one artificially tall span - so this is a direct visual
   match against the design instead of a measured ratio. */
#header .site-logo img {
    height: 64px;
    width: auto;
}

/* .nav-half (site.js) - two clones of the primary nav either side of
   the centred logo, built at runtime and hidden here below 992px so
   mobile keeps using the original hamburger-toggled nav untouched. */
.nav-half {
    display: none;
}

@media (min-width: 992px) {
    #header .container {
        display: flex;
        /* stretch (was centre) - see #header's own comment above on
           why this is what lets a hovered item's background genuinely
           reach the full header height rather than just the row of
           text/logo content within it. min-height preserves the
           header's previous overall height now that #header's own
           padding is gone. */
        align-items: stretch;
        justify-content: center;
        min-height: 6.5rem;
    }

    /* The original nav (hamburger toggler + collapse) is mobile-only
       once the two .nav-half clones exist - hidden outright at desktop
       rather than just its toggler button, since its content is fully
       duplicated into the clones below. */
    #header nav.navbar {
        display: none;
    }

    /* .container now stretches every direct child to its full height
       (see above) - the logo itself should stay vertically centred
       within that height, not stretched/distorted, so it needs its
       own align-self back to centre. */
    #header .site-logo {
        order: 2;
        align-self: center;
    }

    /* Equal-width flex columns either side of the logo, content
       aligned toward it - this is what keeps the logo genuinely
       centred regardless of each side's own text width (see site.js's
       own docblock for why a space-between + fixed-gap CSS-only
       attempt didn't). align-items default (stretch) is what lets each
       <li> below fill the row's full height in turn. */
    .nav-half {
        display: flex;
        flex: 1;
        gap: 1.75rem;
        list-style: none;
        margin: 0;
        padding: 0;
    }

    .nav-half--left {
        order: 1;
        justify-content: flex-end;
    }

    .nav-half--right {
        order: 3;
        justify-content: flex-start;
    }

    .nav-half li {
        position: relative;
    }

    /* On request ("hover background for menu item and dropdown is the
       same width"): widen only a dropdown-having item's own box to a
       fixed minimum - the dropdown below (right: 0 added further down)
       then stretches to match this exact width automatically, rather
       than the two being sized independently (the item to its own text,
       the dropdown to its own min-width) and only visually patched
       together at the seam as before. A leaf item (no dropdown) is
       unaffected and keeps its own natural, text-sized width. */
    .nav-half > li:has(> ul.menu_level_1) {
        min-width: 12rem;
    }

    /* Real bug found live: .nav-half sits outside #navbarSupportedContent
       (site.js clones the nav to two new siblings of it, not inside
       it - see that file's own docblock), so it never inherited the
       vendor CSS's base dropdown behaviour (#navbarSupportedContent
       ul.menu_level_1's own position/display:none/hover-to-show rules,
       scoped to that id specifically) - every dropdown rendered
       permanently expanded in normal block flow instead. Reproduces
       the same behaviour here, scoped to .nav-half.

       left/right: 0 (not min-width) on request - stretches the dropdown
       to exactly match its own parent <li>'s width (set immediately
       above), whatever that resolves to, rather than sizing itself
       independently and only coincidentally lining up.

       margin-top on request ("too much space between the nav elements
       and the top of the screen" / "menu item position was good before
       the last change, dropdown position is correct after the change"):
       the item's own box is stretched to the full <li> height (104px,
       matching #header .container's min-height) so its background can
       reach the screen's top, and its text is centred within that box
       (align-items: centre, reverted below - the position confirmed
       good) - but centring within a box that tall leaves real, visible
       whitespace between the text and the <li>'s own bottom edge, which
       is where `top: 100%` would otherwise attach the dropdown. A plain
       top:100% therefore reproduces the "too much space before the
       dropdown" complaint regardless of the item text's own alignment,
       since the box itself - not the text's alignment within it - is
       what top:100% is measured against. Pulling the dropdown up by
       that known gap - half of (104px li height minus the item text's
       own ~44.8px content height, both measured via
       getBoundingClientRect() earlier this session, not guessed -
       decouples the two: the item's text can stay centred (the "good"
       position) while the dropdown still ends up tight against it
       (the "correct" position), rather than both being forced to trade
       off against each other via the same align-items property. */
    .nav-half ul.menu_level_1 {
        position: absolute;
        top: 100%;
        margin-top: -29.6px;
        left: 0;
        right: 0;
        padding: .5rem 0;
        display: none;
        z-index: 1040;
    }

    .nav-half li:hover > ul.menu_level_1,
    .nav-half li:focus-within > ul.menu_level_1 {
        display: block;
    }

    .nav-half ul.menu_level_1 li {
        padding: .25rem 1rem;
    }

    /* On request ("hover state background needs to extend to the top
       of the screen" + implicitly, its own bottom): the interactive
       box (a or span) fills its <li>'s entire stretched height/width
       rather than being an inline-block sized to its own text with
       whitespace above/below it - see #header's own top-of-file
       comment for why this is what lets the hover background reach
       the header's true edges. Desktop-only (.nav-half, not
       #navbarSupportedContent) - the mobile hamburger list is a plain
       vertical stack where this wouldn't mean anything. Set further
       down (after the shared padding/border-radius rule, which also
       sets `display` - needs to come later in source order to win on
       that shared property, since both rules match with equal
       specificity and CSS falls back to source order). */
}

/* A top-level item with children (e.g. "Our Story", "Events & Hire")
   has no URL of its own - menu.html.twig renders it as a plain
   <span tabindex="0">, not an <a> (see FrontendMenuBuilder's own
   docblock on container_only items) - real bug found live: these
   rendered in the default inherited (dark) text colour, since every
   rule below originally only targeted `a`. */
#navbarSupportedContent a,
#navbarSupportedContent span,
.nav-half a,
.nav-half span {
    font-family: var(--font-display);
    font-weight: 400;
    font-size: 20px;
    letter-spacing: 0.02em;
    text-transform: uppercase;
    text-decoration: none;
    color: var(--colour-white);
}

/* Real bug found live (2026-09-30, "current primary nav item is not
   highlighted on Stay / Local Info / Farm Safety / Contact"): a link
   item's text sits in a nested <span> inside its <a> (see the note
   below), and the broad rule above paints that span white DIRECTLY -
   a directly-set colour always beats one inherited from the parent,
   whatever the parent's own rule's specificity. So the li.current /
   :hover rules further down were correctly turning the <a> blue while
   its own child span stayed white, and the text rendered white. The
   two container-only items ("Our Story", "Events & Hire") never had
   the problem because their text sits directly in the styled <span>.
   The nested span should simply inherit its colour from the one
   interactive element per item - that's where every state is set. */
#navbarSupportedContent > ul > li > a > span,
.nav-half > li > a > span {
    color: inherit;
}

/* Real bug found live: a real link item's markup is <a href="..."><span>
   text</span></a> (menu.html.twig always wraps link text in its own
   span, link or not) - the broad rule above is fine to double-apply
   (colour/font are inherited anyway, harmless twice over), but padding/
   display:inline-block box-model properties are NOT harmless applied
   twice: a link item was getting them on both the outer <a> AND its own
   nested <span>, while a childless dropdown-parent item (a bare <span
   tabindex="0">, no wrapping <a> - see FrontendMenuBuilder's own
   docblock on container_only items) only ever got them once - stacking
   two lots of padding made every real link's own box measurably taller
   (57.6px vs 44.8px, confirmed via getBoundingClientRect(), not
   guessed) than a dropdown-parent's, pushing its own text visibly
   higher within the shared flex row's stretched height. Scoped to just
   the direct child of <li> - the one interactive element per item -
   fixes this without an extra, redundant box on the nested span. */
#navbarSupportedContent > ul > li > a,
#navbarSupportedContent > ul > li > span,
.nav-half > li > a,
.nav-half > li > span {
    padding: 0.4rem 0.6rem;
    border-radius: 4px;
    /* On request (2026-09-30): pointer cursor on every primary item,
       dropdown parent or not. A real link gets it for free; the two
       container-only items are a bare <span tabindex="0"> with no href
       (see the note above) and so fell back to the default cursor. */
    cursor: pointer;
    /* Quick white-to-blue fade on hover/focus, on request (2026-09-30:
       "a subtle, quick animation from white to blue when hovering").
       Colour only - deliberately NOT background-color: a dropdown
       parent's khaki box (below) must appear in the same instant as
       the dropdown panel it joins on to, or the seam between a
       half-faded box and an already-solid panel flickers visibly for
       the duration of the fade. The nested text span inherits `color`
       (see above) so it tracks this fade frame by frame. */
    transition: color 0.15s ease-in-out;
}

/* display split from the shared rule above: the mobile hamburger list
   (#navbarSupportedContent) stays a plain inline-block sized to its own
   text; the desktop clones (.nav-half) instead fill their <li>'s full
   stretched height/width and centre their own text within it - see
   that rule's own comment above (in the desktop media query) for why. */
#navbarSupportedContent > ul > li > a,
#navbarSupportedContent > ul > li > span {
    display: inline-block;
}

/* align-items: centre - reverted back from flex-end on request ("too
   much space between the nav elements and the top of the screen" - the
   flex-end attempt to tighten the item-to-dropdown gap overcorrected,
   pushing the text all the way to the box's bottom and leaving a large
   empty gap above it instead. Centre is the position Tom confirmed was
   good). The dropdown's own tight positioning (also confirmed correct)
   is instead handled independently below, via a negative margin-top
   pulling it up to the centred item's own visual bottom edge - see that
   rule's own comment for the real measurement behind the value. */
.nav-half > li > a,
.nav-half > li > span {
    display: flex;
    align-items: center;
    justify-content: center;
    height: 100%;
    width: 100%;
    box-sizing: border-box;
}

/* Hover/focus = the selected state, on request (2026-09-30: "hovering
   on primary nav items should show the same state as when selected"):
   the text fades from white to the same slate blue li.current uses
   below. Supersedes the earlier pixel-sampled reading of the design's
   homepage mockup ("Our Story" mid-hover: white text on a khaki box),
   which was only ever a dropdown parent being shown - that item's box
   is kept, below, for the dropdown's sake; a leaf item now gets no
   box at all, so its hover genuinely IS its selected state. Padding is
   constant in every state so nothing ever shifts layout. */
#navbarSupportedContent > ul > li:hover > a,
#navbarSupportedContent > ul > li:hover > span,
#navbarSupportedContent > ul > li:focus-within > a,
#navbarSupportedContent > ul > li:focus-within > span,
.nav-half > li:hover > a,
.nav-half > li:hover > span,
.nav-half > li:focus-within > a,
.nav-half > li:focus-within > span {
    color: var(--accent-slate-blue);
}

/* A hovered DROPDOWN PARENT ("Our Story", "Events & Hire") keeps its
   khaki (--colour-brand) background box: it's the same box the
   dropdown panel below uses, so the two read as one continuous shape -
   Tom's own iterated spec ("hover state is a solid block background
   for both the menu item and its children", "top corners of nav should
   not be rounded", "same width", "extend to the top of the screen"),
   none of which the 2026-09-30 hover-equals-selected request touched.
   Every corner square (no rounding at all, top included) so item box
   and panel form one rectangle rather than two separately-rounded
   pills. Leaf items (no dropdown) get no box - see above. */
#navbarSupportedContent > ul > li:has(> ul.menu_level_1):hover > a,
#navbarSupportedContent > ul > li:has(> ul.menu_level_1):hover > span,
#navbarSupportedContent > ul > li:has(> ul.menu_level_1):focus-within > a,
#navbarSupportedContent > ul > li:has(> ul.menu_level_1):focus-within > span,
.nav-half > li:has(> ul.menu_level_1):hover > a,
.nav-half > li:has(> ul.menu_level_1):hover > span,
.nav-half > li:has(> ul.menu_level_1):focus-within > a,
.nav-half > li:has(> ul.menu_level_1):focus-within > span {
    background: var(--colour-brand);
    border-radius: 0;
}

/* Current-page/current-ancestor - functional-default in the vendor CSS
   was font-weight only; the design shows a real colour swap instead
   (sampled as a muted blue-grey, matching --accent-slate-blue already
   used elsewhere for the same "selected" meaning on filter pills). */
#navbarSupportedContent li.current > a,
#navbarSupportedContent li.current_ancestor > a,
#navbarSupportedContent li.current > span,
#navbarSupportedContent li.current_ancestor > span,
.nav-half li.current > a,
.nav-half li.current_ancestor > a,
.nav-half li.current > span,
.nav-half li.current_ancestor > span {
    font-weight: 400;
    color: var(--accent-slate-blue);
}

/* Dropdown submenu (Our Story's "About us"/"About the farm") - design
   shows a solid brand-colour box, not the vendor default's white one.
   Top corners square (not rounded) so it reads as one continuous shape
   with the hovered parent item's own box above it (that box gets
   matching top-only rounding, see the :has() rule above) rather than
   two separately-rounded pills with a visible seam between them. */
#navbarSupportedContent ul.menu_level_1,
.nav-half ul.menu_level_1 {
    background: var(--colour-brand);
    border: none;
    border-radius: 0 0 4px 4px;
    text-align: center;
}

/* Real bug found live, pixel/visual-confirmed against the design: a
   dropdown item ("About us"/"About the farm") is NOT the stamped
   display font every top-level item uses - it's a clean, evenly-weighted
   sans-serif (the body font), sentence case. Must also target the
   nested <span> menu.html.twig wraps link text in - a directly-targeted
   property (the earlier #navbarSupportedContent span/.nav-half span
   rule's text-transform: uppercase) always beats an inherited one
   regardless of specificity, so setting text-transform: none on the
   <a> alone was overridden right back to uppercase on its own child
   span. Confirmed live (rendered "ABOUT US", not "About us") before
   this fix, not assumed. */
#navbarSupportedContent ul.menu_level_1 a,
#navbarSupportedContent ul.menu_level_1 span,
.nav-half ul.menu_level_1 a,
.nav-half ul.menu_level_1 span {
    font-family: var(--font-body);
    font-size: 15px;
    font-weight: 400;
    text-transform: none;
    padding: 0;
}

#navbarSupportedContent ul.menu_level_1 a,
.nav-half ul.menu_level_1 a {
    display: block;
    /* Same quick colour fade the primary items use (see their own
       shared rule above for why it's colour only). */
    transition: color 0.15s ease-in-out;
}

/* Same nested-span bug as the primary items (see the `color: inherit`
   rule near the top of this nav section): a dropdown link's text span
   was painted white directly by the broad rule, so neither li.current
   (the child page you're actually on) nor any hover colour on the <a>
   could ever reach it - on request (2026-09-30, "dropdown items need
   hover color too" / "they don't highlight"). */
#navbarSupportedContent ul.menu_level_1 a > span,
.nav-half ul.menu_level_1 a > span {
    color: inherit;
}

/* Dropdown link hover/focus: same slate blue as a primary item's
   hover and as the current page, so every nav state uses one colour.
   The parent item above stays hovered (it's an ancestor) and keeps its
   own blue text + khaki box while the pointer is down here. The
   current child page itself is already blue via the li.current rule
   above, now that its span inherits. */
#navbarSupportedContent ul.menu_level_1 li:hover > a,
#navbarSupportedContent ul.menu_level_1 li:focus-within > a,
.nav-half ul.menu_level_1 li:hover > a,
.nav-half ul.menu_level_1 li:focus-within > a {
    color: var(--accent-slate-blue);
}

/* ------------------------------------------------------------------
   Footer - dark olive background, white logo/text, khaki square
   social-icon buttons. The bottom bar (copyright + site_info links)
   deliberately departs from the design here, on request: no divider
   line above it, and the copyright line centred on its own row rather
   than sharing a row with the site_info links. */
/* Real gap found live, on request ("remove the margin above the
   footer"): the vendor's own _footer.scss sets #footer { margin-top:
   $cc-padding-double } (64px) - never overridden until now, so every
   page had a visible white strip (the page's own background showing
   through) between its last content section and the olive footer,
   regardless of that last section's own background colour. */
#footer {
    background: var(--accent-olive);
    color: var(--colour-white);
    border-top: none;
    margin-top: 0;
}

#footer .row--footer--contact-nav ul.list-unstyled a,
#footer .container--footer-bar {
    color: var(--colour-white);
}

#footer .container--footer-bar {
    border-top: none;
    flex-direction: column;
    align-items: center;
    text-align: center;
}

#footer .container--footer-bar small {
    color: var(--colour-white);
    width: 100%;
}

#footer .footer-bar-menu {
    justify-content: center;
    width: 100%;
}

#footer .footer-bar-menu a {
    text-transform: uppercase;
    letter-spacing: 0.02em;
    font-size: 13px;
}

/* Real bug found live: the vendor markup gives .row--footer--contact-nav
   Bootstrap's own real `row` class without pairing its two children
   with a matching `col-*` class - Bootstrap 5's `.row > *` selector
   sets `width: 100%; max-width: 100%` unconditionally on every direct
   child of any `.row`, expecting a `.col-*` class to override it back
   down. With neither child having one, both stretched to the full row
   width and stacked vertically instead of sitting side by side as the
   design shows. Confirmed via computed styles, not assumed. */
#footer .row--footer--contact,
#footer .row--footer__social {
    width: auto;
    max-width: none;
    flex-shrink: 1;
}

/* Design shows the site_info links as real nav-style items (uppercase,
   spaced) - the vendor default's plain small-print styling undersells
   them against the design's own treatment. */
#footer .row--footer__social a {
    background: var(--colour-brand);
    width: 2.5rem;
    height: 2.5rem;
    border-radius: 4px;
    align-items: center;
    justify-content: center;
    color: var(--colour-white);
}

#footer .row--footer__social a:hover {
    background: var(--accent-amber);
    opacity: 1;
}

/* Real bug found live: "Staying at Pitmeadow Farm" (and every other
   text_and_image block) shows a small whitespace gap beneath its image
   that isn't in the design. Measured via computed styles first, not
   assumed - the vendor markup wraps the image in a bare <figure> with
   no class, and neither the figure nor the img itself carries any
   margin (confirmed 0px both). The gap is the classic inline-image
   baseline gap instead: <img> defaults to display:inline, so the
   browser reserves space below it for text descenders on its line box
   - here that was ~7.6px, the figure box measuring taller than the
   image it contains by exactly that amount. Fixing generically at the
   figure level (not just .text-image) since this is a markup-level gap
   that would reproduce in any other block using a bare <figure><img>. */
figure img {
    display: block;
}

/* Real "Notes" section (address/size/beds/priceRange/seasonNotes) - a
   separate section further down the page, as the design places it
   (see the template's own comment). Matches the design's
   own off-white band + text/photo pairing (source/DEV/pages/5.pdf) -
   reuses .text-image's own existing flex/figure layout, just with its
   own background colour. */
.accommodation-notes-section {
    background-color: var(--bg-off-white);
    padding-block: 3rem;
}

.accommodation-notes {
    max-width: 640px;
}

.accommodation-notes p {
    margin-bottom: 0.5rem;
}

/* "All amenities" - moved to the very bottom of the page, underneath
   "Notes", split over 3 columns, on request (2026-09-06) - was a
   right-hand sidebar box paired with "About the accommodation",
   matching the design (source/DEV/pages/5.pdf); Tom asked to abandon
   that placement for this one instead. Plain white background (the
   page's last section before the footer). */
.accommodation-amenities-section {
    padding-block: 3rem;
}

.accommodation-amenities {
    list-style: disc;
    columns: 3;
    column-gap: 2rem;
    padding-left: 1.25rem;
    margin: 1.5rem 0 0;
}

.accommodation-amenities li {
    margin-bottom: 0.5rem;
    break-inside: avoid;
}

@media (max-width: 900px) {
    .accommodation-amenities {
        columns: 1;
    }
}
