/**********************************************************

    ███████╗ ██████╗  ██████╗ ████████╗███████╗██████╗
    ██╔════╝██╔═══██╗██╔═══██╗╚══██╔══╝██╔════╝██╔══██╗
    █████╗  ██║   ██║██║   ██║   ██║   █████╗  ██████╔╝
    ██╔══╝  ██║   ██║██║   ██║   ██║   ██╔══╝  ██╔══██╗
    ██║     ╚██████╔╝╚██████╔╝   ██║   ███████╗██║  ██║
    ╚═╝      ╚═════╝  ╚═════╝    ╚═╝   ╚══════╝╚═╝  ╚═╝

 **********************************************************/



    /*
        Figma reference — Homepage, the FOOTER instance at 1920 x 704.

        The footer is built from the theme's own blocks inside the footer
        static element, so almost nothing here creates layout: it dresses
        markup that the editor produces. Which means the selectors follow
        what those blocks actually emit —

            nvm-text  ... a heading as <h2> and its paragraphs
            nvm-menu  ... <nav class="nvm-menu"> around <ul class="menu">
            nvm-image ... <figure class="image-box">
            nvm-logo-grid ... a row of .logo-column

        Two of the three bands are named in the editor, in the row block's
        "Additional CSS class(es)" box:

            footer-columns ... the row with the logo and the four columns
            footer-legal ..... the closing line

        The payment strip needs no name — it is the only logo grid down here.

        An earlier version told the bands apart by what they contained, with
        :has(), so that nothing had to be typed. This is worth the typing: a
        row says outright which band it is, rather than being guessed at from
        its contents and changing character the day somebody adds a menu to
        the wrong one.
    */

    .main-footer {
        padding: clamp( 50px, 7.64vw, 110px ) var(--nvm-content-inset);
        border: none;
        box-shadow: none;
        background: var(--nvm-color-white);
        color: var(--nvm-color-ink);
    }

        /* The section and panel wrappers the blocks bring with them would add
           a second inset on top of the one above, and centre a narrower column
           inside an already centred one. The footer sets its own width. */

        .main-footer .section,
        .main-footer .panel {
            width: 100%;
            margin: 0;
            padding: 0;
        }



/*******************************

    ████████╗██╗   ██╗██████╗ ███████╗
    ╚══██╔══╝╚██╗ ██╔╝██╔══██╗██╔════╝
       ██║    ╚████╔╝ ██████╔╝█████╗
       ██║     ╚██╔╝  ██╔═══╝ ██╔══╝
       ██║      ██║   ██║     ███████╗
       ╚═╝      ╚═╝   ╚═╝     ╚══════╝

 *******************************/



    /*
        Vanilla styles headings and links at element level, so anything left
        to inheritance loses. Every value is stated on the element that holds
        the text, with a class in front of it to win on specificity.
    */

    /* Column headings — 15 / 22.5 bold, set in capitals by the stylesheet so
       they can be typed normally and still translate. */

    .responsiville .main-footer .nvm-text h2,
    .responsiville .main-footer .nvm-text h3 {
        margin: 0 0 30px;
        padding: 0;
        color: var(--nvm-color-ink);
        font-size: 15px;
        font-weight: 700;
        line-height: 1.5;
        text-transform: uppercase;
    }

    /* The contact column is set in bold at 13, unlike the link columns. */

    .responsiville .main-footer .nvm-text p {
        margin: 0;
        color: var(--nvm-color-ink);
        font-size: 13px;
        font-weight: 700;
        line-height: 1.5;
    }

    .responsiville .main-footer .nvm-text p + p {
        margin-top: 30px;
    }

    /*
        The text block indents itself by a gutter, and not on purpose.

        responsiville.ingrid.css gives every grid column its gutter with the
        attribute selector [class*="column"]. The text block carries classes
        named nvm-text-columns-desktop-1 and the like — its own text columns,
        nothing to do with the grid — and the substring matches. So the block
        takes a 10px padding meant for something else and the words sit off
        the line the logo and the menus keep to.

        text-style.css does answer this with `padding: 0 !important`, but that
        file is only enqueued for the editor: the front end never sees it,
        which is why it looks right in the admin and wrong on the page.

        Corrected here for the footer alone, where it shows. The same thing is
        true of every nvm-text on the site and is worth a proper look later.
    */

    .main-footer .nvm-text {
        padding-left: 0;
        padding-right: 0;
    }

    /* A heading and the list under it are two separate blocks, and the theme
       spaces consecutive text blocks apart on its own. The heading's 30 is
       the whole of the gap the design draws, so the second helping goes. */

    .main-footer .nvm-text + .nvm-text {
        margin-top: 0;
        margin-bottom: 0;
    }



/*******************************

    ███╗   ███╗███████╗███╗   ██╗██╗   ██╗███████╗
    ████╗ ████║██╔════╝████╗  ██║██║   ██║██╔════╝
    ██╔████╔██║█████╗  ██╔██╗ ██║██║   ██║███████╗
    ██║╚██╔╝██║██╔══╝  ██║╚██╗██║██║   ██║╚════██║
    ██║ ╚═╝ ██║███████╗██║ ╚████║╚██████╔╝███████║
    ╚═╝     ╚═╝╚══════╝╚═╝  ╚═══╝ ╚═════╝ ╚══════╝

 *******************************/



    /* Items sit 35 apart in the design and are 20 tall, so the gap is 15. */

    .main-footer .nvm-menu ul.menu {
        display: flex;
        flex-direction: column;
        gap: 15px;
        margin: 0;
        padding: 0;
        list-style: none;
    }

        /*
            The size is repeated on the item and not left to the anchor, and
            it is not belt and braces.

            The anchor below is the only thing in the item that carries a
            size; the item itself keeps the body's 17px and its line height of
            1.5, and an inline anchor sits on a line box built to that larger
            measure. The result was rows 40 apart instead of the 35 drawn —
            space that belonged to nothing visible. Sizing the item, and
            making the anchor a block so it stops riding a line box at all,
            leaves the row exactly as tall as its text.
        */

        .main-footer .nvm-menu ul.menu li {
            margin: 0;
            padding: 0;
            list-style: none;
            font-size: 13px;
            line-height: 1.5;
        }

            .main-footer .nvm-menu ul.menu li::before {
                display: none;
            }

            .responsiville .main-footer .nvm-menu ul.menu li a {
                display: block;
                padding: 0;
                background: none;
                color: var(--nvm-color-ink);
                font-size: 13px;
                font-weight: 400;
                line-height: 1.5;
                text-decoration: none;
                transition: color 0.2s ease-in-out;
            }

            .responsiville .main-footer .nvm-menu ul.menu li a:hover,
            .responsiville .main-footer .nvm-menu ul.menu li a:focus-visible {
                background: none;
                color: var(--nvm-color-gold);
            }

            /* The current page is not marked in the design, and a footer list
               of twenty links is no place to start. */

            .responsiville .main-footer .nvm-menu ul.menu li.current-menu-item a {
                color: var(--nvm-color-ink);
            }



/*******************************

     ██████╗ ██████╗ ██╗     ██╗   ██╗███╗   ███╗███╗   ██╗███████╗
    ██╔════╝██╔═══██╗██║     ██║   ██║████╗ ████║████╗  ██║██╔════╝
    ██║     ██║   ██║██║     ██║   ██║██╔████╔██║██╔██╗ ██║███████╗
    ██║     ██║   ██║██║     ██║   ██║██║╚██╔╝██║██║╚██╗██║╚════██║
    ╚██████╗╚██████╔╝███████╗╚██████╔╝██║ ╚═╝ ██║██║ ╚████║███████║
     ╚═════╝ ╚═════╝ ╚══════╝ ╚═════╝ ╚═╝     ╚═╝╚═╝  ╚═══╝╚══════╝

 *******************************/



    /*
        The logo and the four columns.

        In the design the five are 112 / 128 / 93 / 154 / 140 wide with an
        even 203 between each — which is not a grid, it is five columns of
        their own width spread across the line. So the theme's percentage
        columns are set aside here and the row is spaced apart instead: the
        gaps stay even however long the words turn out in either language,
        which a fixed percentage could not promise.
    */

    /*
        Below laptop the five sit two to a line.

        The editor has them at small-column-100 and tablet-column-100, which
        is one column a line all the way from a phone to a 1023 tablet: five
        full width blocks stacked, before the payment marks and the closing
        line are counted. A reader has to scroll past the whole of that to
        leave the page.

        Half width takes that to three lines — the mark beside the contact
        details, then the two pairs of menus — and the headings are still at
        their drawn 15, which is what keeps it readable rather than merely
        shorter.

        This does override what the admin chose, and it is the one place in
        this file that does so on purpose: the column block offers 100, 50,
        33 and the rest, and whichever is picked there would still be read as
        a width for a single column rather than for a row of five. The five
        are a set and are spaced as one here, the same way the laptop rules
        below set the editor's percentages aside for the drawn widths.

        30 across and 40 down: the across is the gutter the row would have
        had, the down is the gap already used between the stacked columns.

        The row is already display: flex with wrap, from the framework, and
        the pair is stated here rather than under `.small` because the
        breakpoint classes are cumulative — `.small` is on the page at every
        width, so a rule written there would outlive the phone and undo the
        laptop layout below.
    */

    .main-footer .footer-columns {
        gap: 40px 30px;
        margin: 0;
    }

        /*
            The gutter goes at every width, so the logo starts on the same
            line as the section's own edge rather than 10px inside it — which
            is also why the halves are short of 50% by half the gap: with no
            padding left to separate them, the gap is the only thing between
            the two columns and it has to come out of their width.
        */

        .main-footer .footer-columns > .column {
            flex-basis: calc( 50% - 15px );
            max-width: calc( 50% - 15px );
            padding: 0;
        }

    /*
        From laptop the design takes over: five columns of their own width,
        spread evenly across the line. This is where the editor's percentages
        are set aside, because the drawn widths are 112 / 128 / 93 / 154 / 140
        and no percentage grid describes that.
    */

    /*
        space-between does the spreading, so the gap is only a floor.

        It was written as a clamp rising to the drawn 203, which is the figure
        the artboard measures between columns — but that figure is a result,
        not an instruction. At 1440 four gaps of 203 plus the columns came to
        1504 in a 1340 line, and with nowrap there was nowhere for the excess
        to go: the last column hung past the right edge and the whole page
        scrolled sideways.

        Left to distribute the free space itself, space-between arrives at the
        same 203 at 1920 and at whatever fits below it.

        The columns may also give way now. Sized purely by their text, a long
        Greek label was enough to overrun the line on its own.
    */

    .laptop .main-footer .footer-columns {
        flex-wrap: nowrap;
        justify-content: space-between;
        gap: 20px;
    }

        .laptop .main-footer .footer-columns > .column {
            flex: 0 1 auto;
            width: auto;
            min-width: 0;
        }

            .main-footer .footer-columns > .column > .column-content {
                padding: 0;
            }

        /* The mark is 112 wide in the design. `img { height: auto !important }`
           lives in the framework's stylesheet, so the ratio has to be left to
           the file rather than stated, or it is overruled anyway. */

        .main-footer .footer-columns .image-box {
            width: clamp( 84px, 7.78vw, 112px );
            margin: 0;
        }

            .main-footer .footer-columns .image-box img {
                display: block;
                width: 100%;
                height: auto !important;
            }



/*******************************

    ██████╗  █████╗ ██╗   ██╗
    ██╔══██╗██╔══██╗╚██╗ ██╔╝
    ██████╔╝███████║ ╚████╔╝
    ██╔═══╝ ██╔══██║  ╚██╔╝
    ██║     ██║  ██║   ██║
    ╚═╝     ╚═╝  ╚═╝   ╚═╝

 *******************************/



    /*
        The payment marks — ten outlined boxes, 58 x 40, twenty apart and
        centred on the page.

        A logo grid is used rather than anything fixed so the marks can be
        added and dropped from the media library as the shop's providers
        change. Its own column widths are therefore ignored: the boxes are
        sized here and simply wrap when there is no more room, which is what
        makes an eleventh one a non-event.
    */

    /*
        A line break inside a picture box is never meant.

        On some pages — Special Offers is one, the home page is not — the
        footer's content comes back from the editor with a <br> sitting
        inside every <figure>, before the image. It is a newline in the
        markup that a filter has turned into a tag, and it costs a line box:
        27px of it, which pushed the picture that far down inside a 40px
        frame that clips. The marks came out as slivers, and only on those
        pages, which is what made it look like a stylesheet problem.

        Hidden rather than chased upstream, because the <br> is introduced
        after the theme has handed over its markup and could come back on any
        page the day a plugin changes. Nothing inside an image box ever wants
        a line break, so this holds wherever it appears.
    */

    .main-footer .image-box br {
        display: none;
    }

    .main-footer .nvm-logo-grid {
        margin-top: clamp( 40px, 4.86vw, 70px );
    }

        .main-footer .nvm-logo-grid .row {
            display: flex;
            flex-wrap: wrap;
            justify-content: center;
            align-items: center;
            gap: 20px;
            margin: 0;
        }

            /*
                Nothing is forced on these. The 40 is a ceiling, not a size.

                The marks were given width: 58px and height: 40px outright,
                which is what every file happens to be — so a mark that was
                ever anything else had to give way, and the figure's
                overflow: hidden is what it gave way to. A cap leaves each
                picture at its own size and its own proportions, and only
                steps in when one is too tall for the row.

                height: auto has to be said, and with !important, twice over.
                theme.images.css carries `.image-box img { height: 100%
                !important }`, which beats the framework's own `height: auto
                !important` on specificity — so without this the picture would
                take the figure's height rather than its own, which is the
                very thing being undone here.

                With a cap and no stated width, a mark too tall for the row
                comes down proportionally: the browser scales the width to
                match, so nothing is squeezed and nothing is cropped.

                aspect-ratio: auto because .image-box sets 16/3 by default,
                and a shape imposed on a box that is now sized by its contents
                would bring the clipping back by another route.
            */

            .main-footer .nvm-logo-grid .logo-column {
                flex: 0 0 auto;
                width: auto;
                padding: 0;
            }

                .main-footer .nvm-logo-grid .logo-column .image-box,
                .main-footer .nvm-logo-grid .logo-column img {
                    display: block;
                    width: auto;
                    height: auto !important;
                    max-height: 40px;
                    aspect-ratio: auto;
                    margin: 0;
                    object-fit: contain;
                }



/*******************************

    ██╗     ███████╗ ██████╗  █████╗ ██╗
    ██║     ██╔════╝██╔════╝ ██╔══██╗██║
    ██║     █████╗  ██║  ███╗███████║██║
    ██║     ██╔══╝  ██║   ██║██╔══██║██║
    ███████╗███████╗╚██████╔╝██║  ██║███████╗
    ╚══════╝╚══════╝ ╚═════╝ ╚═╝  ╚═╝╚══════╝

 *******************************/



    /*
        The closing line: the company's particulars and the credit, centred
        together as one group with 40 between them rather than pushed to
        opposite edges — which is how the artboard has them, sitting off
        centre to the left of the full width.
    */

    .main-footer .footer-legal {
        display: flex;
        flex-wrap: wrap;
        justify-content: center;
        align-items: baseline;
        gap: 10px 40px;
        margin: clamp( 40px, 4.86vw, 70px ) 0 0;
        text-align: center;
    }

        /*
            0 1 auto, and the 1 is the whole point.

            These columns are sized by their text rather than by the grid, so
            that the two halves sit together in the middle instead of being
            pushed to opposite edges. With flex-shrink at 0 they were also
            refusing to come down: the company's particulars are one long
            line, 806px of it, and on a 390 phone that held the whole document
            206px wider than the screen — the page sliding left and right.

            Shrink restored, they give way and the line wraps. max-width and
            min-width keep the promise even where a single word is longer than
            the screen.
        */

        .main-footer .footer-legal > .column {
            flex: 0 1 auto;
            width: auto;
            min-width: 0;
            max-width: 100%;
            padding: 0;
        }

            .main-footer .footer-legal > .column > .column-content {
                padding: 0;
            }

        .responsiville .main-footer .footer-legal .nvm-text p,
        .responsiville .main-footer .footer-legal p {
            margin: 0;
            color: var(--nvm-color-ink);
            font-size: 14px;
            font-weight: 400;
            line-height: 1.5;
        }

        .responsiville .main-footer .footer-legal a {
            background: none;
            color: var(--nvm-color-ink);
            text-decoration: none;
        }

        .responsiville .main-footer .footer-legal a:hover {
            background: none;
            color: var(--nvm-color-gold);
        }



/*****************************************************

     █████╗  ██████╗ ██████╗ ██████╗ ██████╗ ██████╗ ██╗ ██████╗ ███╗   ██╗
    ██╔══██╗██╔════╝██╔════╝██╔═══██╗██╔══██╗██╔══██╗██║██╔═══██╗████╗  ██║
    ███████║██║     ██║     ██║   ██║██████╔╝██║  ██║██║██║   ██║██╔██╗ ██║
    ██╔══██║██║     ██║     ██║   ██║██╔══██╗██║  ██║██║██║   ██║██║╚██╗██║
    ██║  ██║╚██████╗╚██████╗╚██████╔╝██║  ██║██████╔╝██║╚██████╔╝██║ ╚████║
    ╚═╝  ╚═╝ ╚═════╝ ╚═════╝ ╚═════╝ ╚═╝  ╚═╝╚═════╝ ╚═╝ ╚═════╝ ╚═╝  ╚═══╝

 *****************************************************/



    /*
        The menus as drawers, on a phone.

        Everything here hangs off `responsiville-accordion-enabled`, which
        Responsiville puts on the row when it turns the accordion on and takes
        off again at `tablet`. So the two columns a tablet gets and the drawn
        row of five above it are not merely unaffected by these rules — they
        never match them, and there is no breakpoint written twice.

        js/theme.footer.js marks the columns that carry a menu with
        `footer-columns__panel`. The mark and the contact details are not
        among them: they keep the half width from the section above and sit
        side by side over the drawers.
    */

    /*
        No row gap, because the drawers measure their own.

        Every panel carries 20 above and 20 below its line, so consecutive
        drawers are evenly spaced whichever of them is open. A row gap on top
        of that counted a third helping between each pair and the group drifted
        apart. The space above the first line is put where it belongs instead
        — under the two columns that are not drawers.
    */

    .main-footer .footer-columns.responsiville-accordion-enabled {
        row-gap: 0;
    }

        .main-footer .footer-columns.responsiville-accordion-enabled > .column:not( .footer-columns__panel ) {
            padding-bottom: 25px;
        }

        /*
            A drawer takes the line to itself. Two half width drawers would
            put two headings and two pluses on one row, and a reader would
            have to work out which plus belonged to which.

            The rule is a line above each and one more under the last, rather
            than a line under each and one above the first: `:first-of-type`
            counts elements of a type among their siblings, and the first div
            in this row is the column with the mark in it, not the first
            drawer — so the group opened without a line over it. `:last-child`
            is the last column outright, which is the last drawer.
        */

        .main-footer .footer-columns.responsiville-accordion-enabled > .footer-columns__panel {
            flex-basis: 100%;
            max-width: 100%;
            padding: 20px 0;
            border-top: 1px solid var(--nvm-color-stone);
        }

        .main-footer .footer-columns.responsiville-accordion-enabled > .footer-columns__panel:last-child {
            border-bottom: 1px solid var(--nvm-color-stone);
        }

            /*
                The heading is the control.

                It is a text block from the editor rather than a button, so
                the affordances have to be stated: the cursor, room on the
                right for the plus, and the heading's own 30px bottom margin
                taken away — that margin is the gap to a list that is not
                showing yet, and left in place it held a closed drawer open
                by 30 pixels of nothing.
            */

            .main-footer .responsiville-accordion-enabled .footer-columns__panel .nvm-text {
                position: relative;
                padding-right: 34px;
                cursor: pointer;
            }

            .responsiville .main-footer .responsiville-accordion-enabled .footer-columns__panel .nvm-text h2,
            .responsiville .main-footer .responsiville-accordion-enabled .footer-columns__panel .nvm-text h3 {
                margin: 0;
            }

                /*
                    The plus is drawn rather than set.

                    responsiville.accordion.css has one of its own, in the
                    framework's icon font, but it is bound to
                    `.responsiville-accordion-header` — a class this accordion
                    never uses, since the heading block is the header. Two
                    bars cost nothing and owe nothing to a webfont that may
                    not have loaded when the footer is reached.
                */

                .main-footer .responsiville-accordion-enabled .footer-columns__panel .nvm-text::before,
                .main-footer .responsiville-accordion-enabled .footer-columns__panel .nvm-text::after {
                    content: '';
                    position: absolute;
                    top: 50%;
                    right: 0;
                    width: 14px;
                    height: 1.5px;
                    margin-top: -0.75px;
                    background: currentColor;
                    transition: transform 0.25s ease-in-out, opacity 0.25s ease-in-out;
                }

                /* The upright bar of the plus, which leaves on opening and
                   turns as it goes, so the plus becomes a minus. */

                .main-footer .responsiville-accordion-enabled .footer-columns__panel .nvm-text::after {
                    transform: rotate( 90deg );
                }

                .main-footer .responsiville-accordion-enabled .responsiville-accordion-panel-open .nvm-text::after {
                    transform: rotate( 0deg );
                    opacity: 0;
                }

            /*
                The gap between the heading and the list.

                On the inner list rather than on the sliding element: the
                animation measures the drawer's height, and padding on the
                drawer itself is counted from the first frame, so the list
                started 20px down and jumped. On the ul it is carried along
                with the rest.
            */

            .main-footer .responsiville-accordion-enabled .footer-columns__panel .nvm-menu ul.menu {
                padding-top: 20px;
            }

            /*
                An open drawer is as tall as its list, whatever the animation
                left behind.

                The slide ends by setting an exact pixel height on the menu,
                measured before it opened. That is right to the pixel on the
                day, but it is a number frozen into the element: a font that
                swaps late, a longer label in the other language or a link
                added to the menu would all leave the list taller than the box
                holding it — and the box now clips, so the last entry would
                simply go missing.

                Once the panel is open the height is no longer doing any work,
                so it is handed back to the content. !important because the
                animation writes its figure inline.
            */

            .main-footer .responsiville-accordion-enabled .responsiville-accordion-panel-open .nvm-menu {
                height: auto !important;
            }

    /*
        And the same once the accordion lets go.

        Closing a drawer ends with an exact `height: 0` written inline on the
        menu by the animation. While the accordion is on that is invisible,
        because a closed drawer is display: none as well — but widen the
        window past 599 and the accordion disables itself, puts the display
        back and leaves the height alone. The rule above cannot help: it hangs
        off `responsiville-accordion-enabled`, the very class that has just
        been taken away.

        The result was a footer that came back empty on a phone turned
        sideways, and stayed empty until the page was reloaded.

        So the height is handed back here too, keyed off the absence of that
        class. !important because it is an inline style being overruled.

        Outside the accordion block on purpose: this is what the footer looks
        like when the accordion is NOT running, which is every screen from a
        tablet up.
    */

    .main-footer .footer-columns:not( .responsiville-accordion-enabled ) .nvm-menu {
        height: auto !important;
    }

    @media ( prefers-reduced-motion: reduce ) {

        .main-footer .responsiville-accordion-enabled .footer-columns__panel .nvm-text::before,
        .main-footer .responsiville-accordion-enabled .footer-columns__panel .nvm-text::after {
            transition: none;
        }

    }



/*******************************

    ███████╗███╗   ███╗ █████╗ ██╗     ██╗
    ██╔════╝████╗ ████║██╔══██╗██║     ██║
    ███████╗██╔████╔██║███████║██║     ██║
    ╚════██║██║╚██╔╝██║██╔══██║██║     ██║
    ███████║██║ ╚═╝ ██║██║  ██║███████╗███████╗
    ╚══════╝╚═╝     ╚═╝╚═╝  ╚═╝╚══════╝╚══════╝

 *******************************/



    /*
        There is no mobile artboard for the footer. The columns go two to a
        line, which is set in the COLUMNS section above rather than here so
        that the laptop rules can still override it — see the note there. The
        headings keep their size: they are already small, and shrinking them
        further would only make the footer harder to use on the screen where
        it is hardest to use.

        What is left for this section is the two bands that are centred and
        wrap on their own, and only need their gaps tightened.
    */
    .small .main-footer .nvm-logo-grid .row {
        gap: 12px;
    }

    .small .main-footer .footer-legal {
        gap: 10px 20px;
    }


    /*
        Payment logos, lined up by height rather than width.

        The logo grid gives each logo a column of the row's width — 16% on a
        desktop, so about 190px — and the picture is stretched to fill it,
        capped at 100px tall. Two things follow, and both show.

        The pictures are small: 58 x 40 for most of the cards, 81 x 40 for
        tbi bank. Blown up to 100px tall they are two and a half times their
        own size and go soft.

        And they stop matching each other. Sized by width, a wider logo comes
        out shorter: tbi is 81 wide, so it fills its column and lands at 95px
        tall, while a 58 wide card hits the 100px ceiling and leaves 23px of
        empty column on either side of itself. The row reads as uneven and
        the odd one out looks like it has a hole around it.

        They are all drawn 40 tall, which is the one thing they agree on. So
        height is what is fixed here and width follows — every logo the same
        height, each taking only the room it needs, and all of them at the
        size they were made.

        Scoped to the footer: nvm-logo-grid is a block anyone can place, and
        a brand wall somewhere else has no reason to be 40px tall.

        The !important is not decoration — theme.images.css carries
        `.image-box img { height: 100% !important }`.
    */

    .main-footer .nvm-logo-grid .logo-column figure {
        display: flex;
        align-items: center;
        justify-content: center;
    }

    .main-footer .nvm-logo-grid .logo-column figure img {
        width: auto;
        max-width: 100%;
        height: 40px !important;
        object-fit: contain;
    }

