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

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

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



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

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

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



    /*
        Figma reference — the "Category" artboard at 1920.

            120 │ filters 219 │ 21 │ grid 1440 │ 120     = 1920

        This is not the column the home page keeps to, and the difference is
        not a rounding: --nvm-content-inset is 240 at this width and puts the
        content at 240, while the shop begins at 120 and gives the 120 it saves
        to the filter column. So the shop carries its own inset rather than
        bending the shared one, which every other page still depends on.

        max() holds the grid at its drawn 1440 once the screen is wide enough
        and lets the margins take the rest, exactly as the content inset does
        for the rest of the site.
    */

    .small {
        --nvm-shop-inset   : 10px;
        --nvm-shop-filters : 219px;
        --nvm-shop-gutter  : 21px;
    }

    .tablet {
        --nvm-shop-inset: 30px;
    }

    .laptop {
        --nvm-shop-inset: 50px;
    }

    .desktop {
        --nvm-shop-inset: max( 60px, calc( ( 100vw - 1680px ) / 2 ) );
    }

    .nvm-shop {
        display: grid;
        grid-template-columns: 1fr;
        gap: 40px;
        padding: clamp( 40px, 5.73vw, 110px ) var(--nvm-shop-inset);
    }

        /*
            The grid closes with as much air as it opened with — but only when
            nothing follows it.

            The closing text brings its own 140 above the mark, and on a
            category that has one the two would stack into a gap far larger
            than the artboard draws. The shop page has no such text, and
            without this the pagination sat straight on top of the footer.
        */

        .nvm-shop:has( + .nvm-shop__description ) {
            padding-bottom: 0;
        }

        /* The floor a grid track keeps by default is the widest thing inside
           it, and a product photograph is wider than a phone. Lifted here for
           every child, which is what stops the page sliding sideways. */

        .nvm-shop > * {
            min-width: 0;
        }

    /*
        The filter column arrives at laptop. Below that it stacks above the
        grid at full width: a 219 column beside two products leaves neither
        enough room, and filters are worth more at the top of a phone than
        squeezed down its side.
    */

    .laptop .nvm-shop--has-filters {
        grid-template-columns: var(--nvm-shop-filters) 1fr;
        column-gap: var(--nvm-shop-gutter);
        align-items: start;
    }



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

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

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



    /*
        The band behind the title is 1920 x 327 — far shallower than the 21:9
        every other page uses, so the ratio is restated rather than a new one
        added to the image sizes.
    */

    /*
        The band's height comes from the photograph's ratio — and a page
        without one would have no band at all, with the title inside it
        absolutely placed and therefore invisible.

        The cart, the checkout and the account are ordinary pages: they have a
        featured image only if somebody sets one. min-height keeps the band
        standing either way, at the same measure the ratio would have given
        it, so the two cases look like the same band rather than two designs.
    */

    .hero-section--shop {
        position: relative;
        min-height: clamp( 150px, 17.03vw, 327px );
        background: var(--nvm-color-sand-dark);
    }

        /*
            The picture is given the band's floor as well as the band's ratio.

            1920 / 327 is 5.87 : 1, and below roughly 880px of screen that
            ratio makes a band shorter than the 150 floor above — 85 at 500,
            66 at 390. The band still stood at 150, so the photograph stopped
            partway down it and the rest was flat sand, with the title and the
            trail straddling the join. That is the "cut" band on a phone.

            Handed the same floor, the picture fills the band and crops, which
            is what a banner this wide has to do on a narrow screen. On a
            desktop the ratio wins and nothing is cropped at all, so the
            drawn band is untouched.

            Centred, which is the shop's choice. Anchoring the crop left
            would keep the whole of the pale area the title is written
            across; centred, some of it goes and the words carry further
            onto the photograph. The band reads as the one in the artboard
            this way, so the title is the thing that gives ground.

            The cover itself is already set — theme.images.css gives every
            .image-box img width and height of 100% with object-fit: cover
            and object-position: 50% 50%, so nothing is restated here.
        */

        .hero-section--shop .image-box {
            aspect-ratio: 1920 / 327;
            min-height: clamp( 150px, 17.03vw, 327px );
        }

            .hero-section--shop .hero-section-image img {
                object-fit: cover;
            }

    /*
        The title lies on the photograph, not under it.

        The band is one thing in the artboard — a picture 1920 by 327 with the
        name of the category and the trail written across its pale left side.
        Left in the flow the text fell below the picture instead, and the band
        came out 357 tall with a centred heading sitting on the page colour.

        So the text is lifted over the image and the band's own height, set by
        the picture's ratio, is what holds them both.
    */

    .hero-section--shop .hero-section-text {
        position: absolute;
        top: 0;
        right: 0;
        bottom: 0;
        left: 0;
        display: flex;
        flex-direction: column;
        justify-content: center;
        align-items: flex-start;
        padding: 0 var(--nvm-shop-inset);
    }

        /*
            The band's panel and row come from the shared hero markup, which
            centres its heading and holds it to the common content column.
            Neither is wanted here: the title begins on the shop's own left
            edge, which is 120 rather than 240.
        */

        .hero-section--shop .hero-section-text .panel,
        .hero-section--shop .hero-section-text .row {
            width: 100%;
            max-width: none;
            margin: 0;
            padding: 0;
        }

        .hero-section--shop .hero-section-text .row {
            justify-content: flex-start;
        }

        .responsiville .hero-section--shop h1,
        .responsiville .hero-section--shop h2 {
            margin: 0;
            color: var(--nvm-color-ink);
            font-size: clamp( 32px, 4.17vw, 80px );
            font-weight: 800;
            line-height: 1.1;
            text-align: left;
        }

        /*
            The stores page, and only it.

            Its band is a dark photograph and the artboard sets the heading
            in white over it; the ink every other band uses would be unread­
            able there. The page is named by its slug rather than by the id
            WordPress offers, so the rule still finds it if the page is ever
            rebuilt — see nvm_config_body_slug_class().
        */

        .responsiville.page-katastimata .hero-section--shop h1,
        .responsiville.page-katastimata .hero-section--shop h2,
        .responsiville.page-katastimata .hero-section--shop .woocommerce-breadcrumb,
        .responsiville.page-katastimata .hero-section--shop .woocommerce-breadcrumb a,
        .responsiville.page-katastimata .hero-section--shop .hero-section-breadcrumb__sep {
            color: var(--nvm-color-white);
        }

        /* The trail's link is stone on every other band and white here, so
           its hover cannot be the stone-to-ink of the others either. */

        .responsiville.page-katastimata .hero-section--shop .woocommerce-breadcrumb a:hover {
            background: none;
            color: var(--nvm-color-gold);
        }

        .hero-section--shop .hero-section-breadcrumb {
            margin-top: clamp( 16px, 2.08vw, 40px );
        }

            /* The trail is written in the category's own case, and only the
               page you are standing on is dark — the rest are links and read
               as links. */

            .responsiville .hero-section--shop .woocommerce-breadcrumb {
                margin: 0;
                color: var(--nvm-color-ink);
                font-size: 12px;
                font-weight: 700;
                line-height: 1.3;
            }

            .responsiville .hero-section--shop .woocommerce-breadcrumb a {
                padding: 0;
                background: none;
                color: var(--nvm-color-ink);
                font-weight: 400;
                text-decoration: none;
                transition: color 0.2s ease-in-out;
            }

            .responsiville .hero-section--shop .woocommerce-breadcrumb a:hover {
                background: none;
                color: var(--nvm-color-gold);
            }

            /*
                The first crumb is a house.

                It is done here and not in the markup because it cannot be
                done in the markup: woocommerce_breadcrumb() takes a `home`
                argument, but global/breadcrumb.php prints every crumb's name
                through esc_html(), so an SVG passed in would arrive on the
                page as the characters of its own source.

                Which turns out to be the better half of the bargain. The
                word stays in the document and screen readers still announce
                "Αρχική σελίδα" — font-size: 0 shrinks it out of sight
                without taking it out of the accessibility tree, the way
                display: none would.

                The icon is a mask rather than a background image so that it
                takes currentColor: stone beside the other links, gold on
                hover, white on the pages that invert the trail. One file,
                every state, nothing to keep in step by hand.

                The path is the one that was on this site before, kept
                exactly as it was drawn — a house with a doorway, two pixel
                strokes, mitred corners — so this is the icon coming back
                rather than a second one taking its place.
            */

            .responsiville .hero-section--shop .woocommerce-breadcrumb a:first-child {
                font-size: 0;
                line-height: 0;
            }

            .responsiville .hero-section--shop .woocommerce-breadcrumb a:first-child::before {
                content: "";
                display: inline-block;
                width: 13px;
                height: 13px;
                vertical-align: -2px;
                background-color: currentColor;
                -webkit-mask: url("data:image/svg+xml,%3Csvg xmlns='http://www.w3.org/2000/svg' viewBox='0 0 24 24' fill='none' stroke='%23000' stroke-width='2' stroke-linejoin='round'%3E%3Cpath d='M3 10.5 12 3l9 7.5V21h-6v-6H9v6H3z'/%3E%3C/svg%3E") no-repeat center / contain;
                        mask: url("data:image/svg+xml,%3Csvg xmlns='http://www.w3.org/2000/svg' viewBox='0 0 24 24' fill='none' stroke='%23000' stroke-width='2' stroke-linejoin='round'%3E%3Cpath d='M3 10.5 12 3l9 7.5V21h-6v-6H9v6H3z'/%3E%3C/svg%3E") no-repeat center / contain;
            }

            .hero-section--shop .hero-section-breadcrumb__sep {
                display: inline-block;
                margin: 0 12px;
                color: var(--nvm-color-ink);
                font-weight: 400;
            }



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

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

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



    .nvm-shop__filters {
        display: flex;
        flex-direction: column;
        gap: 5px;
    }

    /*
        Not on a phone, where it is a heading over nothing.

        The filter plugin draws its own row of controls on small screens —
        Τιμή, Κατηγορίες, Όλα τα φίλτρα — and leaves this column empty.
        Measured at 390: the aside stands 45 tall, which is the white head and
        no more, and of the two plugin containers inside it none has any size
        at all. At 834 the same aside is 1902 tall with 424 visible controls
        in it, so the line is drawn between the two rather than guessed at.

        .small and then .tablet, because the breakpoint classes are
        cumulative: .small is on the page at every width and cannot be left to
        mean "phone" by itself.
    */

    .small .nvm-shop__filters {
        display: none;
    }

    .tablet .nvm-shop__filters {
        display: flex;
    }

        /* The head and every card below it are the same white block, 15 of
           padding all round — which is what puts the label at 135 and the icon
           15 in from the right edge of a 219 column. */

        .nvm-shop__filters-head {
            display: flex;
            align-items: center;
            justify-content: space-between;
            gap: 10px;
            min-height: 40px;
            padding: 5px 15px;
            background: var(--nvm-color-white);
        }

            .nvm-shop__filters-label {
                color: var(--nvm-color-ink);
                font-size: 14px;
                font-weight: 800;
                line-height: 1.1;
                text-transform: uppercase;
            }

            .nvm-shop__filters-icon {
                display: flex;
                flex: 0 0 auto;
                width: 30px;
                height: 30px;
                color: var(--nvm-color-ink);
            }

                .nvm-shop__filters-icon svg {
                    display: block;
                    width: 30px;
                    height: 30px !important;
                }

    /*
        Each filter is a white card of its own, five apart — colour, price,
        stock, and the rest, each on its own ground with the page showing
        between them. That is how the artboard stacks them, and the five is
        measured from it.

        The widget is not the card, and this is the part that had to change:
        one widget holds every filter the plugin prints, so dressing the
        widget made a single tall card with the filters run together inside
        it. The widget is now only a container, and the ground moves to each
        .fibofilters-block within.

        Three nested columns each keep the same five, so the spacing holds
        wherever the plugin decides to nest a filter.
    */

    .nvm-shop__filter-card {
        display: flex;
        flex-direction: column;
        gap: 5px;
        padding: 0;
        background: transparent;
    }

        .nvm-shop__filters .fibofilters-vertical-filters-container {
            display: flex;
            flex-direction: column;
            gap: 5px;
        }

        .nvm-shop__filters .fibofilters-block {
            padding: 25px 15px;
            background: var(--nvm-color-white);
        }

            /*
                The plugin zeroes the top padding of the first filter, because
                in its own layout that one opens a single panel and wants no
                gap above it. Here every filter is a card of its own, so the
                first needs the same 25 as the rest or it sits tight against
                its own top edge while the others do not.

                The rule it has to beat is
                `.fibofilters-vertical-filters-container .fibofilters-block:first-child`,
                which carries three classes; this carries four, so it wins on
                weight rather than on load order.
            */

            .nvm-shop__filters .fibofilters-vertical-filters-container .fibofilters-block:first-child {
                padding-top: 25px;
            }

        /*
            The widget's own heading, when one is given. It takes the same
            ground as a filter so it does not float on the page colour —
            and leaving the widget's title empty in the admin removes it
            altogether, which is what the artboard shows.
        */

        .responsiville .nvm-shop__filter-title {
            margin: 0;
            padding: 15px;
            background: var(--nvm-color-white);
            color: var(--nvm-color-ink);
            font-size: 16px;
            font-weight: 800;
            line-height: 1.3;
        }

        .responsiville .nvm-shop__filter-card ul {
            margin: 0;
            padding: 0;
            list-style: none;
        }

            .responsiville .nvm-shop__filter-card li {
                margin: 0;
                padding: 0;
                list-style: none;
                font-size: 14px;
                line-height: 1.5;
            }

            .responsiville .nvm-shop__filter-card li + li {
                margin-top: 20px;
            }

            .responsiville .nvm-shop__filter-card li a {
                padding: 0;
                background: none;
                color: var(--nvm-color-ink);
                font-size: 14px;
                font-weight: 400;
                text-decoration: none;
            }

            .responsiville .nvm-shop__filter-card li a:hover {
                background: none;
                color: var(--nvm-color-gold);
            }



    /*
        Each filter's own heading is underlined, the rule running the width of
        the card between its 15 of padding.

        No colour is given to the border on purpose: currentColor keeps it on
        the heading it belongs to, so the two cannot drift apart if that text
        is ever recoloured.
    */

    .nvm-shop__filters .fibofilters-block__headline-box {
        padding-bottom: 10px;
        border-bottom: 2px solid currentColor;
    }



    /*
        The chevron that says a filter opens and closes.

        It was in the markup all along and measured zero by zero. The plugin
        gives .fibofilters-block__chevron-btn no size of its own and lets the
        icon inside carry its own 14 by 8, positioned absolutely against it.
        responsiville.moressette.css then applies `max-width: 100%` and
        `height: auto !important` to every svg on the site — and 100% of a
        box with no width is nothing. The arrow was drawn in grey, visible,
        opaque, and nought pixels wide.

        So the two are given a size. The height carries !important because
        that is the only way past moressette's own, and the button is sized
        as well so the icon has something to be centred against.

        Eleven by seven rather than the fourteen by eight it ships at, and
        drawn in currentColor at one and a half rather than grey at two. The
        rule above this one puts a 2px line in currentColor under the same
        heading: at the shipped weight the arrow read as a second piece of
        furniture beside that line, and in #767676 it read as a third colour
        on a page that uses two. Smaller and in the heading's own ink, it is
        a mark on the heading rather than an object next to it.

        The turn is animated because it is the only thing that happens when
        the heading is pressed and the panel above or below slides: an arrow
        that jumps while everything else moves looks like two events.

        Not scoped to the sidebar: the same chevron is in the mobile and
        horizontal filter panels, and it is missing there for the same
        reason.
    */

    .fibofilters-block__chevron-btn {
        width: 11px;
        height: 7px;
    }

    .fibofilters-block__chevron-btn-icon {
        width: 11px;
        height: 7px !important;
        transition: transform 0.2s ease-in-out;
    }

        .fibofilters-block__chevron-btn-icon path {
            stroke: currentColor;
            stroke-width: 1.5;
        }



    /* The name of each value beside its box. */

    .nvm-shop__filters .fibofilters-item__label {
        font-size: 12px;
    }

    /*
        The one media query in this stylesheet, and it is deliberate.

        Everything else here keys off the framework's breakpoint classes, but
        768 sits inside `tablet` rather than on it — .tablet begins at 600 —
        so writing it as a class would move the change by a hundred and sixty
        pixels. The measurement is kept as given.
    */

    @media ( min-width: 768px ) {

        .nvm-shop__filters .fibofilters-block__headline .fibofilters-block__headline-box-inner {
            font-size: 13px;
        }

    }



    /*
        A chosen filter is marked by the tick alone.

        The plugin fills the whole box with its base colour — already the gold
        — and draws a white tick on it. The design asks for the reverse: the
        box keeps its thin outline and stays on the page colour, and the tick
        itself is what turns gold.

        The two selectors mirror the plugin's own: a filter with children is
        wrapped in a collapser, and the box then sits one level deeper.
    */

    .nvm-shop__filters .fibofilters-item.fibofilters-selected > .fibofilters-item__interactive > .fibofilters-item__control,
    .nvm-shop__filters .fibofilters-item.fibofilters-selected > .fibofilters-collapser-container > .fibofilters-item__interactive > .fibofilters-item__control {
        background: transparent;
    }

        /*
            The tick is a stroked path — a line, with nothing to fill. The
            framework's `svg path { fill: currentColor }` does not know that
            and pours the text colour into it, which on a gold ground was
            invisible and on a bare one would be a dark blot behind the mark.
            Both halves are stated: no fill, and the stroke in gold.
        */

        .nvm-shop__filters .fibofilters-item__control svg path {
            fill: none;
            stroke: var(--nvm-color-gold);
        }



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

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

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



    /*
        Sorting on the left, the count on the right. WooCommerce prints them
        the other way round, so they are swapped with order rather than by
        re-hooking — anything else a plugin adds to the same hook then falls
        between the two instead of being displaced by a changed priority.
    */

    /*
        The rule under the bar, and the height that puts it on the same line
        as the filter column's heading.

        Both boxes begin at the top of the row, so giving the bar the 40 the
        heading already has lands the two bottom edges together — 557 in the
        artboard, for both. The drawing has the bar at 37 and starting three
        lower, which comes to the same line; matching the height is the part
        that survives a change of type size.
    */

    .nvm-shop__bar {
        display: flex;
        flex-wrap: wrap;
        align-items: center;
        gap: 10px 20px;
        min-height: 40px;
        margin-bottom: clamp( 30px, 4.17vw, 56px );
        border-bottom: 1px solid var(--nvm-color-silver);
        color: var(--nvm-color-stone);
        font-size: 14px;
        font-weight: 800;
        line-height: 1.1;
    }

        /* A notice takes the whole line. Left in the row it would squash the
           two controls into whatever was left. */

        .nvm-shop__bar .woocommerce-notices-wrapper {
            flex: 0 0 100%;
            order: 0;
        }

        .nvm-shop__bar .woocommerce-notices-wrapper:empty {
            display: none;
        }

        /*
            The filter plugin hangs several containers of its own on this same
            hook, and they arrive inside the bar.

            Empty, they still keep their padding: one of them stands 40px tall
            with nothing at all in it, which made the bar 45 and carried the
            rule six pixels below the filter column's heading. :not(:has(*))
            is "holds no element", which is the honest test — :empty fails on
            a container that holds only whitespace, and these do.

            When they are carrying something they take the full width beneath
            the row, rather than being squeezed into it alongside the sorting.
        */

        .nvm-shop__bar > [class*="fibofilters"]:not( :has( * ) ) {
            display: none;
        }

        .nvm-shop__bar > [class*="fibofilters"] {
            flex: 0 0 100%;
            order: 4;
        }

        .nvm-shop__bar .woocommerce-ordering {
            order: 1;
            margin: 0;
        }

        .nvm-shop__bar .woocommerce-result-count {
            order: 3;
            margin: 0 0 0 auto;
            color: var(--nvm-color-stone);
            font-size: 14px;
            font-weight: 800;
        }

        /*
            On a phone the count is under the sorting, not beside it.

            The auto margin is what puts it at the right end of the bar, which
            is the drawing from the tablet up. There is no room for the two
            side by side on a phone, so the count wraps onto its own line —
            and an auto margin on a line of its own just strands it at the
            right, out of line with everything above and below it.
        */

        .small .nvm-shop__bar .woocommerce-result-count {
            margin-left: 0;
        }

        .tablet .nvm-shop__bar .woocommerce-result-count {
            margin-left: auto;
        }

        /*
            The same bar on a page that lists its products by shortcode — the
            Special Offers page (Nevma blocks around [products on_sale]).

            There WooCommerce prints the count and the sorting itself, straight
            into its own wrapper with the products after them, so there is no
            .nvm-shop__bar to hang the rules above on. The wrapper becomes the
            row instead, the grid takes the full width beneath it, and the line
            the bar draws under itself is drawn over the grid. The category
            pages never match: their grid is not inside a .column-content.
        */

        .nvm-shop__main > .column-content > .woocommerce {
            display: flex;
            padding: 0;
            flex-wrap: wrap;
            align-items: center;
            column-gap: 20px;
            color: var(--nvm-color-stone);
            font-size: 14px;
            font-weight: 800;
            line-height: 1.1;
        }

            .nvm-shop__main > .column-content > .woocommerce > .woocommerce-notices-wrapper {
                flex: 0 0 100%;
                order: 0;
            }

            .nvm-shop__main > .column-content > .woocommerce > .woocommerce-notices-wrapper:empty {
                display: none;
            }

            .nvm-shop__main > .column-content > .woocommerce > .woocommerce-ordering {
                display: flex;
                align-items: center;
                min-height: 40px;
                order: 1;
                margin: 0;
            }

            .nvm-shop__main > .column-content > .woocommerce > .woocommerce-result-count {
                order: 3;
                margin: 0 0 0 auto;
                color: var(--nvm-color-stone);
                font-size: 14px;
                font-weight: 800;
            }

            .nvm-shop__main > .column-content > .woocommerce > .products {
                flex: 0 0 100%;
                order: 5;
                margin-top: 0;
                padding-top: clamp( 30px, 4.17vw, 56px );
                border-top: 1px solid var(--nvm-color-silver);
            }

            .nvm-shop__main > .column-content > .woocommerce > .woocommerce-pagination {
                flex: 0 0 100%;
                order: 6;
            }

        /* The page's two columns are Nevma blocks, which carry the grid's
           own gutter as padding; the archive's aside and main do not, so the
           column would sit 10 further in and 20 narrower than the drawn 219.
           The filter column also stacks its head and cards five apart, as the
           aside does, though here they sit one level down. */

        .nvm-shop > .nvm-shop__filters,
        .nvm-shop > .nvm-shop__main {
            padding-left: 0;
            padding-right: 0;
        }

        .nvm-shop > .nvm-shop__filters > .column-content {
            display: flex;
            flex-direction: column;
            gap: 5px;
        }

            .nvm-shop > .nvm-shop__filters > .column-content > .nvm-text {
                margin: 0;
                padding: 0;
            }

            /* The select is the design's plain label with a value beside it,
               not a boxed form control. */

            /*
                The chevron is drawn rather than left to the browser.

                A select with its own background removed still shows whatever
                arrow the platform draws, and that arrow is a different shape
                on every one of them — the drawing has a single small chevron,
                so appearance: none clears the native one and the mark is
                supplied here, in the same grey as the label.
            */

            .responsiville .nvm-shop__bar .woocommerce-ordering select,
            .responsiville .nvm-shop__main > .column-content > .woocommerce > .woocommerce-ordering select {
                -webkit-appearance: none;
                appearance: none;

                /*
                    A select takes the width of its longest option, not the
                    one showing — here "Ταξινόμηση κατά μέσο όρο βαθμολογίας",
                    which held the box at 326 and left the chevron stranded a
                    hundred pixels past the end of the words.

                    field-sizing lets it measure the selected option instead,
                    which is the whole reason the property exists. Browsers
                    without it keep the old behaviour: the mark sits further
                    right than drawn, still legible and still theirs to click.
                */
                field-sizing: content;

                height: auto;
                min-height: 0;
                padding: 0 20px 0 0;
                border: none;
                border-radius: 0;
                background-color: transparent;
                background-image: url( "data:image/svg+xml,%3Csvg xmlns='http://www.w3.org/2000/svg' width='10' height='6' viewBox='0 0 10 6'%3E%3Cpath d='M1 1l4 4 4-4' fill='none' stroke='%237F7F7F' stroke-width='1.4' stroke-linecap='round' stroke-linejoin='round'/%3E%3C/svg%3E" );
                background-repeat: no-repeat;
                background-position: right center;
                background-size: 10px 6px;
                color: var(--nvm-color-stone);
                font-size: 14px;
                font-weight: 800;
                line-height: 1.1;
                cursor: pointer;
            }

            /*
                Choosing an option leaves the select focused, and
                responsiville.moressette.css answers that with

                    input:focus, textarea:focus, select:focus {
                        box-shadow: 0 0 10px -5px currentColor;
                    }

                On a boxed form control that halo reads as a soft edge. On
                this one, which has no border and no background, it is the
                only thing drawn — so a grey box appears around the words out
                of nowhere, and because field-sizing measures the chosen
                option, the box is a different width every time. That is the
                jumping the design never asked for.

                :focus-visible was tried in its place, on the understanding
                that it is the half of :focus a browser raises for the
                keyboard and not for the mouse. That is true of a text field.
                It is not true of a select: a select is worked with the arrow
                keys, so Chrome counts it as expecting keyboard input and
                matches :focus-visible after a plain click as well. The
                outline came back, darker than the halo it replaced.

                So nothing is drawn. The cost is real and it is noted here
                rather than hidden: a reader tabbing through the page gets no
                mark on this control. The honest fix is an indicator the
                design can live with at every focus — an underline under the
                words would do it — and that is a decision about the design,
                not something to settle in a bug fix.
            */

            .responsiville .nvm-shop__bar .woocommerce-ordering select:focus,
            .responsiville .nvm-shop__main > .column-content > .woocommerce > .woocommerce-ordering select:focus {
                box-shadow: none;
                outline: none;
            }



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

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

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



    /*
        Four to a row at the drawn width — 4 x 345 and three 20 gaps is 1440
        exactly — coming down a column at a time as the screen narrows. Two on
        a phone rather than one: a single column turns a category of forty
        products into a very long scroll, and the card survives the width.

        The container is named by its class alone rather than as ul.products.
        WooCommerce opens the loop with a <ul>, but the card this theme prints
        is a <div>, so every rule written as `> li.product` matched nothing at
        all and did so silently. Naming the class holds whichever tag the list
        ends up with.

        The card itself is not styled here. woocommerce/content-product.php and
        the products carousel's stylesheet already draw it, and that stylesheet
        is enqueued on every page rather than only where the block appears.
    */

    .responsiville .nvm-shop__main .products {
        display: grid;
        grid-template-columns: repeat( 2, 1fr );
        gap: 40px 10px;
        margin: 0;
        padding: 0;
        list-style: none;
    }

    .tablet .responsiville .nvm-shop__main .products,
    .responsiville .tablet .nvm-shop__main .products {
        gap: 50px 20px;
    }

    .laptop .responsiville .nvm-shop__main .products,
    .responsiville .laptop .nvm-shop__main .products {
        grid-template-columns: repeat( 3, 1fr );
    }

    .desktop .responsiville .nvm-shop__main .products,
    .responsiville .desktop .nvm-shop__main .products {
        grid-template-columns: repeat( 4, 1fr );
        gap: 70px 20px;
    }

        /*
            WooCommerce clearfixes the product list with ::before and ::after,
            from the days it was a float layout. They carry content, so in a
            grid they stop being invisible table cells and become grid items
            like any other — and the first one takes the opening cell, leaving
            a hole where the first product should be.
        */

        .responsiville .nvm-shop__main .products::before,
        .responsiville .nvm-shop__main .products::after {
            content: none;
            display: none;
        }

        .responsiville .nvm-shop__main .products > .product {
            min-width: 0;
            margin: 0;
            padding: 0;
            list-style: none;
            width: auto;
            max-width: none;
            float: none;
        }

            .responsiville .nvm-shop__main .products > .product::before {
                display: none;
            }



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

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

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


    /* The band itself is in css/theme.pagination.css, which dresses this
       one and the blog archive's alike. Only its distance from the grid
       above belongs to this page. */

    .nvm-shop__main .woocommerce-pagination {
        margin-top: clamp( 40px, 4.86vw, 70px );
    }



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

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

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



    /*
        The category's own words, at the foot of the page: 768 wide and centred
        on the page rather than on the grid, which is why it takes no notice of
        the filter column beside it.

        768 of writing, not a 768 box. The inset is padding and the element is
        border-box, so a flat max-width of 768 spent it on the margins: at 1920
        the inset computes to 120 a side and the line came out 528 wide —
        measured — against the 768 the artboard sets. The same arithmetic that
        had the articles rendering 668 instead of 768.

        So the padding is added to the cap rather than taken out of it, and the
        same variable is on both sides of the sum, so the two cancel at every
        width. Narrower than about 890 the cap is wider than the window, the
        box goes full width and the inset is all that is left — which is the
        behaviour wanted there anyway.
    */

    .nvm-shop__description {
        max-width: calc( var(--nvm-panel-small-width) + 2 * var(--nvm-shop-inset) );
        margin: 0 auto;
        padding: clamp( 50px, 7.29vw, 140px ) var(--nvm-shop-inset) clamp( 50px, 6.25vw, 120px );
    }

        /* The house mark, 60 x 32, opening the block. */

        .nvm-shop__description-mark {
            display: block;
            width: clamp( 44px, 3.13vw, 60px );
            margin-bottom: clamp( 30px, 4.17vw, 60px );
            color: var(--nvm-color-ink);
        }

            .nvm-shop__description-mark svg {
                display: block;
                width: 100%;
                height: auto !important;
            }

        .responsiville .nvm-shop__description-title,
        .responsiville .nvm-shop__description h1,
        .responsiville .nvm-shop__description h2 {
            margin: 0 0 20px;
            color: var(--nvm-color-ink);
            font-size: clamp( 26px, 2.5vw, 36px );
            font-weight: 700;
            line-height: 1.5;
            text-align: left;
        }

        .responsiville .nvm-shop__description h3,
        .responsiville .nvm-shop__description h4 {
            margin: 0 0 25px;
            color: var(--nvm-color-ink);
            font-size: clamp( 18px, 1.39vw, 20px );
            font-weight: 700;
            line-height: 1.5;
        }

        /*
            The closing text is set in Hauora Light.

            The artboard reports 400 on these paragraphs, but read at size on
            the page it sits heavier than the drawing does — so 300 is the
            deliberate choice and not a slip. Everything above it keeps its
            weight: the heading stays bold, and only the running text thins.
        */

        .responsiville .nvm-shop__description p,
        .responsiville .nvm-shop__description li {
            margin: 0;
            color: var(--nvm-color-ink);
            font-size: 16px;
            font-weight: 300;
            line-height: 1.5;
        }

        .responsiville .nvm-shop__description p + p {
            margin-top: 1.5em;
        }

        /*
            The opening paragraph is set larger and left at the ordinary
            weight, with a wider gap before the body begins.

            Size alone, no bolding: it is a first line rather than a heading,
            and it stays the editor's plain paragraph — so the description can
            be written and rewritten in the admin without a field of its own
            and without the first line turning heavy against its author's
            intention.
        */

        .responsiville .nvm-shop__description-text > p:first-child {
            font-size: clamp( 18px, 1.39vw, 20px );
            font-weight: 300;
            line-height: 1.5;
        }

        .responsiville .nvm-shop__description-text > p:first-child + p {
            margin-top: clamp( 30px, 4.17vw, 60px );
        }



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

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

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



    /*
        Nothing matched the filters.

        WooCommerce draws this as its own notice and the theme had never said
        otherwise: a grey-lilac panel, #515151 text, a three-pixel #1e85be
        rule across the top and a blue information icon — measured on the
        page. None of those four colours exists anywhere else on this site,
        so an empty result looked like a message from a different program.

        It is a sentence, not an alert. Nobody has done anything wrong and
        there is nothing to acknowledge, so the panel, the rule and the icon
        all go and the sentence is left on the page's own ground, centred,
        in the ink everything else is set in.

        Scoped to the empty-results case. The other WooCommerce notices —
        added to cart, coupon applied, a checkout error — are saying different
        things in different places, and quietly restyling all of them from
        here is how a cart error stops looking like an error.
    */

    .responsiville .woocommerce-no-products-found .woocommerce-info {
        padding: clamp( 40px, 4vw, 70px ) 0;
        border: none;
        background: none;
        color: var(--nvm-color-ink);
        font-size: clamp( 18px, 1.4vw, 22px );
        line-height: 1.5;
        text-align: center;
    }

        /* The blue information mark. It is drawn with a font icon in a
           ::before, so there is nothing to recolour — it is simply not
           wanted. */

        .responsiville .woocommerce-no-products-found .woocommerce-info::before {
            display: none;
        }



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

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

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



    /*
        The strip of subcategories above a category's products.

        It is built out of the products carousel — same class names, same
        data attributes, same arrows — so products-carousel-script.js drives
        it with nothing added to that file. Everything below is the part that
        differs: a strip of small square cards rather than a band of product
        cards under a heading.

        .nvm-subcategories is on the same element as .nvm-products-carousel,
        so these rules need no more weight than the ones they override,
        except where the original is written with the class twice.
    */

    /*
        Lined up with the grid underneath, not with the carousels on the home
        page.

        The products carousel is built to bleed: it is inset on the left by
        --nvm-content-inset and runs off the right edge of the screen, so the
        last card is cut and the band reads as continuing. That is right on
        the home page, where nothing sits under it.

        Here something does, and only one edge of it matters. The strip
        stands directly above the product grid, so its left edge is taken
        from --nvm-shop-inset, the same figure the grid uses — it was ten
        pixels out before, which is the kind of difference that reads as a
        mistake without anyone being able to say why.

        The right edge keeps running off the screen. That was asked for and
        it is the better behaviour anyway: the cut card is what says there is
        more to the right, which matters here more than on the home page,
        because a category can have nine children and show seven.
    */

    .responsiville .nvm-products-carousel.nvm-subcategories {
        /* The band above is a full-width photograph and the strip reads as
           part of it when they are close. Room enough to separate them, and
           it grows with the page: 36 on a phone, 60 at 1440, 70 and no more
           beyond that. */
        padding-top: clamp( 36px, 4.17vw, 70px );
        padding-bottom: 10px;
        padding-left: var(--nvm-shop-inset);
        padding-right: 0;
    }

        /*
            The arrows sit alone on their row, where the products carousel has
            a title and a description beside them. Right aligned, which is
            where they already are — only the row around them is new.
        */

        /*
            The arrows sit under the row, at its right.

            Above it is the band this strip sits directly beneath, and the
            top right belongs to something else: .nvm-offer-sticker is pinned
            to right: 0 at the height of the header plus 17.2vw, which lands
            on this row, and the arrows were underneath it. A control that
            cannot be pressed is not a control, and the sticker is not ours
            to move.

            Below the cards there is no such argument. The sticker ends well
            above, the eye going down the page meets the arrows between the
            row they move and the products they do not, and the right is
            where this design puts the controls of every other carousel —
            so they keep the place they are expected in.

            The inset is stated because the section's own right padding is
            zero: the cards bleed off the screen deliberately and the arrows
            must not, so they stop on the line the grid below stops on.

            They follow the cards in the markup as well as on the screen, so
            that tabbing through the page reaches them in the order it shows
            them.
        */

        /*
            The strip's heading.

            Smaller than the one the products carousel draws — that is a
            section title on a page of sections, at up to 50px, while this
            sits a few pixels under the category's own name and introduces a
            row of small cards. Two thirds of it reads as a label rather than
            a second headline.

            No padding of its own: the section already carries
            --nvm-shop-inset on its left, which is the line the product grid
            below starts on, so the heading lands on it without being told.

            The .nvm-subcategories prefix is not decoration —
            theme.typography.css carries `.responsiville h2` at one class
            plus one element, which would outrank a lone class here.
        */

        .nvm-subcategories .nvm-subcategories__title {
            margin: 0 0 clamp( 14px, 1.25vw, 24px );
            font-size: clamp( 20px, 1.67vw, 32px );
            font-weight: 800;
            line-height: 1.1;
            color: var(--nvm-color-ink);
        }

        .nvm-subcategories__head {
            display: flex;
            flex-direction: row;
            align-items: center;
            justify-content: flex-end;
            padding-right: var(--nvm-shop-inset);
            margin-top: 14px;
        }

        /*
            Nothing to scroll, no arrows.

            products-carousel-script.js already decides this — a row with no
            more cards than fit is laid out static and the arrows are given
            the hidden attribute. The attribute was doing nothing: a browser
            hides [hidden] with display: none from its own stylesheet, and
            any author rule beats that whatever its specificity, so the
            display: flex these buttons are built with kept them on the page.
            Three categories under Lighting, two live arrows above them, and
            neither would move.

            The same is true of every carousel in the theme, not only this
            one, but the rule is kept to this strip rather than fixed at the
            source: the pages the others are on have been signed off as they
            stand, and a control quietly disappearing from them is not a
            change to make on the way past.

            :has() takes the gap with them. Without it the empty row still
            holds its margin — fourteen pixels of nothing, which is a
            tolerable way for an old browser to be wrong.
        */

        .nvm-subcategories .nvm-products-carousel__arrow[hidden] {
            display: none;
        }

        .nvm-subcategories__head:has( .nvm-products-carousel__arrow[hidden] ) {
            margin-top: 0;
        }

        /*
            The width of a card before the carousel exists.

            products-carousel-style.css gives every slide `flex: 0 0 345px`,
            which is the width of a product card, and Slick overrules it with
            its own measurement once it has initialised. That works for the
            block it was written for, where 345 is the answer both before and
            after. Here it is not: these cards are 7.5 to a row, so the first
            paint drew them at a product's width — four enormous squares — and
            they snapped down to size the moment the script ran. On a reload
            it read as the strip briefly turning into the carousel below it.

            So the pre-init width is stated here too, from the same custom
            properties the markup already carries, and the two paints agree.

            The `:not( .slick-initialized )` is what keeps this out of the
            way afterwards: once Slick owns the track it must own the widths
            as well, and a rule still claiming a flex-basis would fight the
            measurement it writes on each slide.
        */

        .nvm-subcategories .nvm-products-carousel__track:not( .slick-initialized ) > .nvm-products-carousel__slide {
            flex: 0 0 calc( 100% / var(--nvm-carousel-cols-mobile, 2.5) );
            max-width:   calc( 100% / var(--nvm-carousel-cols-mobile, 2.5) );
        }

        /*
            Lighter arrows, because this row is lighter than the one they
            were drawn for.

            The carousel's own arrows are 48px discs filled with ink, and
            they earned that: on the home page they sit beside a heading and
            a paragraph, above cards 345 wide, and the complaint that led to
            the fill was that bare chevrons did not read as controls at all.

            None of that holds here. The cards are a third of the width, the
            row has no heading, and two solid black circles over it were the
            heaviest thing on the page — the controls outweighed what they
            controlled.

            So the fill becomes an outline and the disc comes down to 34. The
            edge is what says a thing can be pressed, which was the original
            finding, and an outline is still an edge. Gold on hover, as
            everywhere else, now carried by the border and the chevron
            together rather than by a block of colour.

            The optical nudge of the chevron is kept and scaled with the
            circle: the triangle's weight sits toward its base at any size.
        */

        .responsiville .nvm-subcategories .nvm-products-carousel__arrow {
            width: 34px;
            height: 34px;
            border: 1px solid var(--nvm-color-stone);
            background: none;
            color: var(--nvm-color-ink);
            transition: border-color 0.2s ease-in-out, color 0.2s ease-in-out;
        }

        .responsiville .nvm-subcategories .nvm-products-carousel__arrow:hover,
        .responsiville .nvm-subcategories .nvm-products-carousel__arrow:focus {
            border-color: var(--nvm-color-gold);
            background: none;
            color: var(--nvm-color-gold);
        }

            .nvm-subcategories .nvm-products-carousel__arrow svg {
                width: 7px;
                height: 14px !important;
            }

            .nvm-subcategories .nvm-products-carousel__arrow--prev svg {
                transform: translateX( -1.5px );
            }

            .nvm-subcategories .nvm-products-carousel__arrow--next svg {
                transform: translateX( 1.5px );
            }

        .nvm-subcategories .nvm-products-carousel__arrows {
            gap: 10px;
        }

        .nvm-subcategories__card {
            display: block;
            text-decoration: none;
            color: var(--nvm-color-ink);
        }

            .nvm-subcategories__card .image-box {
                margin-bottom: 6px;
                background: var(--nvm-color-sand-dark);
            }

            /*
                The picture is the only thing that moves. The design does the
                same on the product cards, and doing it differently here
                would read as two components rather than one shop.
            */

            .nvm-subcategories__card .image-box img {
                transition: transform 0.4s ease-in-out;
            }

            .nvm-subcategories__card:hover .image-box img {
                transform: scale( 1.04 );
            }

            .responsiville .nvm-subcategories__name {
                display: block;
                font-size: 11px;
                font-weight: 700;
                line-height: 1.3;
                text-align: center;
                text-transform: uppercase;
            }

    /*
        Written small first, and that is not a preference.

        Responsiville puts its breakpoint classes on <html> and they are
        cumulative: .small is there at every width, so a rule written under
        .small for phones wins on a desktop too. The phone values are the
        base ones above, and the wider screens add to them from here down.
    */

    .tablet .nvm-subcategories .nvm-products-carousel__track:not( .slick-initialized ) > .nvm-products-carousel__slide {
        flex-basis: calc( 100% / var(--nvm-carousel-cols-tablet, 4.5) );
        max-width:  calc( 100% / var(--nvm-carousel-cols-tablet, 4.5) );
    }

    .laptop .nvm-subcategories .nvm-products-carousel__track:not( .slick-initialized ) > .nvm-products-carousel__slide {
        flex-basis: calc( 100% / var(--nvm-carousel-cols-desktop, 7.5) );
        max-width:  calc( 100% / var(--nvm-carousel-cols-desktop, 7.5) );
    }

    .tablet .nvm-subcategories__card .image-box {
        margin-bottom: 10px;
    }

    .tablet .responsiville .nvm-subcategories__name {
        font-size: 13px;
    }
