/* 30 — My Year in Downtown L.A. — standalone archive page.
   Fully self-contained: no shared files with the main site or the other
   three comic readers, per project convention (see DANNY-README.md).
   This is the INDEX/GRID page only — the lightbox modal is a separate,
   later build. */

* {
  box-sizing: border-box;
}

html,
body {
  margin: 0;
  padding: 0;
}

@font-face {
  font-family: "Geared Slab";
  src: url("fonts/gearedslab.woff2") format("woff2");
  font-weight: 400;
  font-style: normal;
  font-display: swap;
}

/* Base tile always covers the whole page. bg_top is layered on top of
   it and repeats ONLY on the x-axis, sitting at the very top — Figma
   couldn't represent single-axis tiling, so this combination (two
   background-image layers, one repeating both ways, one repeating only
   horizontally and pinned to the top) is hand-built rather than copied
   from a Figma export. bg_top is scaled to the same 50% factor Figma
   used for the base tile (200px native -> 100px rendered) so the two
   layers' grain matches; its own height (900px at that scale) is a
   judgment call, not a Figma number — long enough to fade fully into
   the base tile behind the hero. */
body {
  background-color: #0b3350;
  background-image: url("images/design/bg_top.avif"), url("images/design/bg.avif");
  background-repeat: repeat-x, repeat;
  background-position: top left, top left;
  background-size: 100px 900px, 100px 100px;
  font-family: "Bitter", serif;
  color: #000;
}

a {
  color: inherit;
}

button {
  font: inherit;
  color: inherit;
  background: none;
  border: none;
  padding: 0;
  cursor: pointer;
}

.page {
  display: flex;
  flex-direction: column;
  align-items: center;
  gap: var(--page-gap);
  width: 100%;
}

/* ==========================================================
   Scale tiers. Unlike the other three comics, nothing here
   follows a "type jumps at 1024, spacing jumps at 1440" split —
   every value below was read directly off its own breakpoint in
   Figma, tier by tier, since this design doesn't reuse the other
   projects' cascade shape.
   ========================================================== */

.page {
  --page-gap: 36px;
  --hero-main-width: 390px;
  --hero-height: 281px;
  --hero-img-height: 287.73px;
  --hero-pt: 16px;
  --hero-px: 24px;
  --hero-gap: 8px;
  --hero-direction: column;
  /* Fluid instead of a flat mobile value: each scales linearly between
     320px (smallest realistic phone) and 767px (top of this tier,
     right before the row layout takes over at 768px), landing exactly
     on the Figma-spec value at 767px and easing down below it rather
     than jumping. Coefficients solved from (320px -> reduced) and
     (767px -> spec) pairs: num 136->160, heading 20->24, byline 16->18. */
  --hero-num-size: clamp(136px, 118.82px + 5.37vw, 160px);
  --hero-heading-size: clamp(20px, 17.14px + 0.89vw, 24px);
  --hero-byline-size: clamp(16px, 14.57px + 0.45vw, 18px);
  --hero-quote-size: 14px;
  --toggle-text-size: 14px;
  --toggle-label-width: auto;
  --toggle-label-flex: 1 1 0%;
  --subheading-size: 24px;
  --container-padding: 24px;
  --container-max-width: none;
  --grid-gap: 12px;
  --grid-cols: 2;
  --overlay-label-size: 24px;
  --overlay-date-size: 14px;
  --overlay-padding: 16px;
  --credit-line1-size: 16px;
  --credit-line2-size: 12px;
  /* Modal — values read straight off each named Figma breakpoint frame
     (Mobile/Tablet-Portrait/Tablet-Landscape/Desktop Modal), not derived. */
  --modal-overlay-pad-y: 24px;
  --modal-pad-top: 36px;
  --modal-pad-bottom: 24px;
  --modal-pad-x: 0px;
  --modal-pagination-pad-top: 8px;
  --modal-pagination-pad-x: 24px;
  --modal-close-inset: 12px;
  --modal-nav-flex: 1 0 0%;
  --modal-nav-width: auto;
  --modal-date-size: 14px;
  --modal-loader-size: 72px;
}

@media (min-width: 500px) {
  .page {
    --grid-cols: 3;
  }
}

@media (min-width: 768px) {
  .page {
    --hero-main-width: 768px;
    --hero-height: 323px;
    --hero-img-height: 566.61px;
    --hero-pt: 36px;
    --hero-px: 48px;
    --hero-gap: 16px;
    --hero-direction: row;
    --hero-heading-size: 28px;
    --hero-quote-size: 16px;
    --toggle-text-size: 16px;
    --toggle-label-width: 250px;
    --toggle-label-flex: none;
    --subheading-size: 32px;
    --container-padding: 48px;
    --grid-gap: 12px;
    --grid-cols: 4;
    --modal-pad-bottom: 36px;
    --modal-pagination-pad-top: 16px;
    --modal-pagination-pad-x: 0px;
    --modal-nav-flex: none;
    --modal-nav-width: 200px;
    --modal-date-size: 16px;
    --modal-loader-size: 96px;
  }
}

@media (min-width: 1024px) {
  .page {
    --hero-main-width: 900px;
    --hero-height: 350px;
    --hero-img-height: 664px;
    --hero-px: 0px;
    --hero-num-size: 200px;
    --hero-heading-size: 36px;
    --hero-byline-size: 20px;
    --hero-quote-size: 18px;
    --overlay-label-size: 28px;
    --overlay-date-size: 16px;
    --credit-line1-size: 18px;
    --credit-line2-size: 16px;
    --container-max-width: 996px;
    --grid-gap: 16px;
    --grid-cols: 5;
    --modal-overlay-pad-y: 48px;
    --modal-pad-x: 24px;
  }
}

@media (min-width: 1440px) {
  .page {
    --page-gap: 48px;
    --hero-height: 407px;
    --hero-num-size: 250px;
    --hero-byline-size: 24px;
    --toggle-text-size: 18px;
    --subheading-size: 36px;
    --container-padding: 0px;
    --overlay-label-size: 32px;
    --overlay-padding: 24px;
    --grid-cols: 5;
    --modal-pad-top: 48px;
    --modal-pad-bottom: 48px;
    --modal-pad-x: 48px;
    --modal-pagination-pad-top: 24px;
    --modal-close-inset: 16px;
  }
}

@media (min-width: 1920px) {
  .page {
    --toggle-text-size: 20px;
    --container-max-width: 1440px;
    --grid-gap: 20px;
    --grid-cols: 6;
  }
}

/* ==========================================================
   Hero — genuine 3-column layout. The center column is a fixed
   width per tier (390/768/900); the side columns are flex:1 and
   only become visually non-zero once the viewport exceeds that
   fixed width (at exactly 768px and 390px the center IS the full
   viewport, so the sides collapse to 0 on their own — confirmed
   against Figma, which shows no side tiles at those two frames).

   Both the center image and the side tiles are plain CSS
   backgrounds, not <img> tags — this made it possible to size
   them off one shared height variable (--hero-img-height) so
   their scale/grain lines up exactly, per spec. Center is
   width-driven (background-size: 100% var(--hero-img-height)),
   bottom-anchored, clipped by the shorter --hero-height box above
   it. Side tiles repeat-x at that same rendered height — since
   --hero-img-height is always >= --hero-height at every tier
   (by design, matching the "anchored, cropped skyline" look),
   the tile never needs to repeat vertically either.
   ========================================================== */

.hero {
  display: flex;
  align-items: stretch;
  width: 100%;
  position: relative;
}

.hero__tile {
  flex: 1 1 0%;
  min-width: 0;
  background-image: url("images/design/header-tile.avif");
  background-repeat: repeat-x;
  background-position: left bottom;
  background-size: auto var(--hero-img-height);
}

.hero__main {
  flex: 0 0 auto;
  width: 100%;
  max-width: var(--hero-main-width);
  height: var(--hero-height);
  padding: var(--hero-pt) var(--hero-px) 0;
  display: flex;
  flex-direction: var(--hero-direction);
  /* Below 768px .hero__main stacks title-row over quote in a column,
     so align-items is the HORIZONTAL axis here — centered per Figma's
     mobile frame. At 768px+ it switches to a row (title left, quote
     right) where flex-start is the correct cross-axis (vertical) value. */
  align-items: center;
  /* Figma's mobile Header-Main has no space-between — just a plain
     8px gap (var(--hero-gap) at this tier) with content hugging the
     top; space-between here was stretching that gap out to fill the
     whole 281px box and shoving the quote to the very bottom. The
     row layout at 768px+ still wants space-between (title left,
     quote pinned to the far right corner), so it's restored there. */
  justify-content: flex-start;
  gap: var(--hero-gap);
  overflow: hidden;
  position: relative;
  background-image: url("images/design/header.avif");
  background-repeat: no-repeat;
  background-position: center bottom;
  background-size: 100% var(--hero-img-height);
}

.hero__title {
  display: flex;
  align-items: flex-start;
  gap: 16px;
  line-height: 1;
  text-shadow: 1px 1px 0 rgba(255, 255, 255, 0.75);
}

.hero__num {
  margin: 0;
  font-family: "Geared Slab", cursive;
  font-weight: 400;
  font-size: var(--hero-num-size);
  color: #013952;
  line-height: 1;
}

.hero__title-text {
  display: flex;
  flex-direction: column;
  gap: 12px;
  padding-top: 12px;
}

.hero__heading {
  margin: 0;
  font-weight: 400;
  font-size: var(--hero-heading-size);
  color: #000;
  line-height: 1.15;
}

.hero__byline {
  margin: 0;
  font-style: italic;
  font-size: var(--hero-byline-size);
  color: #013952;
}

.hero__quote {
  margin: 0;
  /* No top padding + a pull-up margin instead of clipping .hero__num's
     box: the num's own overflow is left at its default (auto/visible,
     so the "30" doesn't get clipped), and the quote is pulled up
     under the title's baseline to close the gap that leaves instead. */
  margin-top: -1.5rem;
  font-style: italic;
  font-size: var(--hero-quote-size);
  color: #555;
  text-align: center;
  line-height: 1.2;
  text-shadow: 1px 1px 0 rgba(255, 255, 255, 0.75);
  /* Figma breaks this quote to 2 lines in the row (768px+) layout, but
     below that the whole hero is a narrower single column and Danny
     wants it as one line, sitting just under the title instead. */
  white-space: nowrap;
}

.hero__quote p {
  margin: 0;
}

/* The manual <br> in the quote's markup is the 768px+ (row-layout)
   line break; collapsed away below that so the quote reads as one
   line per the mobile spec. */
.hero__quote-break {
  display: none;
}

@media (min-width: 768px) {
  .hero__quote {
    margin-top: 0;
    padding-top: 12px;
    text-align: right;
    white-space: normal;
  }

  .hero__quote-break {
    display: inline;
  }

  .hero__main {
    align-items: flex-start;
    justify-content: space-between;
  }
}

/* ==========================================================
   Toggle. Below 768px the two labels are equal flex:1 boxes
   (text-align handles the left/right lean), which centers the
   switch regardless of label length without measuring anything.
   At 768px+ Figma instead hardcodes both labels to a fixed 250px
   — Danny's own trick, carried over verbatim.
   ========================================================== */

.toggle {
  display: flex;
  align-items: center;
  justify-content: center;
  gap: 16px;
  width: 100%;
  padding-bottom: 16px;
}

.toggle__label {
  margin: 0;
  flex: var(--toggle-label-flex);
  width: var(--toggle-label-width);
  min-width: 0;
  font-size: var(--toggle-text-size);
  line-height: 1;
  color: #fff;
  text-shadow: -1px -1px 0 rgba(0, 0, 0, 0.75);
  transition: color 0.2s ease;
  cursor: pointer;
}

/* Manual break is a mobile-only line-break; both labels read as one
   line at 768px+, where each has its own fixed 250px box to grow into. */
@media (min-width: 768px) {
  .toggle__label-break {
    display: none;
  }
}

@media (hover: hover) {
  .toggle__label:hover {
    color: #fff;
  }
}

.toggle__label--start {
  text-align: right;
}

.toggle__label--recent {
  color: #aaa;
}

#archive.is-reversed .toggle__label--start {
  color: #aaa;
}

#archive.is-reversed .toggle__label--recent {
  color: #fff;
}

.toggle__switch {
  flex: 0 0 auto;
  display: block;
  width: 56px;
  /* No explicit height: Figma never set one either — the track is
     content-driven (padding + knob + border), which comes out to
     34px. An earlier version hardcoded height:32px, which — with
     box-sizing:border-box — ate the 1px border into that total and
     left only 22px of content height for a 24px knob, squeezing it
     against the bottom. Let it size itself instead. */
  padding: 4px;
  background: rgba(0, 0, 0, 0.5);
  border: 1px solid rgba(255, 255, 255, 0.5);
  border-radius: 12px;
}

.toggle__knob {
  display: block;
  width: 24px;
  height: 24px;
  border-radius: 8px;
  background: #fff;
  transition: transform 0.2s ease;
}

#archive.is-reversed .toggle__knob {
  /* Travel distance is the track's CONTENT width minus the knob,
     not the knob's own width: 56px track, border-box, minus 2×4px
     padding and 2×1px border = 46px content box; 46 − 24 = 22px.
     translateX(24px) overshot by 2px and ate into the right padding. */
  transform: translateX(22px);
}

/* ==========================================================
   Container / sections / grid.
   ========================================================== */

.container {
  display: flex;
  flex-direction: column;
  gap: 64px;
  width: 100%;
  max-width: var(--container-max-width);
  padding-inline: var(--container-padding);
  padding-bottom: 48px;
}

.sections {
  display: flex;
  flex-direction: column;
  gap: 64px;
  width: 100%;
}

/* Order-reversal mechanism: every .section and .thumb carries both
   its natural ascending index and its reversed (within-scope)
   descending index as inline custom properties, computed once at
   build time from the CSV — no runtime math. Toggling .is-reversed
   on the page root just switches which one `order` reads. Sections
   reverse which month comes first; thumbs independently reverse
   their own order within their own month, matching "the same goes
   for the comics inside of each month." `order` (not DOM reordering)
   is what makes this correct under flex-wrap — a wrapped grid can't
   be reversed with row-reverse alone without scrambling the wrap. */
.section {
  display: flex;
  flex-direction: column;
  align-items: center;
  gap: 20px;
  width: 100%;
  order: var(--order-asc);
}

#archive.is-reversed .section {
  order: var(--order-desc);
}

.subheading {
  position: relative;
  display: flex;
  align-items: center;
  justify-content: center;
  width: 100%;
  min-height: 2.5em;
  background-image: url("images/design/break.avif");
  background-repeat: no-repeat;
  background-position: center;
  background-size: 100% auto;
}

@media (max-width: 767px) {
  .subheading {
    /* Scaling the whole image up (rather than stretching it) grows
       its built-in center gap proportionally too, to fit the month
       label — background-position:center already centers on both
       axes, and anything past the element's own box is clipped there. */
    background-size: 150% auto;
  }
}

.subheading__text {
  margin: 0;
  font-family: "Geared Slab", cursive;
  font-weight: 400;
  font-size: var(--subheading-size);
  color: #fff;
  text-align: center;
  text-shadow: -1px -1px 0 rgba(0, 0, 0, 0.75);
  white-space: nowrap;
}

.grid {
  display: flex;
  flex-wrap: wrap;
  gap: var(--grid-gap);
  width: 100%;
}

.thumb {
  order: var(--order-asc);
  display: flex;
  flex-direction: column;
  gap: 4px;
  /* Fluid percentage widths (Danny's explicit ask, "fixed percentages
     so they grow the site as needed") rather than the fixed pixel
     sizes Figma shows at one specific canvas width. */
  width: calc((100% - (var(--grid-cols) - 1) * var(--grid-gap)) / var(--grid-cols));
}

#archive.is-reversed .thumb {
  order: var(--order-desc);
}

.thumb__frame {
  position: relative;
  display: flex;
  flex-direction: column;
  align-items: center;
  justify-content: flex-end;
  width: 100%;
  aspect-ratio: 1 / 1;
  padding: 0;
  overflow: hidden;
  text-align: left;
}

.thumb__img {
  position: absolute;
  inset: 0;
  width: 100%;
  height: 100%;
  object-fit: cover;
  display: block;
}

.thumb__overlay {
  display: none;
}

/* Below 768px: caption always visible under the image, never the
   overlay — matches the single "Mobile" Figma frame (no separate
   mobile-touch variant exists, unlike 768-1023 which forks). From
   768-1023px it forks on touch capability (Tablet-Portrait vs
   Tablet-Portrait (Touch) in Figma); at 1024px+ it's always the
   hover-overlay treatment, matching the plain "Tablet-Landscape" /
   "Desktop" / "Desktop-Wide" frames with no touch variants shown. */
.thumb__caption {
  margin: 0;
  width: 100%;
  text-align: center;
  line-height: 1;
  color: #ccc;
}

.thumb__caption-label {
  font-size: 11px;
}

.thumb__caption-date {
  font-size: 10px;
}

@media (min-width: 1024px), (min-width: 768px) and (max-width: 1023px) and (pointer: fine) {
  .thumb__caption {
    display: none;
  }

  .thumb__overlay {
    display: flex;
    flex-direction: column;
    align-items: center;
    justify-content: flex-end;
    position: absolute;
    inset: 0;
    padding: var(--overlay-padding);
    background: rgba(255, 255, 255, 0.9);
    opacity: 0;
    transition: opacity 0.15s ease;
  }

  /* (hover: hover) is the belt-and-suspenders half of this: the
     width/pointer gate above already excludes touch in the
     768-1023 range, but a touchscreen desktop monitor at >=1024
     would still match that gate on width alone. Scoping the
     actual :hover trigger here too means a tap on a device like
     that still can't get the overlay stuck showing after the tap
     ends, the same sticky-hover issue fixed in the other three
     comics. */
  @media (hover: hover) {
    .thumb__frame:hover .thumb__overlay {
      opacity: 1;
    }
  }
}

.thumb__overlay-label {
  font-family: "Geared Slab", cursive;
  font-weight: 400;
  font-size: var(--overlay-label-size);
  color: #000;
  line-height: 1;
  text-shadow: 1px 1px 0 rgba(255, 255, 255, 0.75);
  white-space: nowrap;
}

.thumb__overlay-date {
  font-size: var(--overlay-date-size);
  color: #000;
  line-height: 1;
  text-shadow: 1px 1px 0 rgba(255, 255, 255, 0.75);
  white-space: nowrap;
}

/* ==========================================================
   Footer
   ========================================================== */

.footer {
  display: flex;
  flex-direction: column;
  align-items: center;
  gap: 4px;
  width: 100%;
  filter: drop-shadow(-1px -1px 0 rgba(0, 0, 0, 0.75));
}

.footer__credit {
  margin: 0;
  font-weight: 500;
  font-size: var(--credit-line1-size);
  color: #fff;
  text-align: center;
}

.footer__link {
  font-size: var(--credit-line2-size);
  color: #fff;
  text-decoration: none;
  text-align: center;
}

@media (hover: hover) {
  .footer__link:hover {
    color: #84bfd9;
    text-decoration: underline;
    text-decoration-style: solid;
    text-underline-position: from-font;
  }
}

/* ==========================================================
   Modal. A single element does double duty as the dimmed
   backdrop, the scroll container, and the click-to-close
   target — JS only closes when the click's actual target IS
   this element (not a descendant), so no separate overlay/track
   split or stopPropagation dance is needed.

   Centering that anchors to the top instead of scrolling
   upward when content is taller than the viewport (Bootstrap's
   modal-dialog behavior) is `margin: auto 0` on .modal itself,
   NOT `justify-content: center` on the overlay. Auto margins
   split leftover space evenly when the content fits (identical
   result to justify-content:center), but collapse to 0 instead
   of going negative when it doesn't — so the box simply starts
   flush at the scroll container's top edge instead of centering
   through its overflow, which is what justify-content:center
   would do and is the usual reason that approach feels broken
   (you'd have to scroll up first to find the top of the content).
   ========================================================== */

.modal-overlay {
  position: fixed;
  inset: 0;
  z-index: 1000;
  display: flex;
  flex-direction: column;
  align-items: center;
  overflow-y: auto;
  background: rgba(0, 0, 0, 0.9);
  padding: var(--modal-overlay-pad-y) 12px;
}

.modal-overlay[hidden] {
  display: none;
}

.modal {
  position: relative;
  width: 100%;
  max-width: 62.25rem; /* 996px */
  margin: auto 0;
  display: flex;
  flex-direction: column;
  align-items: center;
  gap: 12px;
  padding: var(--modal-pad-top) var(--modal-pad-x) var(--modal-pad-bottom);
  background: #fff;
  border-radius: 16px;
}

.modal__close {
  position: absolute;
  top: var(--modal-close-inset);
  right: var(--modal-close-inset);
  width: 36px;
  height: 36px;
  line-height: 0;
  transition: filter 0.2s ease;
}

/* JS moves focus here on open (correct a11y practice for a dialog), but
   that's programmatic focus, not a keyboard tab. :focus-visible SHOULD
   already distinguish those, but Safari's heuristic for a script-called
   .focus() disagrees with Chrome's and shows the ring anyway. Rather
   than fight that per-browser guess, script.js adds this class for
   exactly the one focus call it triggers and removes it on blur — so
   the suppression is explicit instead of inferred, and a real Tab into
   the button (any browser) still shows the ring normally. */
.modal__close.js-no-ring:focus {
  outline: none;
}

@media (hover: hover) {
  .modal__close:hover {
    filter: brightness(120%);
  }
}

.modal__date {
  margin: 0;
  font-size: var(--modal-date-size);
  color: #666;
  text-align: center;
  line-height: 1;
  text-shadow: 1px 1px 0 rgba(255, 255, 255, 0.75);
  white-space: nowrap;
}

.modal__frame {
  position: relative;
  width: 100%;
}

.modal__img {
  display: block;
  width: 100%;
  height: auto;
  transition: opacity 0.2s ease-out;
}

.modal__loader {
  position: absolute;
  top: 50%;
  left: 50%;
  width: var(--modal-loader-size);
  height: var(--modal-loader-size);
  transform: translate(-50%, -50%);
  opacity: 0;
  pointer-events: none;
  transition: opacity 0.15s ease-out;
}

.modal__frame.is-loading .modal__img {
  opacity: 0.05;
}

.modal__frame.is-loading .modal__loader {
  opacity: 1;
}

.modal__pagination {
  display: flex;
  gap: 12px;
  justify-content: center;
  width: 100%;
  padding-top: var(--modal-pagination-pad-top);
  padding-left: var(--modal-pagination-pad-x);
  padding-right: var(--modal-pagination-pad-x);
}

.modal__nav {
  flex: var(--modal-nav-flex);
  width: var(--modal-nav-width);
  max-width: 200px;
  min-width: 0;
  height: 48px;
  display: flex;
  align-items: center;
  justify-content: center;
  gap: 12px;
  padding: 4px;
  overflow: hidden;
  background: #013952;
  border-radius: 12px;
  color: #fff;
  font-size: 20px;
  line-height: 1;
  text-shadow: -1px -1px 0 rgba(0, 0, 0, 0.75);
  transition: background-color 0.2s ease;
}

.modal__nav-icon {
  flex-shrink: 0;
  color: currentColor;
}

.modal__nav:disabled {
  background: #ccc;
  color: #eee;
  text-shadow: -1px -1px 0 rgba(0, 0, 0, 0.15);
  cursor: default;
}

@media (hover: hover) {
  .modal__nav:not(:disabled):hover {
    background: #006592;
  }
}

.modal__nav-label--full {
  display: none;
}

@media (min-width: 768px) {
  .modal__nav-label--short {
    display: none;
  }

  .modal__nav-label--full {
    display: inline;
  }
}

/* ==========================================================
   Constrained mode, mobile + touch tablet-portrait — same
   territory turnonthefun/seniorthesis call "constrained," but
   a different result: there, the content area has flex-grow:1
   and eats all leftover space, shoving the footer to the very
   bottom for a fixed-nav feel. Here .modal keeps its natural
   size and centers as a whole (still via margin:auto 0 on
   .modal — auto margins split real leftover space evenly
   whether or not shrinking ever kicks in, so nothing else
   changes there). Only .modal__frame is flex/shrinkable, so
   when the natural stack (date + image + buttons) is taller
   than the viewport, the IMAGE alone gives up size — via the
   browser's own intrinsic-ratio-aware max-width/max-height
   handling on <img>, since these images don't share one fixed
   ratio the way turnonthefun's pages do, so an aspect-ratio
   declared on the frame itself isn't an option here.
   ========================================================== */

@media (max-width: 767px), (min-width: 768px) and (max-width: 1023px) and (pointer: coarse) {
  .modal-overlay {
    overflow-y: hidden;
  }

  .modal {
    max-height: 100%;
    min-height: 0;
  }

  .modal__date,
  .modal__pagination {
    flex-shrink: 0;
  }

  .modal__frame {
    flex: 1 1 auto;
    min-height: 0;
    display: flex;
    align-items: center;
    justify-content: center;
  }

  .modal__img {
    width: auto;
    height: auto;
    max-width: 100%;
    max-height: 100%;
  }
}