/**
 * MTB de Zeeleeuw — photo carousel (v2.1.40)
 *
 * Placement (deliberate, not incidental): meant to sit as its own row in
 * the Layoutbouwer's Body zone, between the hero + "Drie terreinen"
 * intro and the practical content further down (trainingen/inschrijvingen)
 * — the pitch, then the atmosphere/proof, then the practical info. Not
 * inside the hero itself, which already carries the route-line/glow
 * decoration (see hero.css) and needs its heading to stay legible.
 *
 * Pure CSS scroll-snap does the actual carousel mechanics — real native
 * touch/trackpad/keyboard scrolling, no JS required for the core
 * behaviour. js/carousel.js only adds prev/next buttons and a dot
 * indicator on top; see that file's own docblock. No image files ship
 * with this — see the "Eigen HTML" example in NOTES.md for how an admin
 * adds real photos (Joomla se eigen Media Manager, or drop files in
 * images/gallery/).
 */

.photo-carousel {
  position: relative;
}

.pc-head {
  display: flex;
  justify-content: space-between;
  align-items: flex-end;
  gap: var(--space-6);
  margin-bottom: var(--space-6);
  flex-wrap: wrap;
}

.pc-head h2 {
  margin: 0;
}

.pc-controls {
  display: flex;
  gap: var(--space-2);
  flex: none;
}

.pc-prev,
.pc-next {
  display: inline-flex;
  align-items: center;
  justify-content: center;
  width: 44px;
  height: 44px;
  border-radius: 999px;
  border: 1px solid var(--z-line);
  background: var(--z-paper-alt);
  color: var(--z-ink);
  cursor: pointer;
  transition: background var(--dur) var(--ease), border-color var(--dur) var(--ease);
}

.pc-prev:hover,
.pc-next:hover {
  background: var(--z-paper);
  border-color: var(--z-navy);
}

.pc-prev svg,
.pc-next svg {
  width: 18px;
  height: 18px;
  stroke: currentColor;
  fill: none;
}

.pc-viewport {
  display: flex;
  gap: var(--space-4);
  overflow-x: auto;
  scroll-snap-type: x mandatory;
  scroll-behavior: smooth;
  scrollbar-width: none;
  -webkit-overflow-scrolling: touch;
  padding-bottom: var(--space-1);
  /* Lets the first/last slide's own shadow render fully instead of being
     clipped flush against the viewport edge. */
  margin-inline: calc(var(--space-1) * -1);
  padding-inline: var(--space-1);
}

.pc-viewport::-webkit-scrollbar {
  display: none;
}

@media (prefers-reduced-motion: reduce) {
  .pc-viewport {
    scroll-behavior: auto;
  }
}

.pc-slide {
  position: relative;
  flex: 0 0 auto;
  width: min(400px, 78vw);
  aspect-ratio: 4 / 5;
  border-radius: var(--radius-lg);
  overflow: hidden;
  scroll-snap-align: start;
  background: var(--z-paper);
  box-shadow: 0 18px 40px -20px rgba(10, 32, 54, 0.35);
}

.pc-slide img {
  width: 100%;
  height: 100%;
  object-fit: cover;
  display: block;
}

/* On-image terrain label — deliberately its own component rather than
   reusing .terrain-tag (programs.css): that one assumes a flat, known
   background color to sit on; a photo's own colors are unpredictable, so
   this needs its own guaranteed-legible dark backing chip regardless of
   what's underneath. Same duin/weg/strand color coding, carried by the
   dot instead of the text color this time, for exactly that reason. */
.pc-tag {
  position: absolute;
  top: var(--space-3);
  left: var(--space-3);
  z-index: 1;
  display: inline-flex;
  align-items: center;
  gap: 6px;
  padding: 5px 12px 5px 8px;
  border-radius: 999px;
  background: rgba(4, 27, 51, 0.55);
  backdrop-filter: blur(6px);
  -webkit-backdrop-filter: blur(6px);
  color: #fff;
  font-family: var(--font-mono);
  font-size: 11.5px;
  font-weight: 700;
  text-transform: uppercase;
  letter-spacing: 0.04em;
}

.pc-tag .dot {
  width: 7px;
  height: 7px;
  border-radius: 50%;
  flex: none;
}

.pc-tag.duin .dot { background: var(--z-accent-on-dark); }
.pc-tag.weg .dot { background: var(--z-pink); }
.pc-tag.strand .dot { background: var(--z-gold); }

.pc-caption {
  position: absolute;
  inset: auto 0 0 0;
  z-index: 1;
  padding: var(--space-8) var(--space-4) var(--space-3);
  background: linear-gradient(to top, rgba(4, 27, 51, 0.75) 0%, transparent 100%);
  color: #fff;
  font-size: var(--step-sm);
  font-weight: 600;
}

.pc-dots {
  display: flex;
  justify-content: center;
  gap: var(--space-2);
  margin-top: var(--space-5);
}

.pc-dot {
  width: 8px;
  height: 8px;
  padding: 0;
  border: none;
  border-radius: 50%;
  background: var(--z-line);
  cursor: pointer;
  transition: background var(--dur) var(--ease), transform var(--dur) var(--ease);
}

.pc-dot.is-active {
  background: var(--z-navy);
  transform: scale(1.3);
}

/* Dark-row variant — if this carousel ends up in a navy row instead of a
   paper one (see the terrain-tag/diff-tag/app-badge precedent for this
   same pattern in programs.css/footer.css). */
.lb-row--bg-navy .pc-controls .pc-prev, .lb-row--bg-navy .pc-controls .pc-next,
.lb-row--bg-navy-glow .pc-controls .pc-prev, .lb-row--bg-navy-glow .pc-controls .pc-next,
.lb-row--bg-navy-contour .pc-controls .pc-prev, .lb-row--bg-navy-contour .pc-controls .pc-next {
  background: rgba(255, 255, 255, 0.08);
  border-color: rgba(255, 255, 255, 0.3);
  color: #fff;
}

.lb-row--bg-navy .pc-dot,
.lb-row--bg-navy-glow .pc-dot,
.lb-row--bg-navy-contour .pc-dot {
  background: rgba(255, 255, 255, 0.3);
}

.lb-row--bg-navy .pc-dot.is-active,
.lb-row--bg-navy-glow .pc-dot.is-active,
.lb-row--bg-navy-contour .pc-dot.is-active {
  background: #fff;
}

@media (max-width: 700px) {
  .pc-controls {
    display: none;
  }
}
