/* chrome.css - the ONE owner of the site chrome: the fixed bar, the brand lockup,
   the mobile-menu shell and the footer.

   Both chrome layers used to carry their own copy of these rules with their own
   numbers - site.css for the marketing pages, components.css for the console - so the
   two bars and the two footers drifted apart every time either was touched. They are
   defined once here, and every page loads this file directly after base.css:

       tokens -> base -> chrome -> site | components -> animations -> page

   What stays OUT of this file: the CONTENTS of each menu (marketing links live in
   site.css, console sections in admin.css) and anything page-specific. What lives here
   is what must never differ between the two.

   The chrome does not read .container: its gutter is --chrome-pad-x, so a page that
   redefines the container width (index.css does) cannot move the bar or the footer. */

/* ---------- the gilded rule ---------- */
/* ONE gradient, one owner, every edge that closes a piece of chrome: the bottom of both
   fixed bars and the top of the footer, on the marketing pages and in the console alike.
   It is declared as a token in base.css and applied through border-image on a
   TRANSPARENT 1px border, so it replaces the plain rule that used to sit on the same edge
   instead of stacking a second line, and it keeps the border's exact box - no element
   grows by a pixel. The gradient fades to nothing at both ends, so the line reads as a
   highlight across the middle of the page rather than a frame.
   A page must not restate it: a second copy is how the console and the marketing pages
   drifted apart in the first place. */

/* ---------- fixed nav bar (markup: partials/header.html) ---------- */
/* Everything here is keyed on the CLASS .site-nav, never on the bare `nav` element:
   both bars wear it, and a future <nav> anywhere on the site must not silently become a
   fixed bar. The two do not even agree on the tag - the marketing bar is the <nav> from
   the partial, the console's is a <header> that CONTAINS its section <nav> - and the
   class is what makes them the same chrome regardless. */
/* The bar and the mobile menu's top bar are the SAME bar in two states, so their
   geometry and skin live in one rule: opening the menu must not move the brand or
   the tap target by a pixel. --chrome-tap sizes both the burger and the close box. */
/* Geometry and motion come from the shared chrome contract in base.css: the console
   renders its own bar from admin.css and the two must not drift apart. Directions use
   different curves - things that leave accelerate out, things that arrive decelerate
   in - and the nav takes its time coming back, since a bar that snaps into place reads
   as a jolt at the top of the viewport. */
/* The console's header wears .site-nav too, so it takes this skin from the same
   selector the marketing bar does. It must NOT be moved onto an inner wrapper: the
   bar's padding belongs to the bar, so a skin on the inner paints a band shorter than
   the bar it sits in - which is exactly how the console ended up with a 49px header
   floating inside an 89px bar on a phone while the marketing one painted all 89. That
   is also why the console keeps its section navigation INSIDE this element rather than in
   a band of its own (admin.css): the whole header stays one surface, one rule, one
   measured height. */
.site-nav,.mob-topbar{
    display:flex;align-items:center;justify-content:space-between;
    padding:var(--chrome-pad-y) var(--chrome-pad-x);
    backdrop-filter:blur(10px);background:var(--chrome-bg);
    border-bottom:1px solid transparent;border-image:var(--chrome-rule) 1}
.site-nav{position:fixed;top:0;left:0;right:0;z-index:50;
    transition:transform var(--nav-in) var(--ease-out),border-color .4s,background .4s}
/* .scrolled only DARKENS - the rule is already there at rest, so re-declaring a
   border here would stack a second line and grow the bar by a pixel. */
.site-nav.scrolled{background:var(--chrome-bg-scrolled)}
/* Retracted bar (behaviour: site.js and the console shell, at EVERY width). This rule is
   the single owner of the nav transition - a page override must not redeclare it, or the
   transform stops animating on that page. Directions differ on purpose: leaving uses the
   accelerating curve and the shorter duration, returning the decelerating one, so the bar
   gets out of the way promptly and comes back without snapping. */
.site-nav.nav-hidden{transform:translateY(-100%);transition:transform var(--nav-out) var(--ease-in),border-color .4s,background .4s}
@media(prefers-reduced-motion:reduce){.site-nav,.site-nav.nav-hidden{transition:none}}
/* .nav-top is the console's CHROME row - brand, bell, account menu, burger - the exact
   counterpart of the marketing bar's single row. It is a wrapper rather than the bar
   itself for two reasons: the console's controls need a gap the marketing bar does not
   have, and the console puts its section navigation INSIDE this row, between the brand
   and its actions, so the row must be a box of its own to keep its height and its
   centring whatever the navigation beside it does. Everything about that navigation -
   existence, layout, column count, when it takes a further row - is admin.css's; this
   file never learns how many sections the console has. */
.site-nav .nav-top{display:flex;align-items:center;gap:18px;flex:1 1 auto}
/* ONE row height for both bars, and the reason the brand sits at the same y on every
   page: the brand line never goes below the tap target, because it carries the burger
   on a phone and the bell + the account menu in the console. The padding and the
   centring were already shared - only this floor was not, so the console's row was 48
   and the marketing one whatever its links happened to measure (41), which put the
   console's brand 3.5px lower on desktop. Two names for one row, like .brand/.logo:
   .nav-links on the marketing bar, .nav-top in the console. A floor on the <nav> itself
   could not do this - box-sizing is border-box, so it would count the padding. */
.nav-links,.site-nav .nav-top{min-height:var(--chrome-tap)}
/* The footer's WIDTH and gutter are the chrome's, not the page's. Setting only the
   gutter was not enough: the marketing home widens .container to 1180px for its hero,
   and with no max-width of its own here the footer inherited that on the home page and
   the shared 1120px everywhere else - a 30px step per side between the home footer and
   every other one. Both halves are declared now, so no page layer can move the footer:
   this selector (0,1,1) outranks a page's plain .container (0,1,0) whatever the load
   order. */
footer>.container{max-width:var(--chrome-footer-max);padding-inline:var(--chrome-pad-x)}
/* Two names for one thing: the marketing bar calls it .brand, the console .logo. */
.brand,.logo{font-family:var(--serif);font-weight:500;letter-spacing:.18em;font-size:1.2rem;text-transform:uppercase;color:var(--ink);text-decoration:none}
.brand span,.logo span{color:var(--gold)}
/* Two-line lockup, worn by the nav and the mobile-menu top bar; the page brands
   (booking, pay, team) and the footer stay single-line. Sized to fit the bar's
   existing height. The second line is tracked to end exactly where ELYSIUM ends:
   size and tracking were fitted together against the rendered width, and the
   negative margin cancels the trailing letter-spacing, which is added after the
   last letter too. */
/* Worn by the marketing bar (.brand) and the console bar (.logo) alike. */
.brand-lockup{line-height:1.06}
.brand-lockup span{display:block;font-size:.65em;letter-spacing:.325em;margin-right:-.325em;margin-top:3px}

/* ---------- back-to-top (behaviour: shared-ui.js initScrollTop) ---------- */
/* Here rather than in components.css or site.css because BOTH chromes show it and
   neither loads the other's file: the two copies had already drifted apart - different
   offset, shadow and icon size - and only the marketing one had the touch fix, so the
   console's button stayed lit after every tap. Hover is guarded; the press feedback a
   finger needs comes from :active and from the .pressed class the script holds briefly,
   because the button scrolls away from under the finger. */
.to-top{position:fixed;right:24px;bottom:24px;z-index:var(--z-top);width:48px;height:48px;border-radius:50%;
  cursor:pointer;background:var(--panel);border:1px solid var(--line);color:var(--gold);
  display:flex;align-items:center;justify-content:center;box-shadow:var(--shadow-1);
  opacity:0;visibility:hidden;transform:translateY(10px);
  transition:opacity .3s,transform .3s,visibility .3s,background .3s,border-color .3s}
.to-top.show{opacity:1;visibility:visible;transform:translateY(0)}
@media(hover:hover) and (pointer:fine){.to-top:hover{background:var(--gold);color:var(--bg);border-color:var(--gold)}}
.to-top:active,.to-top.pressed{background:var(--gold);color:var(--bg);border-color:var(--gold)}
.to-top svg{width:22px;height:22px;fill:currentColor}
@media(max-width:600px){.to-top{right:18px;bottom:18px;width:44px;height:44px}}

/* ---------- mobile menu (markup: partials/header.html; behaviour: site.js) ---------- */
.burger{display:none;flex-direction:column;justify-content:center;align-items:center;
  gap:6px;width:var(--chrome-tap);height:var(--chrome-tap);background:none;border:none;cursor:pointer;padding:0;-webkit-tap-highlight-color:transparent}
.burger span{display:block;width:26px;height:2px;background:var(--ink);border-radius:1px}
/* Overlay + panel: the panel slides in from the right while the overlay fades in.
   visibility carries a delay so the closing slide finishes before the menu stops
   being hit-testable - display/opacity alone would cut the transition short. */
.mob-menu{position:fixed;inset:0;z-index:200;display:flex;justify-content:flex-end;
  background:rgba(8,7,6,.66);opacity:0;visibility:hidden;
  transition:opacity var(--menu-out) var(--ease-standard),visibility 0s linear var(--menu-out)}
.mob-menu.open{opacity:1;visibility:visible;
  transition:opacity var(--menu-in) var(--ease-settle),visibility 0s}
.mob-panel{display:flex;flex-direction:column;width:min(480px,100%);height:100%;
  background:var(--bg);transform:translateX(100%);
  transition:transform var(--menu-out) var(--ease-standard)}
.mob-menu.open .mob-panel{transform:none;transition:transform var(--menu-in) var(--ease-settle)}
@media(prefers-reduced-motion:reduce){
  .mob-menu,.mob-menu.open,.mob-panel,.mob-menu.open .mob-panel{transition:none}
}
body.menu-open{overflow:hidden}
.mob-topbar{flex:0 0 auto}
.mob-close{width:var(--chrome-tap);height:var(--chrome-tap);display:flex;align-items:center;justify-content:center;
  background:none;border:none;cursor:pointer;position:relative;-webkit-tap-highlight-color:transparent}
.mob-close::before,.mob-close::after{content:'';position:absolute;width:28px;height:2px;
  background:var(--ink-soft);border-radius:1px;transition:background .2s}
.mob-close::before{transform:rotate(45deg)}
.mob-close::after{transform:rotate(-45deg)}
@media(hover:hover) and (pointer:fine){.mob-close:hover::before,.mob-close:hover::after{background:var(--gold)}}
.mob-close:active::before,.mob-close:active::after{background:var(--gold)}

/* The menu's ITEM LIST - one type, one rhythm, one set of rules for both chromes.
   The two were separate copies with separate numbers (site.css for the marketing menu,
   components.css for the console) and they drifted exactly as the bars and the footers
   had: on a phone the console rendered its items at 27.3px on a 60px pitch against the
   marketing menu's 25.6px on 44.1px, so nine console entries read heavier and looser
   than six marketing ones. The marketing values are the reference.
   Two names for one list, like .brand/.logo: .mob-primary on the marketing menu,
   .mob-nav in the console. What each list CONTAINS stays per layer, and everything
   BELOW it is each layer's own and is deliberately not touched here - the marketing
   CTAs, secondary links, socials and contacts, and the console's account block. */
.mob-body{flex:1 1 auto;overflow-y:auto;-webkit-overflow-scrolling:touch;padding:4px 28px 48px}
.mob-primary,.mob-nav{list-style:none;margin-bottom:28px}
/* display:block rather than flex: the marketing menu is the reference and renders its
   items as blocks, and a flex box builds its line box differently enough to shift the
   pitch. width/text-align are what a <button> needs to sit like the <a> beside it. */
.mob-primary li a,.mob-nav li a,.mob-nav li button{
  display:block;width:100%;text-align:left;background:none;border:none;
  font-family:var(--serif);font-weight:300;font-size:clamp(1.85rem,8vw,3rem);
  color:var(--ink);text-decoration:none;padding:11px 0;line-height:1.1;
  border-bottom:1px solid var(--line-soft);cursor:pointer;transition:color .2s}
/* The top bar already rules off above the first item; a second line right under it read
   as a double rule. Transparent rather than removed, so the item keeps its position at
   both padding values. */
.mob-primary li:first-child a,.mob-nav li:first-child a,.mob-nav li:first-child button{
  border-top:1px solid transparent}
@media(hover:hover) and (pointer:fine){
  .mob-primary li a:hover,.mob-nav li a:hover,.mob-nav li button:hover{color:var(--gold)}}
.mob-primary li a:active,.mob-nav li a:active,.mob-nav li button:active{color:var(--gold)}
@media(max-width:760px){
  .mob-body{padding:2px 28px 28px}
  .mob-primary,.mob-nav{margin-bottom:18px}
  .mob-primary li a,.mob-nav li a,.mob-nav li button{font-size:1.6rem;padding:7px 0}
}

/* The footer sets its OWN line-height instead of inheriting the page's body copy.
   Every spacing value in here was already shared, yet the marketing footer stood
   18px taller than the console's: site.css sets body{line-height:1.6} and the console
   has no such rule, so the brand, the licensed line and the bottom row grew on one
   layer and not the other. `normal` is what the console renders, and the console is
   the reference - now every page gets that rhythm and no page layer can shift it.
   .foot-contact keeps its own 1.9: that one IS a deliberate value. */
/* The footer renders the same on every page because it takes NOTHING from the page's
   own typography or decoration:
     line-height - site.css sets body{line-height:1.6} and the console does not;
     font-weight - site.css sets body{font-weight:300} and the console does not, which
       is why the same colours read pale on the marketing pages and solid in the
       console: every line of the footer was rendered a weight lighter there;
     stacking   - site.css paints two FIXED decorative layers at z-index 0 (a gold
       radial wash and a 3.5% noise grain). A static footer is in-flow content, so
       positioned layers paint OVER it - the grain was literally on top of the footer's
       text and social icons on every marketing page, and login.css had a local
       footer{position:relative;z-index:1} to escape exactly that. The chrome owns it
       now, so no page needs its own copy.
     background  - lifting the footer stopped the layers painting OVER it, but a
       transparent footer still let them show THROUGH: measured against the console,
       99.1% of the footer's pixels differed, mean 4.8/255. It carries the page
       background itself now, so the decoration ends at its top rule (where a rule
       already is) and the strip is the same surface everywhere - 0.2% of pixels, max
       delta 2, which is antialiasing.
   The console is the reference: 400, normal, flat, and nothing painted over it. */
/* ---------- skip link ---------- */
/* Off-screen, not hidden: `display:none` and `visibility:hidden` remove it from the
   tab order, which is the one thing it exists to be in. It returns on :focus-visible
   and sits ABOVE the fixed bar (z-index 50) and BELOW the mobile menu (200), or it
   would come back underneath the thing it skips. */
.skip-link{position:fixed;top:0;left:0;z-index:150;transform:translateY(-120%);
  padding:12px 20px;border-radius:0 0 8px 0;background:var(--panel);color:var(--ink);
  border:1px solid var(--gold);border-top:0;text-decoration:none;font-size:.9rem;
  transition:transform var(--dur) var(--ease-standard)}
.skip-link:focus-visible{transform:translateY(0);outline:2px solid var(--gold);
  outline-offset:-4px}
@media(prefers-reduced-motion:reduce){.skip-link{transition:none}}

/* The footer opens on the same gilded rule the bars close on - it is the one line that
   separates the page from its chrome, so it is the same line. border-image paints the
   gradient on the transparent top border; the 1px box is unchanged, so none of the
   whole-pixel geometry below moves. */
footer{padding:22px 0 50px;border-top:1px solid transparent;border-image:var(--chrome-rule) 1;
  line-height:normal;font-weight:400;position:relative;z-index:1;background:var(--bg)}
.foot-grid{display:flex;justify-content:space-between;flex-wrap:wrap;gap:30px;align-items:flex-end}
/* Explicit line-heights: with `normal` the BOX height comes from the face's own
   metrics, so a font that has not loaded yet (or falls back) changes the height of
   this column - and because .foot-grid is bottom-aligned, that moves the social
   icons AND the contact lines together.

   WHOLE PIXELS, not ratios: a page's total height decides the sub-pixel phase the
   footer starts on (measured: 0.609 on the marketing home, 0 in the console), and box
   edges snap to device pixels while glyph baselines do not. With fractional box
   heights inside - 13.984 for this line, 27.36 per contact line - the two round apart
   and the text reads a hair off against the circles, differently per page. Integer
   boxes cannot: whatever phase the footer lands on, everything inside it shifts by the
   same amount. The values are what the loaded faces render today. */
.foot-brand{font-family:var(--serif);font-size:1.7rem;font-weight:400;letter-spacing:.1em;line-height:34px}
.foot-brand span{color:var(--gold)}
/* The credentials line is small uppercase text, so it takes the 4.5:1 floor like any
   other body copy. At the .45 gold it shipped with it measured 2.55:1 - technically a
   whisper, in practice unreadable for a lot of people. .75 measures 5.05:1 and keeps
   it quieter than the brand above it, which is the effect the .45 was reaching for. */
.foot-licensed{font-size:.68rem;letter-spacing:.15em;text-transform:uppercase;color:rgba(201,165,88,.75);margin-top:7px;line-height:14px}
.foot-contact{text-align:right;font-size:.9rem;color:var(--ink-soft);line-height:27px}

/* ---------- accessibility trust marks ---------- */
/* ONE owner for the pair, because they appear in three places (the shared footer, the
   home page trust row and the Accessibility page) and a badge that drifts between them
   stops reading as one claim. It lives in the CHROME rather than in site.css for the
   same reason the footer does: chrome.css is the one stylesheet every page loads, so
   the console footer wears the identical mark without site.css.

   The Elysium mark is TEXT, not an image. A trust badge is a claim about legibility, so
   rendering it as a picture of words would be a small joke at the visitor's expense: as
   text it scales with the page, reflows, survives forced-colors mode and needs no
   font embedded into an asset. The W3C mark next to it stays an <img> because it must
   be the official bytes, unmodified.

   Both boxes are 31px high - the official logo's own height - so the pair sits on one
   line without a wrapper measuring anything. */
.trust-badges{display:flex;flex-wrap:wrap;align-items:center;gap:10px;
  list-style:none;margin:0;padding:0}
.trust-badge{display:inline-flex;align-items:center;height:31px;border-radius:4px;
  border:1px solid var(--line);text-decoration:none;transition:border-color .25s,color .25s}
.trust-badge:focus-visible{outline:2px solid var(--gold);outline-offset:2px}
@media(hover:hover) and (pointer:fine){.trust-badge:hover{border-color:var(--gold)}}
.trust-badge:active{border-color:var(--gold)}
.trust-badge-ada{gap:7px;padding:0 9px;color:var(--ink-soft);background:rgba(201,165,88,.05)}
@media(hover:hover) and (pointer:fine){.trust-badge-ada:hover{color:var(--ink)}}
.trust-badge-ada:active{color:var(--ink)}
/* Tinted with the gold rather than drawn in it: the glyph is a mask, so one data URI
   serves every state and the colour is the one CSS decides. */
.trust-badge-mark{flex:0 0 auto;width:15px;height:15px;background-color:var(--gold);
  -webkit-mask:var(--icon-access) center/contain no-repeat;
  mask:var(--icon-access) center/contain no-repeat}
/* Two lines inside 31px, so the wording is the badge rather than a caption beside it.
   Whole-pixel line boxes for the same reason every other footer box has them. */
.trust-badge-text{display:flex;flex-direction:column;justify-content:center;
  font-size:.58rem;line-height:10px;letter-spacing:.1em;text-transform:uppercase}
.trust-badge-text b{color:var(--gold);font-weight:600;letter-spacing:.16em}
/* line-height:0 leaves no text baseline under the logo, so the 31px image is the whole
   box and the two badges align on the same edge. */
.trust-badge-w3c{line-height:0;overflow:hidden}
.trust-badge-w3c img{display:block;width:88px;height:31px}
/* In the footer the marks sit under Licensed - Bonded - Insured, in the brand column,
   and they are the only thing there that must not stretch the column on a phone. */
.foot-trust{margin-top:14px}
.foot-contact a{color:var(--ink);text-decoration:none}

/* ---------- contact lines: phone / email / hours ---------- */
/* The footer's contact column and the mobile menu's contact block render the SAME two
   SSI fragments, so they are styled together here and keyed on what the fragment
   actually produces - an <a href="tel:">, an <a href="mailto:"> and a <span> for the
   hours - rather than on classes the fragment cannot carry. That also means the STUB
   markup (the degraded, backend-unreachable path) is decorated identically, without a
   second copy of anything.
   The glyph is a MASK tinted with currentColor, so it is always exactly the ink of the
   line it belongs to, including the hover colour, and it is sized in em so it tracks the
   line's own type. It is decorative: the phone number, the address and the hours read
   themselves, so nothing here needs an accessible name. */
.foot-contact a,.foot-hours>span,.mob-contact a,.mob-hours>span{
  display:inline-flex;align-items:center;gap:6px}
.foot-contact a[href^="tel:"],.mob-contact a[href^="tel:"]{--contact-icon:var(--icon-phone)}
.foot-contact a[href^="mailto:"],.mob-contact a[href^="mailto:"]{--contact-icon:var(--icon-mail)}
.foot-hours>span,.mob-hours>span{--contact-icon:var(--icon-clock)}
.foot-contact a::after,.foot-hours>span::after,
.mob-contact a::after,.mob-hours>span::after{
  content:"";flex:0 0 auto;width:1em;height:1em;background-color:currentColor;
  -webkit-mask:var(--contact-icon) center/contain no-repeat;
  mask:var(--contact-icon) center/contain no-repeat}
/* WHICH SIDE follows the alignment, not the element: the glyph closes a right-aligned
   line and opens a left-aligned one. The pseudo-element is always the last child, so
   reversing the row is what moves it to the front - no second rule and no second glyph.
   The footer is right-aligned until 600px (its own rule below) and the mobile menu is
   left-aligned always, so the menu takes the reversed order at every width. */
.mob-contact a,.mob-hours>span{flex-direction:row-reverse}
@media(max-width:600px){.foot-contact a,.foot-hours>span{flex-direction:row-reverse}}
.foot-link{color:inherit;text-decoration:none;transition:color .25s}
@media(hover:hover) and (pointer:fine){.foot-link:hover{color:var(--ink-soft)}}
.foot-link:active{color:var(--ink-soft)}
/* 27px above the rule as well as below it, measured to the visible edge of the
   social pills - their bordered circle is what the eye reads, not the glyph inside. */
.foot-bottom{margin-top:27px;padding-top:24px;border-top:1px solid var(--line-soft);font-size:.78rem;
  line-height:18px;color:var(--ink-dim);display:flex;justify-content:space-between;flex-wrap:wrap;gap:12px}
@media(min-width:821px){.foot-bottom{font-size:.84rem}.foot-link{margin:0 3px}}
/* The legal/company links are a NAMED navigation landmark, not a run of links in a
   span: there are seven documents now, and they should be reachable as one group. The
   separator dots are gone with the change - a flex gap does the same visual job
   without putting a decorative character into the reading order, and it is what lets
   the row wrap cleanly on a phone instead of stranding a dot at the end of a line.
   The desktop margin above would otherwise stack on top of that gap. */
.foot-nav{display:flex;flex-wrap:wrap;column-gap:16px;row-gap:6px;justify-content:flex-end}
.foot-nav .foot-link{margin:0}
@media(max-width:600px){.foot-nav{justify-content:flex-start}}
@media(max-width:600px){.foot-contact{text-align:left}}
.socials{display:flex;gap:14px;margin-top:18px}
/* The glyph is centred by the flex box and by NOTHING inherited: line-height:0 leaves
   no text baseline in the circle for it to sit on, and the svg is block-level in its
   own right rather than relying on being blockified as a flex item. Both are belt and
   braces on purpose - this is the one place where a stray inherited line-height would
   drop every icon a pixel or two below the centre, and the two chrome layers do not
   share a body typography. */
.socials a{width:42px;height:42px;display:flex;align-items:center;justify-content:center;
  line-height:0;border:1px solid var(--line);border-radius:50%;color:var(--ink-soft);transition:all .3s}
@media(hover:hover) and (pointer:fine){.socials a:hover{border-color:var(--gold);color:var(--gold);transform:translateY(-2px)}}
.socials a:active{border-color:var(--gold);color:var(--gold)}
/* 20px, not 19: the circle's content box is 40px (42 minus its border), so an odd
   glyph leaves 10.5px on each side - the one fractional relationship left inside the
   icon. The border is painted on the box and snaps to the device grid, the glyph is
   rasterized at its own offset, so that half pixel let them round apart whenever the
   footer landed on a different sub-pixel phase - which every page has its own of, and
   the console's changes with its data. An even glyph makes the gap exactly 10px and
   the relationship integral at any phase and any DPR. */
.socials svg{display:block;flex:0 0 auto;width:20px;height:20px;fill:currentColor}
/* Who shows the burger and when the menu exists at all - the same answer on both
   chromes, so neither can end up with a burger and no menu behind it. */
@media(max-width:760px){.burger{display:flex}}
@media(min-width:761px){.mob-menu{display:none!important}}
