/*
Theme Name: Barber Brahim
Description: Custom native block theme for Barber Brahim (Pilot 003) - one design-led homepage, reference-driven. No page builder.
Requires at least: 6.5
Tested up to: 7.1
Requires PHP: 8.0
Text Domain: barber-brahim-pilot3
*/

/* ==========================================================================
   Design-system CSS (STD-001-style separation: theme.json holds tokens,
   this file holds section geometry/behaviour). No client content here.
   ========================================================================== */

/* Owner review, revision 4 (extended revision 7) - real found cause,
   shared by several reported misalignments (hero facts, trust-strip
   icons, the story photos, the final CTA split, and - revision 7 - the
   hero's own photo/scrim/content stack): this project's wp:group
   wrapper blocks intentionally omit their own `layout` attribute (see
   this project's compose-home.php top docblock) so WordPress does not
   inject its own competing layout classes - but every such group is
   still tagged `is-layout-flow` by core, and core's own global styles
   still emit a block-gap top margin on every child but the first
   (`.is-layout-flow > :where(:not(:first-child))`). That margin is
   invisible in a normal stacked flow, but the moment this project's own
   CSS turns the very same wrapper into a flex row or CSS grid - or, as
   found live in revision 7, absolutely-positions its children with
   `inset:0` - the stray margin becomes a real offset: confirmed live
   via getBoundingClientRect that `.bb-hero__scrim`, `.bb-hero__scrim-
   bottom` and `.bb-hero__content` (every `.bb-hero` child except the
   first, `.bb-hero__photo`) each carried a computed `margin-top:24px`,
   pushing the scrim 24px below the hero's actual top - `inset:0` sets
   the offset from the containing block, not from the margin box, so it
   does not cancel a margin the way it might look like it should. Result
   was a 24px unscrimmed strip of raw photo directly under the header.
   Zeroed at each such wrapper's direct children only, never globally,
   so normal flow spacing elsewhere (paragraphs, price rows, footer
   columns) keeps its intended rhythm. `.bb-cta__light` and
   `.bb-cta__light-info` (revision 8, new wrappers for the compact Maps
   layout) are zeroed pre-emptively for the same reason before the bug
   could reproduce there too. `.bb-fact` and `.bb-cta__contact-line`
   (revision 13, STD-001 remediation) are new for the same reason again:
   both used to be a single `wp:html` span/paragraph combining an icon
   and text in one non-editable blob - now an icon (still decorative
   `wp:html`, per STD-001's own allowance) plus a real, independently
   editable `wp:paragraph`, so this same two-child block-gap issue would
   otherwise have reappeared there too. */
.bb-hero > *,
.bb-hero__facts > *,
.bb-trust__row > *,
.bb-trust__item > *,
.bb-story > *,
.bb-cta > *,
.bb-cta__light > *,
.bb-cta__light-info > *,
.bb-fact > *,
.bb-cta__contact-line > *,
.bb-prices > *,
/* Pre-multi-page editability remediation (Repository Owner decision):
   `.bb-footer__hours-row` used to be a single `wp:paragraph` with two
   `<span>` children (no block-gap involved). It is now a `wp:group`
   with two independently central-bound `wp:paragraph` children, so the
   same block-gap margin-top this project has already found and fixed
   twice (see this rule's own docblock above) would otherwise reappear
   here a third time - zeroed pre-emptively, per Proposal 1's own
   guidance to check this whenever a wrapper's children are repositioned
   into a row instead of stacked flow. */
.bb-footer__hours-row > * {
	margin-top: 0;
}

/* Reliable full-bleed breakout - block themes don't always generate the
   automatic negative-margin alignfull rule for every nesting context.
   Container-query units deliberately use the real layout width (which
   excludes the browser scrollbar), unlike 100vw: the latter produced a
   measurable 7px horizontal overflow on every Pilot-3 page at desktop. */
.wp-site-blocks {
	container-type: inline-size;
}
.alignfull {
	margin-left: calc(50% - 50vw) !important;
	margin-right: calc(50% - 50vw) !important;
	max-width: 100vw;
	width: auto;
}
@supports (width: 100cqw) {
	.alignfull {
		margin-left: calc(50% - 50cqw) !important;
		margin-right: calc(50% - 50cqw) !important;
		max-width: 100cqw;
		width: auto;
	}
}

/* ==========================================================================
   Editor-only overrides (Owner review, revision 13 - STD-001 remediation,
   real found cause of "the Home editor shows almost only the title and a
   big empty area"): `add_editor_style('style.css')` in functions.php loads
   this exact same stylesheet into the block editor canvas, which WordPress
   wraps in `.editor-styles-wrapper` - so every rule below, unscoped, was
   also running inside the editor, with two concrete failures:
   1. `.bb-reveal{opacity:0}` (further down, inside the reduced-motion
      media query) is meant to be flipped to `opacity:1` by
      `assets/js/interactions.js`'s IntersectionObserver on the real
      frontend - that script never runs inside the editor iframe, so
      every major section (hero, prices text/photo, story photos,
      collage, final CTA - everything this project's compose-home.php
      tags `bb-reveal`) stayed invisible in the canvas: not missing
      content, invisible content.
   2. `.alignfull{width:100vw; margin:calc(50% - 50vw)}` breaks a
      full-bleed section out of its normal column on the real frontend
      body - inside the editor canvas (which is itself a scaled/scrollable
      iframe, not the real viewport) the same 100vw math produced a
      massive horizontal scrollbar instead, pushing content out of view.
   Both are scoped here to `.editor-styles-wrapper` only, with the
   frontend rules themselves left completely untouched - confirmed no
   change to the approved public appearance at any breakpoint. */
.editor-styles-wrapper .bb-reveal {
	opacity: 1 !important;
	transform: none !important;
}
.editor-styles-wrapper .alignfull {
	margin-left: 0 !important;
	margin-right: 0 !important;
	max-width: 100% !important;
	width: 100% !important;
}
/* The hero's decorative scrim/overlay layers are `position:absolute`
   full-bleed panels meant to sit silently behind real content on the
   frontend - inside the editor they must never swallow clicks intended
   for the real blocks underneath (headline, buttons, images), which a
   plain "select the section" click would otherwise hit first. */
.editor-styles-wrapper .bb-hero__scrim,
.editor-styles-wrapper .bb-hero__scrim-bottom {
	pointer-events: none;
}
/* Owner review, revision 15: the `barber-brahim/icon-item` block's
   Inspector icon-picker CSS used to live here, reachable only via
   `add_editor_style()` - which never reaches the sidebar (see
   assets/css/icon-picker-editor.css's own docblock for the full root
   cause). Moved to that dedicated file, loaded via
   `enqueue_block_editor_assets` instead - nothing here any more. */

img {
	max-width: 100%;
	height: auto;
}

/* Header -> hero gap (Owner review, revision 2 - a real, found cause, not
   papered over with a negative margin): WordPress's own block-gap spacing
   applies a 24px margin-top to <main> as the template's second root-level
   block (after the header template part) - this is WP core's generic
   vertical rhythm between root blocks, not anything this theme's CSS
   added, and it does not belong between an edge-to-edge dark header and
   an edge-to-edge photographic hero. Zeroed at the exact element that
   carries it. */
main.wp-block-group {
	margin-top: 0;
}

/* --- Header ------------------------------------------------------------- */
.bb-header {
	/* Matches header-logo.png's own real photographed background (sampled
	   ~#0c0c0b) rather than the theme's general ink token (#15120d) - a
	   deliberately tighter match so the logo's own rectangle reads as
	   part of the header, not a pasted-in image with a visible edge. */
	background: #0c0c0b;
	position: sticky;
	top: 0;
	z-index: 100;
}
.bb-header__inner {
	display: flex;
	align-items: center;
	justify-content: space-between;
	gap: 1.5rem;
	/* Vertical padding reduced again (Owner review, revision 4): the
	   header logo grew from 52px to 72px tall to actually read as the
	   brand at a glance rather than a small badge, and total header
	   height must not grow to match - so the surrounding padding gives
	   up nearly all of what the logo gained (0.5rem -> 0.3rem, a 6.4px
	   saving on each edge against the logo's 20px gain). */
	padding: 0.3rem clamp(1.25rem, 4vw, 3rem);
	max-width: 1440px;
	margin: 0 auto;
}
/* Official header brand asset (Owner review, revision 2): the real
   supplied header-logo.png, shown at its own real 2:1 aspect ratio -
   no reconstructed "Brahim" script + "Barber - sinds 1998" label
   typeset next to it any more (removed entirely, not just hidden). */
.bb-brand {
	flex: 0 0 auto;
	display: flex;
	align-items: center;
}
.bb-brand.wp-block-site-logo,
.bb-brand .custom-logo-link {
	display: flex;
	align-items: center;
	margin: 0;
}
/* Only HEIGHT is ever fixed here, width always auto (Owner review,
   revision 4 explicit check): a future logo the Owner uploads through
   Site Identity with a different aspect ratio scales from this one
   dimension and is never stretched or cropped by a second, competing
   fixed axis. */
.bb-brand img.custom-logo {
	display: block;
	height: 72px;
	width: auto;
}
/* Core Navigation block, restyled - native overlay-menu mechanics (no
   custom JS needed for the mobile toggle; WordPress core handles it). */
.bb-nav.wp-block-navigation {
	flex: 1 1 auto;
	justify-content: center;
	color: var(--wp--preset--color--contrast);
}
.bb-nav .wp-block-navigation__container {
	gap: clamp(1.1rem, 2vw, 2rem) !important;
	justify-content: center;
}
.bb-nav .wp-block-navigation-item__content {
	color: var(--wp--preset--color--contrast) !important;
	text-decoration: none !important;
	font-family: var(--wp--preset--font-family--body);
	font-size: 0.8rem;
	font-weight: 700;
	letter-spacing: 0.1em;
	text-transform: uppercase;
	position: relative;
	padding: 0.35rem 0 !important;
	opacity: 0.88;
	transition: opacity 0.2s ease;
}
.bb-nav .wp-block-navigation-item__content:hover,
.bb-nav .wp-block-navigation-item__content:focus-visible {
	opacity: 1;
}
.bb-nav .wp-block-navigation-item__content::after {
	content: "";
	position: absolute;
	left: 0;
	bottom: 0;
	width: 0;
	height: 2px;
	background: var(--wp--preset--color--gold);
	transition: width 0.25s ease;
}
.bb-nav .wp-block-navigation-item__content:hover::after,
.bb-nav .wp-block-navigation-item__content:focus-visible::after {
	width: 100%;
}
.bb-nav .wp-block-navigation__responsive-container-open,
.bb-nav .wp-block-navigation__responsive-container-close {
	color: var(--wp--preset--color--contrast);
}
.bb-nav .wp-block-navigation__responsive-container.is-menu-open {
	background: var(--wp--preset--color--ink);
	padding: 1.5rem;
}
.bb-nav .wp-block-navigation__responsive-container.is-menu-open .wp-block-navigation__responsive-container-content,
.bb-nav .wp-block-navigation__responsive-container.is-menu-open .wp-block-navigation__container {
	/* PILOT 003 MOBILE NAVIGATION CENTERING: both this wrapper and the
	   nav container it holds were being cross-axis-centered/shrink-
	   wrapped to their content's own width (~100px) rather than
	   stretched to the open panel's real width (312px at a 360px
	   viewport, confirmed live via getComputedStyle()) - so the whole
	   label group sat pinned near the left edge instead of each full-
	   width row centering its own label. `!important` is required on
	   both: WordPress core's navigation/style.min.css sets align-items
	   on these same two elements via
	   `align-items: var(--navigation-layout-justification-setting, ...)`
	   at equal-or-greater selector specificity, loading after this
	   theme stylesheet, and this block instance carries the relevant
	   custom property inline - which any plain (non-!important)
	   declaration here cannot outrank. Once both stretch to the full
	   panel width, `width: 100%` on each item/content below resolves
	   against that real width and `text-align: center` centers each
	   label within its own full-width, full-comfort tap target. */
	align-items: stretch !important;
}
.bb-nav .wp-block-navigation__responsive-container.is-menu-open .wp-block-navigation__container {
	/* align-items: stretch above still wasn't enough on its own to
	   widen this specific element live (its `.items-justified-center`
	   block-supports class carries its own layout assumptions this
	   theme doesn't need in the open-menu state) - an explicit width
	   closes the gap directly and unambiguously, confirmed live. */
	width: 100% !important;
	gap: 0.4rem !important;
}
.bb-nav .wp-block-navigation__responsive-container.is-menu-open .wp-block-navigation-item {
	width: 100%;
}
.bb-nav .wp-block-navigation__responsive-container.is-menu-open .wp-block-navigation-item__content {
	font-size: 1.1rem;
	padding: 0.6rem 0 !important;
	width: 100%;
	text-align: center;
}
.bb-header__cta {
	flex: 0 0 auto;
}
/* Button style variations - the actual clickable element WordPress
   renders is `.wp-block-button__link` *inside* the wrapper div that
   carries `is-style-X`, so every rule below targets that link, never
   the wrapper (found live: styling the wrapper directly doubles up
   padding/background in the wrong place). */
.wp-block-button .wp-block-button__link {
	display: inline-flex;
	align-items: center;
	gap: 0.5rem;
	font-family: var(--wp--preset--font-family--body);
	font-size: 0.78rem;
	font-weight: 700;
	letter-spacing: 0.05em;
	text-transform: uppercase;
	text-decoration: none !important;
	padding: 0.65rem 1.3rem;
	border-radius: 3px;
	white-space: nowrap;
	transition: background-color 0.2s ease, color 0.2s ease, border-color 0.2s ease, transform 0.15s ease;
}
.wp-block-button .wp-block-button__link svg { width: 1em; height: 1em; flex: 0 0 auto; }
.wp-block-button.is-style-bb-fill .wp-block-button__link {
	background: var(--wp--preset--color--gold);
	color: var(--wp--preset--color--ink) !important;
}
.wp-block-button.is-style-bb-fill .wp-block-button__link:hover { background: var(--wp--preset--color--gold-deep); transform: translateY(-1px); }
.wp-block-button.is-style-bb-outline-dark .wp-block-button__link {
	background: transparent;
	color: var(--wp--preset--color--contrast) !important;
	border: 1.5px solid rgba(255,255,255,0.55);
}
.wp-block-button.is-style-bb-outline-dark .wp-block-button__link:hover { border-color: var(--wp--preset--color--gold); color: var(--wp--preset--color--gold) !important; }
/* Owner review, revision 4: hero's secondary CTA ("Bel direct") needs
   the approved-design gold outline, not the generic on-dark outline
   used elsewhere - a distinct style variation (not a repaint of
   bb-outline-dark) so any other current/future dark-background button
   that genuinely wants a neutral outline is unaffected. Interior stays
   transparent (reads as the hero's dark photo behind it) so this never
   competes with the filled gold WhatsApp CTA next to it. */
.wp-block-button.is-style-bb-outline-gold .wp-block-button__link {
	background: transparent;
	color: var(--wp--preset--color--contrast) !important;
	border: 1.5px solid var(--wp--preset--color--gold);
}
.wp-block-button.is-style-bb-outline-gold .wp-block-button__link:hover { background: var(--wp--preset--color--gold); color: var(--wp--preset--color--ink) !important; }
.wp-block-button.is-style-bb-outline-light .wp-block-button__link {
	background: transparent;
	color: var(--wp--preset--color--ink) !important;
	border: 1.5px solid rgba(21,18,13,0.28);
}
.wp-block-button.is-style-bb-outline-light .wp-block-button__link:hover { border-color: var(--wp--preset--color--gold-deep); color: var(--wp--preset--color--gold-deep) !important; }
/* Pre-multi-page editability remediation (Repository Owner decision):
   the footer's phone/WhatsApp entries are now real `core/button` blocks
   (the only native block whose `url` AND `text` can both be bound to
   the central business-info source), styled here to render as a plain
   inline link identical to every other footer link (`.bb-footer a`,
   below) rather than this project's usual boxed CTA chrome - resets
   every button-specific rule the shared `.wp-block-button__link` rule
   above applies, then matches `.bb-footer a`'s own declared values
   exactly rather than relying on inheritance/cascade order. */
.wp-block-button.is-style-bb-plain-link { display: inline; }
.wp-block-button.is-style-bb-plain-link .wp-block-button__link {
	display: inline;
	background: none;
	border: none;
	padding: 0;
	border-radius: 0;
	font-family: var(--wp--preset--font-family--body);
	font-size: 0.85rem;
	font-weight: 400;
	letter-spacing: normal;
	text-transform: none;
	color: rgba(255,255,255,0.72);
}
.wp-block-button.is-style-bb-plain-link .wp-block-button__link:hover { color: var(--wp--preset--color--gold) !important; transform: none; }

@media (max-width: 560px) {
	.bb-brand img.custom-logo { height: 46px; }
	/* The compact mobile header (logo + hamburger) has no room left for
	   the WhatsApp button without overflowing 360px viewports - the
	   hero's own WhatsApp CTA sits immediately below anyway, so nothing
	   is lost by not repeating it in the cramped header row. */
	/* Matches WP core's own `.wp-block-group.is-layout-flex` specificity
	   (two class selectors) - found live: a single-class `display: none`
	   here lost to WordPress's generated global-styles-inline-css rule,
	   which is more specific, not just earlier in source order. */
	.wp-block-group.bb-header__cta { display: none; }
	/* Owner review, revision 12 - real found cause: `.bb-nav.wp-block-
	   navigation` keeps its base `flex:1 1 auto` here too, so once the
	   WhatsApp CTA above is hidden, the nav block stretches to fill that
	   freed-up width - confirmed live via getBoundingClientRect, its own
	   box already reached the header's right padding edge - and the
	   block's own `justifyContent:center` layout attribute (see
	   header.html's `wp:navigation` block) then centers the single
	   remaining child (the hamburger) inside that whole stretched box,
	   not at its edge: measured ~90px of empty space on both sides of
	   the button instead of a flush right edge. Fix shrinks the nav back
	   to its own content width (`flex:0 0 auto`) and pushes that compact
	   box itself to the right with `margin-left:auto` - structural, not
	   an absolute-position or negative-margin patch. Two-class selector
	   specificity matches this file's existing precedent (see the
	   `.wp-block-group.bb-header__cta` rule just above) for beating
	   WordPress's own generated `justifyContent` layout-support rule. */
	.bb-nav.wp-block-navigation {
		flex: 0 0 auto;
		margin-left: auto;
		justify-content: flex-end;
	}
	.bb-nav .wp-block-navigation__responsive-container-open {
		display: inline-flex;
		align-items: center;
		justify-content: center;
		width: 44px;
		height: 44px;
		padding: 0.5rem;
	}
}

/* --- Hero ----------------------------------------------------------------- */
.bb-hero {
	position: relative;
	background: var(--wp--preset--color--ink);
	overflow: hidden;
	min-height: min(86vh, 760px);
	display: flex;
	align-items: stretch;
}
.bb-hero__photo {
	position: absolute;
	inset: 0;
	width: 100%;
	height: 100%;
	object-fit: cover;
	object-position: 62% center;
}

.bb-hero__photo img {
	width: 100%;
	height: 100%;
	object-fit: cover;
	object-position: center;
	display: block;
}
.bb-hero__scrim {
	position: absolute;
	inset: 0;
	background: linear-gradient(100deg,
		rgba(15,12,8,0.97) 0%,
		rgba(15,12,8,0.94) 28%,
		rgba(15,12,8,0.72) 42%,
		rgba(15,12,8,0.28) 58%,
		rgba(15,12,8,0.05) 72%,
		rgba(15,12,8,0) 85%);
}
.bb-hero__scrim-bottom {
	position: absolute;
	inset: 0;
	background: linear-gradient(0deg, rgba(15,12,8,0.55) 0%, rgba(15,12,8,0) 24%);
}
/* Owner review, revision 6: the revision-5 header/hero gradient
   (`.bb-hero::after`) was rejected outright and is removed in full,
   comment and rule together - no trace, no reduced-opacity remnant.
   The header is a uniform, hard-edged black bar; the hero photo begins
   immediately below it with no transition layer of any kind. */
.bb-hero__content {
	position: relative;
	z-index: 2;
	display: flex;
	flex-direction: column;
	justify-content: center;
	max-width: 680px;
	padding: clamp(4.5rem, 9vw, 6rem) clamp(1.25rem, 4vw, 3rem) clamp(3rem, 6vw, 4.5rem);
	margin-right: auto;
}
.bb-eyebrow {
	font-family: var(--wp--preset--font-family--body);
	font-size: 0.75rem;
	font-weight: 800;
	letter-spacing: 0.28em;
	text-transform: uppercase;
	color: var(--wp--preset--color--gold);
	margin: 0 0 1.1rem;
}
.bb-hero__title {
	font-family: var(--wp--preset--font-family--display);
	font-weight: 640;
	font-size: clamp(2.65rem, 6vw, 4.4rem);
	line-height: 1.04;
	letter-spacing: -0.01em;
	color: var(--wp--preset--color--contrast);
	margin: 0 0 1.35rem;
}
.bb-hero__title em {
	font-style: normal;
	color: var(--wp--preset--color--gold);
}
.bb-hero__lede {
	font-size: 1.08rem;
	line-height: 1.65;
	color: rgba(255,255,255,0.82);
	max-width: 46ch;
	margin: 0 0 2rem;
}
.bb-hero__ctas {
	display: flex;
	flex-wrap: wrap;
	gap: 0.85rem;
	margin-bottom: 1.75rem;
}
.bb-hero__ctas .wp-block-button .wp-block-button__link { padding: 0.9rem 1.65rem; font-size: 0.82rem; }
.bb-hero__facts {
	display: flex;
	flex-wrap: wrap;
	align-items: center;
	gap: 0.65rem;
}
.bb-fact {
	display: inline-flex;
	align-items: center;
	gap: 0.5rem;
	font-size: 0.72rem;
	font-weight: 700;
	letter-spacing: 0.04em;
	text-transform: uppercase;
	color: rgba(255,255,255,0.92);
	border: 1px solid rgba(255,255,255,0.28);
	border-radius: 3px;
	padding: 0.5rem 0.85rem;
	white-space: nowrap;
}
.bb-fact svg { width: 14px; height: 14px; color: var(--wp--preset--color--gold); flex: 0 0 auto; }
/* Owner review, revision 13: `.bb-fact` now wraps a real `wp:paragraph`
   (see compose-home.php) instead of holding text directly - the
   paragraph's own default block-bottom-margin (global styles) is
   zeroed so it doesn't add unwanted height inside the compact chip;
   type styling above is inherited from `.bb-fact` by normal CSS
   cascade, so no separate `.bb-fact__text` rules are needed. */
.bb-fact p { margin: 0; }

@media (max-width: 900px) {
	.bb-hero { min-height: min(92vh, 680px); align-items: flex-end; }
	/* Owner review, revision 9 - real found cause, deeper than it first
	   looked: `.bb-hero__photo{object-fit:cover}` targets the `<figure>`
	   wrapper (see compose-home.php), not the actual `<img>` inside it -
	   `object-fit`/`object-position` are no-ops on a non-replaced
	   element, so they never did anything, on any breakpoint. The figure
	   is correctly `position:absolute;inset:0`, but the `<img>` itself
	   was left at its own static-position natural size (whatever the
	   browser's responsive-image algorithm selected from `srcset`) -
	   confirmed live via getBoundingClientRect: at 1440px wide, the
	   selected image happens to render ~1440x960, comfortably taller
	   than the 760px hero box, so the excess is simply clipped and it
	   looks like correct `cover` behavior by coincidence. At 360px wide
	   the selected image renders only ~360x240 - far shorter than the
	   ~680-753px mobile hero - so the image simply ran out about a
	   quarter of the way down, and everything below that showed
	   `.bb-hero`'s own plain `--ink` background: a real gap, not a dark
	   scrim over a photo. Desktop's accidental correctness means this is
	   fixed here, mobile-only, without touching the shared base rule.
	   With the `<img>` now genuinely covering the box, a modest `scale()`
	   (safe - `.bb-hero` already clips overflow, so zoomed edges never
	   show) trades away part of the photo's vertical range for a tighter,
	   more deliberate crop.
	   Owner review, revision 11: the anchor was flipped from high
	   (`transform-origin` near the top, `8%`) to low (`75%`) - the
	   top-anchored crop kept too much of the plain brick facade and
	   pipework visible at this zoom, exactly the "uninteresting" upper
	   section the Owner flagged. Anchoring near the bottom instead keeps
	   the storefront glazing, the "Brahim" window branding and the
	   entrance signage board in frame - confirmed visually on real 360
	   and 768 screenshots, not assumed - while `overflow:hidden` on
	   `.bb-hero` still guarantees no white edges regardless of anchor.
	   `object-position` is set to match but is a no-op in practice at
	   this aspect ratio: `object-fit:cover` already shows the source
	   photo's full height with zero vertical cropping before the
	   transform runs (there is never vertical slack for object-position
	   to distribute), so the transform-origin is what actually does the
	   framing work. */
	.bb-hero__photo img {
		display: block;
		width: 100%;
		height: 100%;
		object-fit: cover;
		object-position: 18% bottom;
		transform: scale(1.5);
		transform-origin: 18% 75%;
	}
	/* Owner review, revision 10 - real found cause of both this round's
	   issues: (1) live-measured content zone (getBoundingClientRect) on
	   360px shows the eyebrow-to-facts stack spans ~5% to ~94% of the
	   hero's height - i.e. almost the ENTIRE hero, not just its bottom
	   third - so the revision-9 gradient's low ceiling and early taper
	   left the middle/upper content (lede, headline) under-covered,
	   which is why it read as "light and unrestful" against the busy
	   photo; (2) the text-shadow added as insurance for that same gap
	   was placed on the generic `.bb-eyebrow` class, which every section
	   label ("Onze prijzen", "Ons verhaal", ...) also uses outside the
	   hero - given the Owner's explicit preference (contrast via the
	   overlay, not visible text-shadow), the shadow is removed entirely
	   rather than re-scoped, and this gradient carries contrast on its
	   own instead. Solid, close-to-uniform coverage across the measured
	   content span (0-80% from the bottom), easing only through the
	   ~15% of the hero above the eyebrow that is pure, undarkened photo. */
	/* "PILOT 003 - MOBILE HERO CROP + OVERLAY REFINEMENT": the left-side
	   entrance crop above trades away the price board's own text-shadow
	   worth of contrast (dark price-board text on light card is easy to
	   read against) for a warmer, lighter doorway/interior glow - a
	   modestly stronger scrim keeps the same proportional taper (revision
	   10's own reasoning above is unchanged: full coverage of the
	   measured content zone, easing only through the top ~15%) but each
	   stop raised by a flat +0.10-0.12 so the photo still reads as a real,
	   recognizable photograph (never solid black) while giving the text
	   more separation from it. No text-shadow added anywhere (Owner's
	   standing preference, restated this round). */
	.bb-hero__scrim {
		background: linear-gradient(0deg,
			rgba(15,12,8,0.76) 0%,
			rgba(15,12,8,0.73) 45%,
			rgba(15,12,8,0.62) 75%,
			rgba(15,12,8,0.38) 90%,
			rgba(15,12,8,0.2) 100%);
	}
	.bb-hero__scrim-bottom { display: none; }
	.bb-hero__content { max-width: 100%; padding: 2.5rem 1.25rem 2.75rem; }
	.bb-hero__title { font-size: clamp(2.3rem, 9vw, 3rem); }
	.bb-hero__ctas .wp-block-button { flex: 1 1 auto; } .bb-hero__ctas .wp-block-button .wp-block-button__link { justify-content: center; width: 100%; }
}

/* --- Trust strip ------------------------------------------------------- */
.bb-trust {
	background: var(--wp--preset--color--cream);
	border-bottom: 1px solid var(--wp--preset--color--line);
}
.bb-trust__row {
	display: grid;
	grid-template-columns: repeat(3, 1fr);
	gap: clamp(1.5rem, 4vw, 3rem);
	max-width: 1280px;
	margin: 0 auto;
	padding: clamp(2rem, 4vw, 2.75rem) clamp(1.25rem, 4vw, 3rem);
}
.bb-trust__item {
	display: flex;
	align-items: flex-start;
	gap: 0.9rem;
}
/* Owner review, revision 4: now a real `wp:image` Media Library
   attachment (figure > img), not an inline SVG span - margin zeroed
   (figures carry a default block margin) and the icon centered inside
   the same gold-ringed circle as before. */
.bb-trust__icon {
	flex: 0 0 auto;
	width: 40px;
	height: 40px;
	margin: 0;
	border-radius: 50%;
	border: 1.5px solid var(--wp--preset--color--gold);
	display: flex;
	align-items: center;
	justify-content: center;
	/* Owner review, revision 16: `--bb-icon-color` is only ever set as an
	   inline style by bb_render_icon_item_block() (functions.php) when
	   the Owner has explicitly picked a non-default color for THAT one
	   block instance - narrowly scoped to this element, never set
	   anywhere else, so it cannot leak into the circle's own border,
	   title, description, or any other trust item. No inline style at
	   all (the existing, un-migrated-to-color case) falls straight
	   through to the same `gold-deep` this rule always used. */
	color: var(--bb-icon-color, var(--wp--preset--color--gold-deep));
}
.bb-trust__icon img { width: 18px; height: 18px; object-fit: contain; display: block; }
/* Owner review, revision 14: trust icons now come from the
   `barber-brahim/icon-item` block's curated inline-SVG set (see
   functions.php's bb_icon_set()) rather than a Media Library `<img>` -
   same 18px size and `currentColor` inheritance from `.bb-trust__icon`
   above, so swapping icon keeps identical visual weight/position. */
.bb-trust__icon svg { width: 18px; height: 18px; display: block; }
.bb-trust__item h3 {
	font-family: var(--wp--preset--font-family--body);
	font-size: 0.82rem;
	font-weight: 800;
	letter-spacing: 0.06em;
	text-transform: uppercase;
	margin: 0.15rem 0 0.35rem;
	color: var(--wp--preset--color--ink);
}
.bb-trust__item p {
	font-size: 0.92rem;
	line-height: 1.55;
	color: rgba(21,18,13,0.72);
	margin: 0;
}
.bb-trust__item strong { color: var(--wp--preset--color--ink); font-weight: 700; }

@media (max-width: 720px) {
	.bb-trust__row { grid-template-columns: 1fr; gap: 1.5rem; }
}

/* --- Section rhythm ------------------------------------------------------ */
.bb-section { padding-top: 4.5rem; padding-bottom: 4.5rem; }
@media (max-width: 720px) {
	.bb-section { padding-top: var(--wp--preset--spacing--50); padding-bottom: var(--wp--preset--spacing--50); }
}

/* Gallery -> Contact transition only (Owner review, revision 3): both
   sections sit on the same cream background with no visual break
   between them, so their default 4.5rem+4.5rem padding read as one
   168px void rather than two intentional section edges. Targeted to
   this one transition - every other section-to-section gap on the
   page was already correct and is left untouched. */
#fotos { padding-bottom: 2rem; }
#contact { padding-top: 2rem; }
@media (max-width: 720px) {
	#fotos { padding-bottom: var(--wp--preset--spacing--40); }
	#contact { padding-top: var(--wp--preset--spacing--40); }
}
.bb-section--sand { background: var(--wp--preset--color--sand); }
.bb-rule {
	width: 3rem;
	height: 3px;
	background: var(--wp--preset--color--gold);
	border: 0;
	margin: 0 0 1.1rem;
}

/* --- Prices --------------------------------------------------------------- */
.bb-prices {
	display: grid;
	grid-template-columns: 42% 1fr;
	gap: clamp(2rem, 5vw, 4rem);
	align-items: center;
	max-width: 1280px;
	margin: 0 auto;
	padding: 0 clamp(1.25rem, 4vw, 3rem);
}
.bb-prices__heading {
	font-family: var(--wp--preset--font-family--display);
	font-weight: 600;
	font-size: clamp(1.75rem, 3vw, 2.5rem);
	line-height: 1.18;
	margin: 0 0 1.5rem;
}
.bb-price-list { list-style: none; margin: 0 0 1rem; padding: 0; }
.bb-price-row {
	display: flex;
	align-items: baseline;
	gap: 0.75rem;
	padding: 0.85rem 0;
	border-bottom: 1px solid var(--wp--preset--color--line);
}
.bb-price-row__icon { flex: 0 0 auto; width: 18px; height: 18px; color: var(--wp--preset--color--gold-deep); }
.bb-price-row__name { flex: 1 1 auto; font-size: 1rem; font-weight: 500; margin: 0; }
.bb-price-row__amount {
	margin: 0;
	flex: 0 0 auto;
	font-family: var(--wp--preset--font-family--display);
	font-weight: 700;
	font-size: 1.15rem;
	color: var(--wp--preset--color--gold-deep);
	white-space: nowrap;
}
.bb-price-row--featured {
	background: var(--wp--preset--color--sand);
	margin: 0.35rem -0.9rem;
	padding: 0.85rem 0.9rem;
	border-radius: 4px;
	border-bottom: 1px solid transparent;
}
.bb-prices__note { font-size: 0.82rem; color: rgba(21,18,13,0.55); margin: 0; }
.bb-prices__photo {
	border-radius: 6px;
	overflow: hidden;
	aspect-ratio: 4 / 5;
}
.bb-prices__photo img { width: 100%; height: 100%; object-fit: cover; display: block; }

@media (max-width: 900px) {
	.bb-prices { grid-template-columns: 1fr; }
	.bb-prices__photo { order: -1; aspect-ratio: 16 / 10; }
}

/* --- Story ------------------------------------------------------------ */
.bb-story {
	display: grid;
	grid-template-columns: 1fr 1.15fr 1fr;
	gap: clamp(1rem, 3vw, 2rem);
	align-items: stretch;
	max-width: 1280px;
	margin: 0 auto;
	padding: 0 clamp(1.25rem, 4vw, 3rem);
}
.bb-story__photo { border-radius: 6px; overflow: hidden; }
.bb-story__photo img { width: 100%; height: 100%; object-fit: cover; display: block; min-height: 320px; }
.bb-story__text { display: flex; flex-direction: column; justify-content: center; padding: 1rem 0; }
.bb-story__text h2 { font-size: clamp(1.9rem, 3.2vw, 2.6rem); margin: 0 0 1rem; }
.bb-story__text h2 em { font-style: normal; color: var(--wp--preset--color--gold-deep); }
.bb-story__text p { font-size: 0.98rem; line-height: 1.7; color: rgba(21,18,13,0.78); margin: 0 0 0.9rem; }
.bb-signature {
	font-family: var(--wp--preset--font-family--script);
	font-size: 1.9rem;
	color: var(--wp--preset--color--ink);
	margin-top: 0.75rem;
}
/* Restrained cross-links to the new Over ons / Foto's pages (controlled
   Home adaptation C, "PILOT 003 - ONE-SHOT MULTI-PAGE WEBSITE
   COMPLETION") - small, text-only, using the theme's own default link
   color (theme.json styles.elements.link) rather than a button, so
   neither addition competes visually with the section's real content or
   the page's actual CTAs. */
.bb-story__more { margin-top: 0.9rem; }
.bb-story__more a,
.bb-collage__more a {
	font-family: var(--wp--preset--font-family--body);
	font-size: 0.82rem;
	font-weight: 700;
	letter-spacing: 0.02em;
	text-decoration: none;
}
.bb-story__more a:hover,
.bb-collage__more a:hover { text-decoration: underline; }
.bb-collage__more { margin-top: 1.25rem; }

@media (max-width: 900px) {
	.bb-story { grid-template-columns: 1fr; }
	.bb-story__photo img { min-height: 220px; }
	/* Owner review, revision 9: `order:-1` reordered the text ahead of
	   both photos, overriding the natural Gutenberg DOM order (photo,
	   text, photo). Removed - mobile now simply follows source order,
	   giving the requested photo -> text -> photo reading sequence. */
	.bb-story__text { padding: 0 0 0.5rem; }
}

/* --- Collage (Owner review, revision 4: real `core/gallery` block,
   see compose-home.php's own docblock for why) --------------------- */
/* `.wp-block-gallery` (extra qualifier, not just `.bb-collage`) beats
   WordPress core's own gallery stylesheet on every rule below - core's
   `figure.wp-block-image` selectors carry more classes than a bare
   `.bb-collage__item` would, so without this every one of these would
   silently lose to core's defaults instead of shaping the row. */
.wp-block-gallery.bb-collage {
	display: flex;
	gap: 0.6rem;
	max-width: 1280px;
	margin: 0 auto;
	padding: 0 clamp(1.25rem, 4vw, 3rem);
	overflow: hidden;
}
.wp-block-gallery.bb-collage .bb-collage__item { border-radius: 4px; overflow: hidden; flex: 1 1 0; min-width: 0; width: auto; height: clamp(220px, 26vw, 320px); margin: 0; }
/* `!important` matches this file's existing precedent (see `.alignfull`
   above) for the one place a WordPress core block stylesheet cannot be
   beaten on specificity alone - core's own `img{width:auto;height:auto}`
   inside `.wp-block-gallery.has-nested-images figure.wp-block-image`
   would otherwise stop these photos filling their fixed-height cell and
   being cropped to it. */
.wp-block-gallery.bb-collage .bb-collage__item img { width: 100% !important; height: 100% !important; object-fit: cover; display: block; transition: transform 0.5s ease; }
.wp-block-gallery.bb-collage .bb-collage__item:hover img { transform: scale(1.04); }
.wp-block-gallery.bb-collage .bb-collage__item--wide { flex: 1.7 1 0; }
.wp-block-gallery.bb-collage .bb-collage__item--narrow { flex: 0.75 1 0; }

@media (max-width: 900px) {
	.wp-block-gallery.bb-collage { overflow-x: auto; scroll-snap-type: x mandatory; padding-bottom: 0.5rem; }
	.wp-block-gallery.bb-collage .bb-collage__item { flex: 0 0 62vw; scroll-snap-align: start; height: 240px; }
	.wp-block-gallery.bb-collage .bb-collage__item--wide { flex: 0 0 74vw; }
	.wp-block-gallery.bb-collage .bb-collage__item--narrow { flex: 0 0 48vw; }
}

/* --- Final CTA ------------------------------------------------------------ */
/* Owner review, revision 8 - real found compositional fault, not a
   visual patch: `.bb-cta__dark` is diagonally clipped
   (`clip-path: polygon(0 0, 100% 0, 92% 100%, 0% 100%)`), which cuts
   INTO its own box - the clipped-away triangle is real transparent
   space, showing whatever sits BEHIND `.bb-cta__dark` in the stacking
   order. That used to be `.bb-cta` itself, which had no background of
   its own (transparent), so the triangle showed the page's `--cream`
   background - a visibly different, lighter shade than `--sand`. The
   previous fix attempt (`.bb-cta__light{margin-left:-6%}`) tried to
   stretch the light half's own box left to cover that triangle instead
   - measured live via getBoundingClientRect: at the clip's bottom
   corner the two edges missed each other by ~13px (percentage margins
   on a grid item and clip-path percentages on a differently-sized box
   are not the same base, so they cannot be reconciled by tuning two
   numbers), leaving a persistent white/light sliver.
   Real fix: the SHARED container gets the sand background, and the
   dark half's clipped shape simply sits on top of it - the exposed
   triangle then always shows the correct color, in one place, with no
   second box having to precisely match an edge it does not own. */
.bb-cta {
	display: grid;
	grid-template-columns: 1fr 1fr;
	max-width: 1280px;
	margin: 0 auto;
	overflow: hidden;
	border-radius: 8px;
	background: var(--wp--preset--color--sand);
}
.bb-cta__dark {
	background: var(--wp--preset--color--ink);
	color: var(--wp--preset--color--contrast);
	padding: clamp(2.5rem, 5vw, 3.5rem);
	display: flex;
	flex-direction: column;
	justify-content: center;
	clip-path: polygon(0 0, 100% 0, 92% 100%, 0% 100%);
}
.bb-cta__dark h2 { color: var(--wp--preset--color--contrast); font-size: clamp(1.9rem, 3vw, 2.4rem); margin: 0 0 0.85rem; }
.bb-cta__dark h2 em { font-style: normal; color: var(--wp--preset--color--gold); }
.bb-cta__dark p { color: rgba(255,255,255,0.75); margin: 0; font-size: 0.98rem; }
/* No own background any more (inherits the shared `.bb-cta` sand behind
   it - same token, so the seam is invisible by construction) and no
   `margin-left` hack: it now sits exactly in its own grid column, which
   is what makes the fix structural rather than another tuned patch. */
.bb-cta__light {
	padding: clamp(2.5rem, 5vw, 3.5rem);
	position: relative;
	display: flex;
	flex-direction: row;
	align-items: center;
	gap: clamp(1.25rem, 2.5vw, 2rem);
	overflow: hidden;
}
.bb-cta__light-info {
	display: flex;
	flex-direction: column;
	justify-content: center;
	gap: 1.35rem;
	flex: 1 1 auto;
	min-width: 0;
}
.bb-cta__contact-line { display: flex; align-items: center; gap: 0.65rem; font-size: 1.02rem; font-weight: 600; }
.bb-cta__contact-line svg { width: 18px; height: 18px; color: var(--wp--preset--color--gold-deep); flex: 0 0 auto; }
/* Owner review, revision 13: wraps a real `wp:paragraph` now (see
   compose-home.php) instead of holding text directly - zero its default
   block margin; type styling is inherited from `.bb-cta__contact-line`. */
.bb-cta__contact-line p { margin: 0; }
.bb-cta__actions { display: flex; flex-wrap: wrap; gap: 0.65rem; position: relative; z-index: 1; }
/* Compact Google Maps embed (Owner-authorized this round) - "compact"
   is enforced structurally: fixed, modest width band plus a landscape
   (4:3) aspect ratio, so it cannot grow to dominate the card or push
   the contact info/CTAs out; the existing `.bb-cta` grid still stretches
   both halves to the taller (dark) side's height, so the card's overall
   height is governed by the existing text content, not by the map. */
.bb-cta__map {
	flex: 0 0 auto;
	width: clamp(240px, 22vw, 320px);
	aspect-ratio: 4 / 3;
	max-height: 100%;
	border-radius: 6px;
	overflow: hidden;
	box-shadow: 0 0 0 1px var(--wp--preset--color--line);
}
.bb-cta__map iframe {
	display: block;
	width: 100%;
	height: 100%;
	border: 0;
}

/* Owner review, revision 9 - real found cause: at 1024px the outer
   `.bb-cta` grid keeps dark/light side by side (no complaint about
   that), but the *inner* `.bb-cta__light` row was still forcing the
   contact info and the map onto the same line - measured live, that
   left the info column only ~124px wide, wrapping "Schoolstraat 9,
   Hilversum" and "06 4640 8112" onto two lines apiece. The map itself
   was already narrower here (`clamp(200px,26vw,260px)`), it just wasn't
   enough room for both. Fix: the inner light half switches to a single
   column on its own ~1100px breakpoint - independent of the outer
   grid's 900px breakpoint - so the phone number gets its full 512px-ish
   half back and reliably fits on one line, while the map (not stretched
   to `width:100%` here - stays visibly "compact", per the brief) sits
   below it at a controlled width. */
@media (max-width: 1100px) {
	.bb-cta__light { flex-direction: column; align-items: flex-start; gap: 1.5rem; }
	.bb-cta__map { width: clamp(220px, 46vw, 300px); align-self: flex-start; }
}

@media (max-width: 900px) {
	.bb-cta { grid-template-columns: 1fr; border-radius: 0; }
	.bb-cta__dark { clip-path: none; }
	.bb-cta__light { align-items: stretch; }
	.bb-cta__map { width: 100%; aspect-ratio: 16 / 9; align-self: stretch; }
}

/* --- Footer ------------------------------------------------------------ */
.bb-footer {
	background: var(--wp--preset--color--ink);
	color: rgba(255,255,255,0.65);
	padding: clamp(2.5rem, 5vw, 3rem) 0 1.25rem;
}
.bb-footer__grid {
	display: grid;
	grid-template-columns: 1.3fr 1fr 1fr 1fr;
	gap: 2rem;
	max-width: 1280px;
	margin: 0 auto;
	padding: 0 clamp(1.25rem, 4vw, 3rem) clamp(2rem, 4vw, 2.5rem);
	border-bottom: 1px solid rgba(255,255,255,0.1);
}
/* Official footer brand asset (Owner review, revision 2, enlarged
   revision 4, enlarged revision 5): the real supplied complete logo
   (monogram + wordmark in one image) - no separate reconstructed
   "Brahim" script text next to it any more. Square source asset, so
   width/height stay equal (never a fixed-width + fixed-height pair
   fighting a differently-shaped replacement) and both change together
   if the Owner ever swaps it. Revision 5: enlarged to an optically
   balanced desktop width (still the Gutenberg Image block underneath -
   fully editable, replace/relink/alt text all still work normally,
   only the decorative render size is set here). `height: auto` (not a
   second fixed pixel value) so the image's own natural aspect ratio
   drives the height - no cropping/stretching even if the Owner swaps
   in a non-square asset later. The block's own inline
   `style="width:122px;height:auto"` on the <img> needs `!important` on
   width only to be reliably overridden; height already matches "auto"
   so no conflict exists there. */
.bb-footer__brand { margin: 0 0 0.85rem; border-radius: 6px; overflow: hidden; width: 220px; }
.bb-footer__brand img { display: block; width: 220px !important; height: auto; }
.bb-footer__tagline { font-size: 0.85rem; line-height: 1.55; max-width: 26ch; }
.bb-footer h4 {
	font-family: var(--wp--preset--font-family--body);
	font-size: 0.72rem;
	font-weight: 800;
	letter-spacing: 0.14em;
	text-transform: uppercase;
	color: var(--wp--preset--color--gold);
	margin: 0 0 0.9rem;
}
.bb-footer ul { list-style: none; margin: 0; padding: 0; display: flex; flex-direction: column; gap: 0.55rem; }
/* Owner review, revision 4 - real found cause: this rule used to live
   on `.bb-footer a` only, so a plain-text list item with no link (the
   Contact column's street address) fell through to the theme's global
   body type scale instead - rendering roughly 50% larger than every
   sibling item and visibly competing with the column heading. Sizing
   the `<li>` itself, not just its optional `<a>`, makes every footer
   list item match regardless of whether it happens to be a link. */
.bb-footer-list li { color: rgba(255,255,255,0.72); font-size: 0.85rem; line-height: 1.6; }
.bb-footer a { color: rgba(255,255,255,0.72); text-decoration: none; font-size: 0.85rem; }
.bb-footer a:hover { color: var(--wp--preset--color--gold); }
.bb-footer__hours-row { display: flex; justify-content: space-between; align-items: baseline; gap: 1rem; font-size: 0.85rem; line-height: 1.6; }
/* Pre-multi-page editability remediation: `.bb-footer__hours-row` now
   wraps two real, independently central-bound `wp:paragraph` blocks
   instead of two `<span>` inside one paragraph - global styles' default
   paragraph bottom margin is zeroed here so it doesn't add unwanted
   height inside this compact row, matching the identical, already-
   established `.bb-fact p { margin: 0; }` pattern elsewhere in this
   file for the same reason. */
.bb-footer__hours-row p { margin: 0; }
/* Privacy is now a normal item inside the footer's existing "Navigatie"
   list (`.bb-footer-list`) - no separate rules needed, it inherits that
   list's own styling exactly like Home/Over ons/Prijzen/Foto's/Contact.
   ("PILOT 003 - BOUNDED FOOTER + MOBILE HERO FIX" item 2 - the previous
   standalone `.bb-footer__privacy-link` paragraph and its CSS are
   removed, not just hidden.) */
.bb-footer__bottom-row {
	display: flex;
	flex-wrap: wrap;
	justify-content: space-between;
	align-items: baseline;
	gap: 0.3rem 1.25rem;
	max-width: 1280px;
	margin: 0 auto;
	padding: 1.1rem clamp(1.25rem, 4vw, 3rem) 0;
}
.bb-footer__bottom-row > * { margin-top: 0; }
.bb-footer__bottom {
	font-size: 0.78rem;
	opacity: 0.6;
}
/* NextGenBuilds production credit ("PILOT 003 - BOUNDED FOOTER + MOBILE
   HERO FIX" item 3) - plain text, no link (deliberately not clickable
   yet - no destination exists), same muted weight as the copyright line
   beside it. Sits right-aligned via the shared flex row's
   `justify-content: space-between` above; on a narrow viewport the row
   wraps and this drops to its own line rather than overflowing. No icon:
   no genuine NextGenBuilds favicon/brand asset exists anywhere in this
   repository (searched explicitly this round) - text only, per this
   round's own explicit instruction for that case. */
.bb-footer__credit {
	font-size: 0.78rem;
	opacity: 0.6;
	white-space: nowrap;
}

@media (max-width: 900px) {
	.bb-footer__grid { grid-template-columns: 1fr 1fr; }
}
@media (max-width: 540px) {
	.bb-footer__grid { grid-template-columns: 1fr; }
}

/* --- Reveal on scroll (restrained) --------------------------------------- */
@media (prefers-reduced-motion: no-preference) {
	.bb-reveal {
		opacity: 0;
		transform: translateY(16px);
		transition: opacity 0.6s ease, transform 0.6s ease;
	}
	.bb-reveal.is-visible {
		opacity: 1;
		transform: translateY(0);
	}
}

/* ==========================================================================
   PAGE FAMILY - "PILOT 003 - ONE-SHOT MULTI-PAGE WEBSITE COMPLETION"

   Each new page (Over ons, Prijzen, Foto's, Contact) gets its own distinct
   first viewport and composition silhouette (per that instruction's
   Section 7), built from the SAME underlying tokens/typography/palette/
   button language as Home - never a fourth repetition of "heading,
   paragraph, three cards, CTA". Block-gap zeroing follows this file's own
   established pattern (see the `.bb-hero > *` rule near the top of this
   file) wherever a wrapper's children are turned into a row/grid instead
   of stacked flow.
   ========================================================================== */

.bb-page-banner > *,
.bb-about-hero > *,
.bb-about-hero__text > *,
.bb-about-row > *,
.bb-contact-panel > *,
.bb-contact-panel__info > *,
.bb-contact-line > * {
	margin-top: 0;
}

/* --- Shared: compact page banner (Prijzen, Contact) ---------------------
   A shorter, darker cousin of Home's full-viewport hero - same ink
   background + photo + scrim recipe, deliberately NOT full-height, so it
   reads as "a page banner", never as a second homepage hero. */
.bb-page-banner {
	position: relative;
	background: var(--wp--preset--color--ink);
	overflow: hidden;
	min-height: min(46vh, 400px);
	display: flex;
	align-items: flex-end;
}
.bb-page-banner__photo {
	position: absolute;
	inset: 0;
	width: 100%;
	height: 100%;
	object-fit: cover;
}
.bb-page-banner__photo img { display: block; width: 100%; height: 100%; object-fit: cover; }
.bb-page-banner__scrim {
	position: absolute;
	inset: 0;
	background: linear-gradient(0deg, rgba(15,12,8,0.92) 0%, rgba(15,12,8,0.62) 55%, rgba(15,12,8,0.28) 100%);
}
.bb-page-banner__content {
	position: relative;
	z-index: 2;
	max-width: 1280px;
	width: 100%;
	margin: 0 auto;
	padding: clamp(2.5rem, 6vw, 3.75rem) clamp(1.25rem, 4vw, 3rem) clamp(2.25rem, 5vw, 3rem);
}
.bb-page-banner__content .bb-eyebrow { color: var(--wp--preset--color--gold); }
.bb-page-banner__content h1 {
	font-family: var(--wp--preset--font-family--display);
	font-weight: 640;
	font-size: clamp(2.2rem, 5vw, 3.4rem);
	line-height: 1.06;
	color: var(--wp--preset--color--contrast);
	margin: 0 0 0.75rem;
}
.bb-page-banner__content h1 em { font-style: normal; color: var(--wp--preset--color--gold); }
.bb-page-banner__content p {
	color: rgba(255,255,255,0.82);
	font-size: 1.02rem;
	max-width: 52ch;
	margin: 0;
}
@media (max-width: 720px) {
	.bb-page-banner { min-height: min(52vh, 340px); }
}

/* --- Over ons: editorial asymmetric intro -------------------------------
   Deliberately NOT a photographic full-viewport hero (that silhouette is
   Home's) and NOT a dark banner (that's Prijzen/Contact) - a light,
   asymmetric two-column editorial split on sand, oversized display type
   doing the work instead of a photo dominating the frame. */
.bb-about-hero {
	background: var(--wp--preset--color--sand);
	display: grid;
	grid-template-columns: 0.9fr 1.1fr;
	align-items: stretch;
	gap: clamp(1.5rem, 4vw, 3rem);
	max-width: 1280px;
	margin: 0 auto;
	padding: clamp(2.5rem, 6vw, 4rem) clamp(1.25rem, 4vw, 3rem);
}
.bb-about-hero__photo {
	border-radius: 6px;
	overflow: hidden;
	/* Asymmetric: bleeds slightly above the text column's own top edge -
	   the offset that makes this read as "editorial", not "Home's grid,
	   recolored". */
	margin-top: -1.5rem;
	align-self: stretch;
}
.bb-about-hero__photo img { width: 100%; height: 100%; object-fit: cover; display: block; min-height: 320px; }
.bb-about-hero__text { display: flex; flex-direction: column; justify-content: center; }
.bb-about-hero__text .bb-eyebrow { color: var(--wp--preset--color--gold-deep); }
.bb-about-hero__kicker {
	font-family: var(--wp--preset--font-family--display);
	font-style: italic;
	font-weight: 420;
	font-size: clamp(3.5rem, 9vw, 6.5rem);
	line-height: 0.9;
	color: var(--wp--preset--color--gold-deep);
	margin: 0 0 0.5rem;
}
.bb-about-hero__text h1 {
	font-size: clamp(1.9rem, 3.4vw, 2.7rem);
	margin: 0 0 1rem;
}
.bb-about-hero__text p { font-size: 1.02rem; line-height: 1.68; color: rgba(21,18,13,0.78); margin: 0; max-width: 46ch; }
@media (max-width: 900px) {
	.bb-about-hero { grid-template-columns: 1fr; }
	.bb-about-hero__photo { margin-top: 0; order: -1; }
	.bb-about-hero__photo img { min-height: 240px; }
}

/* --- Over ons: history/craft rows (two-up, alternating) - a narrower,
   two-column cousin of `.bb-story`'s three-column rhythm, so the two
   pages read as the same family without being the same grid. ---------- */
.bb-about-row {
	display: grid;
	grid-template-columns: 1fr 1fr;
	align-items: center;
	gap: clamp(1.5rem, 4vw, 3rem);
	max-width: 1280px;
	margin: 0 auto;
	padding: clamp(3rem, 6vw, 4.5rem) clamp(1.25rem, 4vw, 3rem);
}
.bb-about-row--reverse .bb-about-row__photo { order: 2; }
.bb-about-row__photo { border-radius: 6px; overflow: hidden; }
.bb-about-row__photo img { width: 100%; height: 100%; object-fit: cover; display: block; min-height: 280px; }
/* Owner review ("COMPLETE THE TWO REMAINING VISUAL FIXES"): the
   "Persoonlijke aandacht" row's photo only (CVDF9886, attachment 9) was
   cropping Brahim's head off the top under `object-fit: cover`'s default
   center focal point. Scoped to `.bb-about-row--reverse` specifically -
   the OTHER row ("Herkomst en vakmanschap") keeps the general rule's
   default centered focal point untouched. Container size, border-radius
   and `object-fit: cover` composition are unchanged; only the vertical
   anchor point moves, so nothing stretches or distorts. */
.bb-about-row--reverse .bb-about-row__photo img { object-position: center top; }
.bb-about-row__text h2 { font-size: clamp(1.7rem, 2.8vw, 2.2rem); margin: 0 0 0.9rem; }
.bb-about-row__text h2 em { font-style: normal; color: var(--wp--preset--color--gold-deep); }
.bb-about-row__text p { font-size: 0.98rem; line-height: 1.7; color: rgba(21,18,13,0.78); margin: 0 0 0.85rem; }
@media (max-width: 900px) {
	.bb-about-row { grid-template-columns: 1fr; }
	.bb-about-row--reverse .bb-about-row__photo { order: -1; }
	.bb-about-row__photo img { min-height: 220px; }
}

/* --- Over ons: full-width atmosphere band - a silhouette Home never
   uses (a single wide photographic band, no text over it) ------------- */
.bb-about-atmosphere { position: relative; height: clamp(240px, 42vw, 460px); overflow: hidden; }
.bb-about-atmosphere img { width: 100%; height: 100%; object-fit: cover; display: block; }

/* --- Over ons: closing action (lighter than Home's dark `.bb-cta` split
   panel - deliberately a different, calmer close) ---------------------- */
.bb-about-close {
	text-align: center;
	max-width: 640px;
	margin: 0 auto;
	padding: clamp(3rem, 6vw, 4.5rem) clamp(1.25rem, 4vw, 3rem);
}
.bb-about-close .bb-eyebrow { color: var(--wp--preset--color--gold-deep); }
.bb-about-close h2 { font-size: clamp(1.7rem, 2.8vw, 2.3rem); margin: 0 0 0.75rem; }
.bb-about-close p { font-size: 1rem; color: rgba(21,18,13,0.75); margin: 0 0 1.5rem; }
.bb-about-close .wp-block-buttons { justify-content: center; }

/* --- Prijzen: reused central service-list block, skinned to match
   `.bb-price-row` without touching the generic block's own markup/CSS
   file (STD-003 SS2a-adjacent discipline: theme owns presentation, the
   OS block owns data/structure). Two-column on wide screens - a denser,
   more "complete catalog" rhythm than Home's single-column 3-item
   preview, per this instruction's own "precise alignment" brief. ------- */
.bb-prijzen-list-wrap { max-width: 1280px; margin: 0 auto; padding: clamp(3rem, 6vw, 4.5rem) clamp(1.25rem, 4vw, 3rem) clamp(1.5rem, 3vw, 2rem); }
.bb-prijzen-list-wrap > .bb-eyebrow { color: var(--wp--preset--color--gold-deep); text-align: center; display: block; }
.bb-prijzen-list-wrap > h2 { text-align: center; font-size: clamp(1.9rem, 3.2vw, 2.6rem); margin: 0 auto 2.5rem; max-width: 32ch; }
.ngb-service-list {
	list-style: none;
	margin: 0;
	padding: 0;
	columns: 2;
	column-gap: clamp(2rem, 4vw, 3.5rem);
}
.ngb-service-list li { break-inside: avoid; }
.ngb-service-list > li > div {
	padding: 0.9rem 0;
	border-bottom: 1px solid var(--wp--preset--color--line);
}
.ngb-service-list__name {
	font-size: 1.02rem;
	font-weight: 500;
	color: var(--wp--preset--color--ink);
}
.ngb-service-list__price {
	font-family: var(--wp--preset--font-family--display);
	font-weight: 700;
	font-size: 1.15rem;
	color: var(--wp--preset--color--gold-deep);
	white-space: nowrap;
}
/* Subtle emphasis for the treatment this instruction singles out
   ("Gezichtsbehandeling (30 minuten)") - targets the LAST row of the
   central catalog structurally (that service is seeded last), not by
   matching its name in CSS, so this stays a generic, content-neutral
   rule rather than a hardcoded string coupling. If the catalog is ever
   reordered in Settings -> Service Catalog so a different service ends
   up last, the emphasis moves with it - disclosed here, not a hidden
   assumption. Scoped to the Prijzen page's own wrapper only - Home's
   3-item preview (below) reuses this same block with a `serviceIds`
   subset that never includes the catalog's actual last item, but is
   scoped out explicitly anyway rather than relying on that coincidence. */
.bb-prijzen-list-wrap .ngb-service-list > li:last-child > div {
	background: var(--wp--preset--color--sand);
	margin: 0.35rem -0.9rem 0;
	padding: 0.9rem 0.9rem;
	border-radius: 4px;
	border-bottom: 1px solid transparent;
}
@media (max-width: 720px) {
	.ngb-service-list { columns: 1; }
}

/* --- Home's 3-item preview: the SAME reused `nextgenbuilds/service-list`
   block (a `serviceIds` subset), skinned here to match the previously
   hand-typed `.bb-price-row` look this Standard's approved baseline
   established - controlled Home adaptation B ("PILOT 003 - ONE-SHOT
   MULTI-PAGE WEBSITE COMPLETION"): swapped from Home's own static
   per-row markup to this central, live-rendered block specifically so a
   central price edit updates this preview too (Requirement 5 - "changing
   one central price must update every displayed occurrence"), which a
   baked-in static row could never satisfy. The one disclosed visual
   difference from the original approved rows: a single shared decorative
   icon (CSS `::before`, not a per-service icon choice - the generic
   block has no icon concept, and none of Home's 3 preview items ever
   used a different icon anyway) replaces the original inline-SVG icon
   markup. Everything else - divider, type scale, price color/weight,
   spacing, the surrounding shell/photo/heading - is pixel-identical to
   the approved baseline. */
.bb-price-list .ngb-service-list {
	list-style: none;
	margin: 0 0 1rem;
	padding: 0;
	columns: 1;
}
.bb-price-list .ngb-service-list > li > div {
	display: flex;
	align-items: baseline;
	gap: 0.75rem;
	padding: 0.85rem 0 0.85rem 1.7rem;
	border-bottom: 1px solid var(--wp--preset--color--line);
	position: relative;
}
.bb-price-list .ngb-service-list > li > div::before {
	content: "";
	position: absolute;
	left: 0;
	top: 50%;
	transform: translateY(-50%);
	width: 18px;
	height: 18px;
	background: url("data:image/svg+xml,%3Csvg xmlns='http://www.w3.org/2000/svg' viewBox='0 0 24 24' fill='none' stroke='%239C7530' stroke-width='1.8'%3E%3Ccircle cx='6' cy='8.2' r='2.2'/%3E%3Ccircle cx='6' cy='15.8' r='2.2'/%3E%3Cpath d='M7.6 8.2 20 20M7.6 15.8 20 4'/%3E%3C/svg%3E") no-repeat center / contain;
}
.bb-price-list .ngb-service-list__name { flex: 1 1 auto; font-size: 1rem; font-weight: 500; color: var(--wp--preset--color--ink); }
.bb-price-list .ngb-service-list__price {
	margin: 0;
	flex: 0 0 auto;
	font-family: var(--wp--preset--font-family--display);
	font-weight: 700;
	font-size: 1.15rem;
	color: var(--wp--preset--color--gold-deep);
	white-space: nowrap;
}
.bb-prices__cta { margin-top: 0.5rem; }
.bb-prijzen-actions {
	max-width: 1280px;
	margin: 0 auto;
	padding: 0 clamp(1.25rem, 4vw, 3rem) clamp(2.5rem, 5vw, 3.5rem);
	text-align: center;
}
.bb-prijzen-actions .bb-fact {
	display: inline-flex;
	margin: 0 auto 1.5rem;
	color: var(--wp--preset--color--ink);
	border-color: var(--wp--preset--color--line);
}
.bb-prijzen-actions .bb-fact svg { color: var(--wp--preset--color--gold-deep); }
.bb-prijzen-actions .wp-block-buttons { justify-content: center; }
.bb-prijzen-close { position: relative; height: clamp(220px, 36vw, 400px); overflow: hidden; }
.bb-prijzen-close img { width: 100%; height: 100%; object-fit: cover; display: block; }

/* --- Foto's: restrained intro (no banner at all - the gallery grid
   itself is this page's "first viewport" identity, a silhouette none
   of the other pages use) + the reused central gallery block, skinned
   to match this project's rounded/gold visual language on top of its
   generic, unmodified grid/lightbox markup. ----------------------------- */
.bb-fotos-intro {
	max-width: 720px;
	margin: 0 auto;
	padding: clamp(3rem, 6vw, 4rem) clamp(1.25rem, 4vw, 3rem) clamp(1.5rem, 3vw, 2rem);
	text-align: center;
}
.bb-fotos-intro .bb-eyebrow { color: var(--wp--preset--color--gold-deep); }
.bb-fotos-intro h1 { font-size: clamp(1.9rem, 3.2vw, 2.6rem); margin: 0 0 0.75rem; }
.bb-fotos-intro p { font-size: 1rem; color: rgba(21,18,13,0.75); margin: 0; }

/* PILOT 003 PRIVACY PAGE VISUAL + CONTACT BLOCK CORRECTION: scoped to
   the Privacy page only via .bb-privacy-page (added to that page's own
   content wrappers, not a bare `h1`/`h2` selector) - every other page
   keeps the theme's normal serif (Fraunces) headings untouched. Only
   the font-family changes; size, color, margin, weight and responsive
   behavior are deliberately inherited unchanged from the theme's
   existing heading styles (theme.json's heading element: 600 weight,
   1.12 line-height, -0.01em letter-spacing all still apply). */
.bb-privacy-page h1,
.bb-privacy-page h2 {
	font-family: var(--wp--preset--font-family--body);
}
/* Compact three-line address block (street / postcode+city / country),
   each line its own block-bound paragraph so each stays wired to the
   central bb/business-info source - tightened spacing only applies
   between these specific lines, not paragraphs generally. */
.bb-privacy-address {
	display: flex;
	flex-direction: column;
	gap: 0;
}
.bb-privacy-address p {
	margin: 0 0 0.2em;
	line-height: 1.4;
}
.bb-privacy-address p:last-child {
	margin-bottom: 0;
}

.ngb-gallery { max-width: 1280px; margin: 0 auto; padding: 0 clamp(1.25rem, 4vw, 3rem) clamp(3rem, 6vw, 4.5rem); }
.ngb-gallery__grid {
	list-style: none;
	margin: 0;
	padding: 0;
	display: grid;
	grid-template-columns: repeat(auto-fill, minmax(220px, 1fr));
	gap: 0.6rem;
}
.ngb-gallery__item { margin: 0; }
.ngb-gallery__trigger {
	display: block;
	width: 100%;
	padding: 0;
	border: 0;
	background: none;
	cursor: pointer;
	border-radius: 4px;
	overflow: hidden;
	aspect-ratio: 4 / 5;
}
.ngb-gallery__trigger:focus-visible { outline: 2px solid var(--wp--preset--color--gold); outline-offset: 2px; }
.ngb-gallery__thumb { width: 100%; height: 100%; object-fit: cover; display: block; transition: transform 0.5s ease; }
.ngb-gallery__trigger:hover .ngb-gallery__thumb { transform: scale(1.04); }
/* Desktop gallery: a restrained six-column editorial rhythm. The
   explicit placement fills every row for this curated twelve-image set,
   removing the accidental sparse final row without a masonry gimmick. */
@media (min-width: 901px) {
	.ngb-gallery__grid {
		grid-template-columns: repeat(6, minmax(0, 1fr));
		grid-auto-rows: clamp(132px, 10vw, 150px);
		grid-auto-flow: dense;
	}
	.ngb-gallery__item { grid-column: span 2; grid-row: span 2; }
	.ngb-gallery__item:nth-child(2),
	.ngb-gallery__item:nth-child(4) { grid-row: span 1; }
	.ngb-gallery__item:nth-child(8),
	.ngb-gallery__item:nth-child(9) { grid-column: span 3; }
	.ngb-gallery__trigger { height: 100%; aspect-ratio: auto; }
}
@media (max-width: 560px) {
	.ngb-gallery__grid { grid-template-columns: repeat(auto-fill, minmax(150px, 1fr)); gap: 0.4rem; }
}

/* --- Contact: compact page banner reuses `.bb-page-banner` above, plus
   a dedicated info+map panel - a bigger, page-primary map treatment
   than Home's compact corner map (this page's actual purpose), not a
   restyled copy of `.bb-cta`. ------------------------------------------ */
.bb-contact-panel {
	display: grid;
	grid-template-columns: 1fr 1.2fr;
	gap: clamp(2rem, 4vw, 3rem);
	align-items: stretch;
	max-width: 1280px;
	margin: 0 auto;
	padding: clamp(3rem, 6vw, 4.5rem) clamp(1.25rem, 4vw, 3rem);
}
.bb-contact-panel__info { display: flex; flex-direction: column; justify-content: center; gap: 1.5rem; }
.bb-contact-panel__info .bb-eyebrow { color: var(--wp--preset--color--gold-deep); }
.bb-contact-panel__info h2 { font-size: clamp(1.7rem, 2.8vw, 2.2rem); margin: 0; }
.bb-contact-line { display: flex; align-items: flex-start; gap: 0.75rem; font-size: 1rem; }
.bb-contact-line svg { width: 20px; height: 20px; color: var(--wp--preset--color--gold-deep); flex: 0 0 auto; margin-top: 0.15rem; }
.bb-contact-line p { margin: 0; line-height: 1.6; }
/* Opening hours on Contact - bound rows (see compose-pages.php), same
   block-gap concern as `.bb-footer__hours-row` (this file's own
   established pattern - see that rule's docblock near the top of this
   file for the full root cause). */
.bb-contact-hours { display: flex; flex-direction: column; gap: 0.3rem; flex: 1 1 auto; }
.bb-contact-hours__row { display: flex; justify-content: space-between; gap: 1rem; max-width: 22rem; }
.bb-contact-hours__row > * { margin-top: 0; }
.bb-contact-hours__row p:first-child { color: rgba(21,18,13,0.6); }
.bb-contact-hours__row p:last-child { font-weight: 600; }
.bb-contact-panel__info .wp-block-buttons { display: flex; flex-wrap: wrap; gap: 0.65rem; }
/* `barber-brahim/maps-embed` (functions.php's bb_render_maps_embed_block())
   always renders its own `.bb-cta__map` class on its wrapper - reused
   here unmodified (same centrally-addressed dynamic block Home uses),
   just given a bigger box via this wrapping container instead of forking
   the block for a second class name. */
.bb-contact-map {
	border-radius: 6px;
	overflow: hidden;
	min-height: 360px;
	box-shadow: 0 0 0 1px var(--wp--preset--color--line);
}
.bb-contact-map .bb-cta__map {
	width: 100%;
	height: 100%;
	aspect-ratio: auto;
	min-height: 360px;
	border-radius: 0;
	box-shadow: none;
}
.bb-contact-map iframe { display: block; width: 100%; height: 100%; border: 0; min-height: 360px; }
@media (max-width: 900px) {
	.bb-contact-panel { grid-template-columns: 1fr; }
	/* Keep the primary contact facts/actions before the supporting map on
	   narrow screens; desktop retains the approved side-by-side layout. */
	.bb-contact-map { min-height: 320px; }
	.bb-contact-map .bb-cta__map,
	.bb-contact-map iframe { min-height: 320px; }
}

/* ---------------------------------------------------------------------
 * Google Reviews (ADR-004 v0.2; "GOOGLE REVIEWS CAPABILITY - ONE-SHOT
 * NATIVE MODULE IMPLEMENTATION + FIXTURE QA", 2026-08-25) - bounded
 * project-specific skin over the reusable module's unstyled, generic
 * markup classes (`.ngb-reviews*`, os-wordpress/assets/css/ngb-reviews.
 * css, loaded first and left untouched - this file only adds Pilot-3's
 * own cream/gold/ink visual system on top, same layering convention as
 * `.ngb-gallery`/`.ngb-service-list` above). Reviews remains disabled
 * pending a real Google connection (site-spec.json `reviews.enabled:
 * false`) - this skin has no visible effect on the live site yet; it is
 * prepared ahead of that connection so enabling it later is a settings
 * change, not a styling task.
 *
 * Signature idea (frontend-design, bounded to this one component): each
 * card carries a single oversized gold serif quotation mark bleeding off
 * its own top-left corner - a quiet callback to the display typeface
 * already used for pull quotes/headings elsewhere on this site, so a
 * review reads as "a customer's word", not a generic testimonial-widget
 * card. Deliberately not a star-rating-forward layout (every stock
 * review widget leads with stars) - the text leads, the rating is
 * secondary meta.
 * --------------------------------------------------------------------- */
.ngb-reviews {
	max-width: 1280px;
	margin: 0 auto;
	padding: clamp(3rem, 6vw, 4.5rem) clamp(1.25rem, 4vw, 3rem);
}
.ngb-reviews__heading {
	font-family: var(--wp--preset--font-family--display);
	color: var(--wp--preset--color--ink);
	font-size: var(--wp--preset--font-size--x-large);
	margin: 0 0 0.5rem;
	text-align: center;
}
.ngb-reviews__copy {
	color: var(--wp--preset--color--ink-soft);
	text-align: center;
	max-width: 42rem;
	margin: 0 auto 2.5rem;
}
.ngb-reviews--grid .ngb-reviews__list {
	grid-template-columns: repeat(auto-fill, minmax(280px, 1fr));
	gap: 1.75rem;
}
.ngb-reviews__item {
	position: relative;
	background: var(--wp--preset--color--cream);
	border: 1px solid var(--wp--preset--color--line);
	border-radius: 6px;
	padding: 2.25rem 1.5rem 1.5rem;
	overflow: hidden;
}
.ngb-reviews__item::before {
	content: "\201C";
	position: absolute;
	top: -0.6rem;
	left: 0.75rem;
	font-family: var(--wp--preset--font-family--display);
	font-size: 4.5rem;
	line-height: 1;
	color: var(--wp--preset--color--gold);
	opacity: 0.55;
	pointer-events: none;
}
.ngb-reviews__meta {
	font-size: 0.9rem;
}
.ngb-reviews__name {
	font-weight: 600;
	color: var(--wp--preset--color--ink);
}
.ngb-reviews__rating {
	color: var(--wp--preset--color--gold-deep);
	letter-spacing: 0.05em;
}
.ngb-reviews__date {
	color: var(--wp--preset--color--ink-soft);
}
.ngb-reviews__text {
	color: var(--wp--preset--color--ink);
	line-height: 1.6;
}
.ngb-reviews__source-link {
	color: var(--wp--preset--color--gold-deep);
	text-decoration: none;
	border-bottom: 1px solid transparent;
}
.ngb-reviews__source-link:hover,
.ngb-reviews__source-link:focus-visible {
	border-bottom-color: currentColor;
}
.ngb-reviews__attribution {
	text-align: center;
	color: var(--wp--preset--color--ink-soft);
	margin-top: 2.5rem;
}
.ngb-reviews--editor-preview .ngb-reviews__preview-notice {
	background: var(--wp--preset--color--sand);
	color: var(--wp--preset--color--ink);
	border-radius: 4px;
	padding: 0.6rem 0.9rem;
	margin: 0 0 1.5rem;
	text-align: center;
}
@media (max-width: 600px) {
	.ngb-reviews__item { padding: 2rem 1.1rem 1.25rem; }
}
