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

    ███╗   ███╗███████╗███╗   ██╗██╗   ██╗███████╗
    ████╗ ████║██╔════╝████╗  ██║██║   ██║██╔════╝
    ██╔████╔██║█████╗  ██╔██╗ ██║██║   ██║███████╗
    ██║╚██╔╝██║██╔══╝  ██║╚██╗██║██║   ██║╚════██║
    ██║ ╚═╝ ██║███████╗██║ ╚████║╚██████╔╝███████║
    ╚═╝     ╚═╝╚══════╝╚═╝  ╚═══╝ ╚═════╝ ╚══════╝
                                                                                        
 *****************************************************/


    /* Make links non clickable in backend. */

    .is-root-container .nvm-menu a {
        pointer-events: none;
    }

    .nvm-menu a,
    .nvm-menu a:hover {
        text-decoration: none !important;
        border: none !important;
        color: var(--nvm-color-text);
    }
    
    .nvm-menu-in-content li {
        list-style-type: disc;
    }

    .nvm-menu-in-content li {
        margin-left: 1em;
    }



    /* The 404 page lays this menu out in columns across the grid, as the design
       does, instead of running it down the left.

       Multi-column is used rather than a flex row because the block renders
       whatever menu is assigned to it, and the menus here are nested three
       levels deep. A flex row would make one column per top level item, which
       is a single column when the menu hangs off one category. Flowing the
       whole list instead fills the columns evenly whatever its shape.

       The columns go on the outer list only. Set on `ul` they would have
       applied to every sub-menu too, and each nested list would have started
       columns of its own.

       Leaf items are kept whole; the groups above them may break, which is what
       lets the columns balance. The breakpoint classes are cumulative, so these
       go narrowest first and the later rule wins wherever it applies.

       `display: block` is the load bearing line. menu-render.php puts a
       `navigation` class on the nav, and responsiville.moressette.css gives
       `.navigation ul` `display: flex`. A flex container ignores `columns`
       outright, so the rules below did nothing at all until the list was put
       back to a block box. */

    /* The artboard leaves 60px between the title above and the first row. The
       title carries part of that in its own bottom margin; this makes up the
       rest. */

    .error404 .nvm-menu {
        margin-top: 30px;
    }

    .error404 .nvm-menu > div > ul {
        display: block;
        columns: 1;
        margin: 0;
        padding: 0;
    }

    .tablet .error404 .nvm-menu > div > ul {
        columns: 2;
        column-gap: 40px;
    }

    .laptop .error404 .nvm-menu > div > ul {
        columns: 4;
        column-gap: 60px;
    }

    /* The block's own `.nvm-menu-in-content li` gives every item a disc and a
       1em indent, which steps each level further in. The design has neither. */

    .error404 .nvm-menu li {
        list-style-type: none;
        margin: 0 0 30px;
    }

    /* 18px on a 24.6px line, 30px between entries, straight from the artboard.
       The bottom margin goes on every item: where one holds a sub-menu, its own
       margin collapses with that of the sub-menu's last child, so the rhythm
       stays at 30px instead of doubling at the end of a group. */

    .error404 .nvm-menu a {
        font-size: 18px;
        line-height: 25px;
    }

    .error404 .nvm-menu .sub-menu {
        display: block;
        margin: 0;
        padding: 0;
    }

    .error404 .nvm-menu .sub-menu li {
        break-inside: avoid;
    }
