/*
 * Park Minigolf — WooCommerce / Bookings skin.
 *
 * The booking product, cart and checkout pages are rendered by WooCommerce, not
 * from the design's HTML files, so they arrive wearing the old theme. This
 * restyles that markup to match the rest of the site.
 *
 * Everything is scoped under .pmg-shop, a body class the plugin adds only on
 * booking products, cart, checkout and order-received. Nothing here can reach
 * the client's other WooCommerce pages unless that class is present.
 *
 * Selectors come from the real rendered markup and from the Bookings plugin's
 * own dist/frontend.css, not from guesswork -- the date picker is jQuery UI
 * (.ui-datepicker), the slot list is .block-picker, and Bookings marks days with
 * .bookable / .fully_booked / .not_bookable_by_rules.
 */

/* Tokens come from tokens.css, which base.css carries on :root -- this block
   used to declare its own copy, and its --muted was still #647565, the value
   the rest of the site moved off for contrast. That is why the checkout's grey
   text was lighter than every other page. */
.pmg-shop {
	margin: 0;
	background: var(--cream);
	color: var(--ink);
	font-family: Inter, ui-sans-serif, system-ui, -apple-system, BlinkMacSystemFont, "Segoe UI", sans-serif;
	line-height: 1.45;
}

.pmg-shop *, .pmg-shop *::before, .pmg-shop *::after { box-sizing: border-box; }

/* ---------------------------------------------------------------- layout -- */

.pmg-shop .pmg-shop-main {
	width: min(1380px, calc(100% - 42px));
	margin: auto;
	padding: 54px 0 90px;
}

.pmg-shop .pmg-shop-inner {
	max-width: 1040px;
	margin: auto;
}

/*
 * A breadcrumb back into the design's own pages. WooCommerce's breadcrumb is
 * hidden below; this one is rendered by the template so it always points at the
 * Broneeri page wherever that lives.
 */
/* The rule belongs to the word, not to the arrow, so it is drawn on the span
   the template wraps the word in -- underlining the link itself would carry it
   under the arrow and the gap too. */
.pmg-shop .pmg-back {
	display: inline-block;
	margin: 0 0 26px;
	font-weight: 800;
	font-size: 15px;
	color: var(--muted);
	text-decoration: none;
	transition: color .2s ease;
}
.pmg-shop .pmg-back:hover { color: var(--ink); }
.pmg-shop .pmg-back::before { content: "\2190"; font-size: 17px; padding-right: 8px; }
.pmg-shop .pmg-back span {
	text-decoration: underline;
	text-underline-offset: 4px;
	text-decoration-thickness: 2px;
}

/* --------------------------------------------------------- product header -- */

/*
 * The product page markup is the plugin's own (templates/shop-page.php), not
 * WooCommerce's, so these are our class names. The theme's own title hook is
 * never called -- UiCore replaces it, and its replacement is dequeued here --
 * which is why the page had no heading at all before.
 */
.pmg-shop .pmg-product__title {
	font-size: clamp(40px, 4.6vw, 62px);
	line-height: .98;
	letter-spacing: -.045em;
	font-weight: 950;
	margin: 0 0 12px;
	color: var(--ink);
}

.pmg-shop .pmg-product__price {
	font-size: 30px;
	font-weight: 950;
	letter-spacing: -.02em;
	color: var(--green-dark);
	margin: 0 0 16px;
}
.pmg-shop .pmg-product__price .woocommerce-Price-amount { color: inherit; }

.pmg-shop .pmg-product__desc {
	font-size: 18px;
	color: var(--muted);
	max-width: 62ch;
	margin: 0 0 4px;
}
.pmg-shop .pmg-product__desc p { margin: 0 0 10px; }

/*
 * These products are virtual and have no imagery, so WooCommerce renders its
 * grey placeholder frame. Hidden rather than filled: an empty picture box above
 * a booking calendar is worse than no picture box.
 *
 * The tab strip, breadcrumb, related products and per-product meta are all
 * theme furniture that the design has no place for.
 */
.pmg-shop .woocommerce-product-gallery,
.pmg-shop .woocommerce-product-gallery--without-images,
.pmg-shop .woocommerce-tabs,
.pmg-shop .woocommerce-breadcrumb,
.pmg-shop .related,
.pmg-shop .upsells,
.pmg-shop .product_meta {
	display: none !important;
}

/* Undo the theme's two-column product layout now the gallery is gone. */
.pmg-shop .product .summary,
.pmg-shop .product .entry-summary {
	width: 100% !important;
	float: none !important;
	margin: 0 !important;
	padding: 0 !important;
}

/* ---------------------------------------------------------- booking form -- */

/*
 * ONE card, not two. Bookings nests .wc-bookings-booking-form inside form.cart,
 * so styling both as cards drew a box inside a box. The form is the card; the
 * inner wrapper is left as a plain block.
 */
.pmg-shop form.cart {
	background: var(--white);
	border: 1px solid var(--line);
	border-radius: var(--radius);
	box-shadow: var(--shadow);
	padding: 32px;
	margin: 30px 0 0;
}
.pmg-shop .wc-bookings-booking-form {
	background: none;
	border: 0;
	border-radius: 0;
	box-shadow: none;
	padding: 0;
	margin: 0;
	display: block;
}

.pmg-shop .wc-bookings-booking-form .form-field {
	margin: 0 0 22px;
	padding: 0;
	float: none;
	width: 100%;
}

.pmg-shop .wc-bookings-booking-form label {
	display: block;
	font-weight: 900;
	font-size: 13px;
	letter-spacing: .07em;
	text-transform: uppercase;
	color: var(--muted);
	margin: 0 0 10px;
}

.pmg-shop .wc-bookings-booking-form input[type="number"],
.pmg-shop .wc-bookings-booking-form input[type="text"],
.pmg-shop .wc-bookings-booking-form select {
	width: 100%;
	padding: 13px 16px;
	border: 1.5px solid var(--line);
	border-radius: 14px;
	background: var(--white);
	font: inherit;
	color: var(--ink);
	transition: border-color .2s ease, box-shadow .2s ease;
}
.pmg-shop .wc-bookings-booking-form input:focus,
.pmg-shop .wc-bookings-booking-form select:focus {
	outline: none;
	border-color: var(--green);
	box-shadow: 0 0 0 4px rgba(108, 194, 71, .18);
}

.pmg-shop .wc-bookings-date-picker-timezone-block {
	font-size: 13px;
	color: var(--muted);
	margin-top: 8px;
}

/* ------------------------------------------------- booking form layout -- */

/*
 * Two columns from 900px up: calendar on the left, everything that follows from
 * it -- time slots, price, any per-product fields -- on the right.
 *
 * The form was stacking, which left a 420px calendar sitting in a 1040px card
 * with the right half empty and the slot list a long way below the date you had
 * just clicked. Nothing here changes the markup: Bookings emits the picker as
 * the first child of #wc-bookings-booking-form and there is no wrapper around
 * the rest, so the split is done by putting *every* child in column 2 and then
 * pulling the picker back into column 1, where it spans the explicit rows.
 *
 * Three explicit rows cover the two hourly products (picker / slots / price).
 * The client's party products have extra fields -- persons, duration, resource
 * -- and those land in implicit rows in column 2 underneath. That degrades to a
 * taller right column rather than breaking.
 */
@media (min-width: 900px) {
	/*
	 * The submit button is a sibling of the booking form, not a child of it, so
	 * it does not take part in the two-column split below and was left sitting
	 * under the calendar -- away from the total it is confirming. The outer form
	 * repeats the same column track so the button can be dropped into column 2,
	 * directly beneath the price.
	 */
	.pmg-shop form.cart {
		display: grid;
		grid-template-columns: minmax(0, 420px) minmax(0, 1fr);
		column-gap: 38px;
	}
	.pmg-shop form.cart > * { grid-column: 1 / -1; }
	.pmg-shop form.cart > .wc-bookings-booking-form-button { grid-column: 2; }

	.pmg-shop #wc-bookings-booking-form {
		display: grid;
		grid-template-columns: minmax(0, 420px) minmax(0, 1fr);
		grid-template-rows: auto auto 1fr;
		column-gap: 38px;
		row-gap: 20px;
		align-items: start;
	}
	.pmg-shop #wc-bookings-booking-form > * { grid-column: 2; min-width: 0; margin: 0; }
	.pmg-shop #wc-bookings-booking-form > .wc-bookings-date-picker {
		grid-column: 1;
		grid-row: 1 / -1;
	}
}

/* ------------------------------------------------------------- calendar -- */

/*
 * jquery-ui-style is dequeued for these pages (see pmg_pages_shop_assets), so
 * there is no widget theme underneath: no gradient header, no .ui-corner-all
 * rounding, no state colours. Everything the calendar looks like is here.
 */
.pmg-shop .wc-bookings-date-picker .ui-datepicker,
.pmg-shop .ui-datepicker,
.pmg-shop .ui-datepicker-inline {
	width: 100%;
	max-width: 420px;
	border: 1px solid var(--line);
	border-radius: 20px;
	background: var(--white);
	padding: 16px;
	box-shadow: none;
	font-family: inherit;
}

.pmg-shop .ui-datepicker-header {
	position: relative;
	background: none;
	border: 0;
	padding: 2px 0 12px;
	display: flex;
	align-items: center;
	justify-content: space-between;
	color: var(--ink);
	font-weight: 950;
}

.pmg-shop .ui-datepicker-title {
	order: 2;
	font-weight: 950;
	font-size: 17px;
	letter-spacing: -.01em;
	color: var(--ink);
	text-align: center;
	flex: 1;
}

/*
 * Bookings sets these as `.wc-bookings-date-picker .ui-datepicker
 * .ui-datepicker-prev` (0,3,0) with a #999 background, which outranks a plain
 * `.pmg-shop .ui-datepicker-prev` (0,2,0) -- that is why the arrows stayed grey
 * blocks. The longer selector below matches its depth.
 */
.pmg-shop .wc-bookings-date-picker .ui-datepicker .ui-datepicker-prev,
.pmg-shop .wc-bookings-date-picker .ui-datepicker .ui-datepicker-next,
.pmg-shop .ui-datepicker-prev,
.pmg-shop .ui-datepicker-next {
	position: static;
	background: var(--soft);
	border-radius: 999px;
	height: 36px;
	width: 36px;
	top: auto;
	width: 36px;
	height: 36px;
	border-radius: 999px;
	background: var(--soft);
	border: 0;
	cursor: pointer;
	display: flex;
	align-items: center;
	justify-content: center;
	transition: background .2s ease;
	top: auto;
	left: auto;
	right: auto;
}
.pmg-shop .ui-datepicker-prev { order: 1; }
.pmg-shop .ui-datepicker-next { order: 3; }
.pmg-shop .ui-datepicker-prev:hover,
.pmg-shop .ui-datepicker-next:hover { background: var(--line); }
.pmg-shop .ui-datepicker-prev.ui-state-disabled,
.pmg-shop .ui-datepicker-next.ui-state-disabled { opacity: .3; cursor: default; }

/*
 * jQuery UI renders the arrows as <a><span class="ui-icon">Prev</span></a> and
 * relies on its sprite plus text-indent to hide the word. With that stylesheet
 * gone the literal "Prev"/"Next" would show, so the span is hidden outright and
 * the glyph drawn on the anchor instead.
 */
.pmg-shop .ui-datepicker-prev span,
.pmg-shop .ui-datepicker-next span { display: none; }
.pmg-shop .ui-datepicker-prev::before { content: "‹"; font-size: 26px; line-height: 1; color: var(--ink); }
.pmg-shop .ui-datepicker-next::before { content: "›"; font-size: 26px; line-height: 1; color: var(--ink); }

/*
 * `border-collapse: separate` rather than `collapse`, and the gap between days
 * comes from border-spacing rather than td padding. Padding was the original
 * approach and it lost: something in the WooCommerce/theme cascade zeroes
 * `td { padding }` here, so every day cell butted against its neighbours. Two
 * things went wrong at once -- the green available days fused into solid slabs
 * one row tall, and where four 12px rounded corners met they left a little
 * four-pointed star of background showing through, scattered across the grid.
 * border-spacing is a table property, nothing else in the cascade sets it, and
 * it cannot be zeroed by a td rule.
 */
.pmg-shop .ui-datepicker-calendar { width: 100%; border-collapse: separate; border-spacing: 5px; margin: -5px; }
.pmg-shop .ui-datepicker-calendar th {
	font-size: 12px;
	font-weight: 900;
	letter-spacing: .06em;
	text-transform: uppercase;
	color: var(--muted);
	padding: 8px 0;
	border: 0;
	background: none;
}
.pmg-shop .ui-datepicker-calendar td { padding: 0; border: 0; background: none; }

.pmg-shop .ui-datepicker-calendar td a,
.pmg-shop .ui-datepicker-calendar td span {
	display: flex;
	align-items: center;
	justify-content: center;
	aspect-ratio: 1;
	border-radius: 12px;
	font-weight: 800;
	font-size: 15px;
	border: 0;
	background: var(--soft);
	color: var(--ink);
	text-align: center;
	transition: background .18s ease, color .18s ease, transform .18s ease;
}

.pmg-shop .ui-datepicker-calendar td a:hover {
	background: var(--green);
	color: var(--on-green);
	transform: translateY(-1px);
}

/* Bookings' own day states. Unbookable days must read as flat and dead. */
.pmg-shop .ui-datepicker-calendar td.ui-datepicker-unselectable span,
.pmg-shop .ui-datepicker-calendar td.not_bookable_by_rules span,
.pmg-shop .ui-datepicker-calendar td.unavailable span {
	background: transparent;
	color: #C3CFC2;
}
/* Same !important problem as .bookable: Bookings forces #792d2a on a full day. */
.pmg-shop .wc-bookings-date-picker .ui-datepicker .ui-datepicker-calendar td.fully_booked:not(.not_bookable_by_rules) a,
.pmg-shop .wc-bookings-date-picker .ui-datepicker .ui-datepicker-calendar td.fully_booked:not(.not_bookable_by_rules) span,
.pmg-shop .ui-datepicker-calendar td.fully_booked a,
.pmg-shop .ui-datepicker-calendar td.fully_booked span {
	background-color: #F6E3E0 !important;
	color: #A8564A !important;
	text-shadow: none !important;
	border-color: transparent !important;
	text-decoration: line-through;
}
.pmg-shop .wc-bookings-date-picker .ui-datepicker td.fully_booked:not(.not_bookable_by_rules) { opacity: 1; }
/*
 * Bookings paints every available day solid #1f874b (and #176d3b once the range
 * is hovered) with `!important`, on `.wc-bookings-date-picker .ui-datepicker
 * td.bookable a` (0,3,1). A plain `.pmg-shop ... td.bookable a` (0,2,1) lost
 * twice over -- on specificity and on !important -- which is why a whole month
 * of open days read as one green wall with nothing to distinguish the day you
 * had actually chosen. Available is the *normal* state here and gets the quiet
 * treatment; the solid green is spent on the one day that is selected.
 *
 * The selectors below go one level deeper than Bookings' and carry !important
 * only on the declarations Bookings forces. Anything it does not force
 * (border-radius, transitions) is left to the plain rules above.
 */
.pmg-shop .wc-bookings-date-picker .ui-datepicker .ui-datepicker-calendar td.bookable a,
.pmg-shop .wc-bookings-date-picker .ui-datepicker .ui-datepicker-calendar td.bookable-range a.ui-state-default {
	background-color: var(--soft) !important;
	color: var(--ink) !important;
	text-shadow: none !important;
	border-color: transparent !important;
}
.pmg-shop .wc-bookings-date-picker .ui-datepicker .ui-datepicker-calendar td.bookable a:hover {
	background-color: var(--green) !important;
	color: var(--on-green) !important;
}

/* Today is marked with a ring, so it stays legible whether or not it is chosen. */
.pmg-shop .ui-datepicker-calendar td.ui-datepicker-today a { box-shadow: inset 0 0 0 2px var(--green); }

/*
 * The chosen day.
 *
 * The class qualifier on the anchor is load-bearing. Once a day is picked
 * Bookings adds `.bookable-range` to its td, and the rule above that neutralises
 * Bookings' `td.bookable-range .ui-state-default` green is one class deeper than
 * a plain `td.ui-datepicker-current-day a` -- so the selected day kept the pale
 * available background and the only thing marking it was the underline Bookings
 * forces. Naming the anchor's class brings this back to the same weight, and it
 * is later in the file, so it wins.
 */
.pmg-shop .wc-bookings-date-picker .ui-datepicker .ui-datepicker-calendar td.ui-datepicker-current-day a.ui-state-default,
.pmg-shop .wc-bookings-date-picker .ui-datepicker .ui-datepicker-calendar td a.ui-state-active.ui-state-default,
.pmg-shop .ui-datepicker-calendar td.ui-datepicker-current-day a,
.pmg-shop .ui-datepicker-calendar td a.ui-state-active {
	background-color: var(--ink) !important;
	color: #EAFCE0 !important;
	text-shadow: none !important;
	text-decoration: none !important;
	box-shadow: none;
}

/*
 * The day tooltip. Bookings appends it to the body, not inside the calendar, so
 * it is not reachable from .pmg-shop and has to be styled unscoped -- but the
 * class is its own and appears on no other element, so nothing else is affected.
 * Left as Bookings' white box with a #767676 border it read as a browser alert
 * dropped on top of the grid.
 */
.wc-bookings-date-tooltip {
	background-color: #12351E;
	color: #EAFCE0;
	border: 0;
	border-radius: 10px;
	padding: 7px 12px;
	font-family: Inter, ui-sans-serif, system-ui, -apple-system, sans-serif;
	font-size: 12.5px;
	font-weight: 700;
	line-height: 1.35;
	box-shadow: 0 10px 26px rgba(6, 28, 12, .28);
	pointer-events: none;
}

/*
 * The GTranslate switcher floats bottom-left, outside .pmg-page, and on a phone
 * it lands directly on top of the booking total -- the white "ET" bar reads as
 * the price box being cut in half. Hidden on the skinned pages only (body
 * carries .pmg-shop), so the client's switcher still works everywhere else on
 * their site. Worth raising with them: the site is Estonian and the widget's
 * own styling matches nothing around it.
 */
body.pmg-shop .gtranslate_wrapper { display: none; }

/* ----------------------------------------------------------- time slots -- */

/*
 * `overflow: visible` is the fix for the top row of slots being sliced off on
 * hover. Bookings sets `overflow: hidden` on .block-picker -- a float clear it
 * no longer needs, since this is a grid -- and the hover state lifts a pill by
 * 2px and grows a 1.5px border. On every row but the first that overflow is
 * invisible; on the first it cut the top off the pill you were pointing at.
 * The small top padding keeps the lift clear of the label above it.
 */
.pmg-shop .block-picker,
.pmg-shop .wc-bookings-time-block-picker {
	list-style: none;
	margin: 6px 0 0;
	padding: 4px 0 0;
	display: grid;
	grid-template-columns: repeat(auto-fill, minmax(96px, 1fr));
	gap: 10px;
	overflow: visible;
}

.pmg-shop .block-picker li { margin: 0; padding: 0; list-style: none; width: auto; }

/*
 * Before a date is picked, Bookings puts a plain message ("Choose a date above
 * to see available times") inside .block-picker. As a grid child it was taking
 * one 96px slot-sized column and wrapping after two words. Anything that is not
 * a slot spans the full row instead.
 */
.pmg-shop .block-picker > :not(li) {
	grid-column: 1 / -1;
	color: var(--muted);
	font-size: 16px;
	padding: 4px 0;
}

/*
 * jQuery UI keeps a single shared popup container, #ui-datepicker-div, parked at
 * the end of <body> for input-attached pickers. Bookings uses the *inline*
 * picker (.ui-datepicker-inline), so this one is never opened -- but the
 * .ui-datepicker rules above were still painting it, leaving an empty white box
 * at the foot of the page.
 */
.pmg-shop #ui-datepicker-div { display: none !important; }

/*
 * Bookings styles the slots as `.wc-bookings-booking-form .block-picker li.block
 * a` (0,3,2), which beat a plain `.block-picker li a` (0,2,2) and left the pills
 * alternating #fff / #f5f5f5. This selector goes one deeper.
 */
.pmg-shop .wc-bookings-booking-form .block-picker li.block a,
.pmg-shop .block-picker li.block a,
.pmg-shop .block-picker li a {
	display: flex;
	align-items: center;
	justify-content: center;
	padding: 13px 6px;
	border-radius: 14px;
	background: var(--soft);
	border: 1.5px solid transparent;
	font-weight: 900;
	font-size: 15px;
	color: var(--ink);
	transition: background .18s ease, border-color .18s ease, color .18s ease, transform .18s ease;
}
.pmg-shop .wc-bookings-booking-form .block-picker li.block a:hover,
.pmg-shop .block-picker li a:hover {
	border-color: var(--green);
	background: var(--white);
	transform: translateY(-2px);
}
/*
 * Bookings forces the chosen slot to #239e57 with !important, so this needs it
 * too -- otherwise the selected hour came out a different green from the
 * selected day and neither matched the brand. Both are ink now, so "chosen"
 * looks the same whichever control you are looking at.
 */
.pmg-shop .wc-bookings-booking-form .block-picker li.block a.selected,
.pmg-shop .block-picker li a.selected,
.pmg-shop .block-picker li.selected a {
	background: var(--ink) !important;
	border-color: var(--ink);
	color: #EAFCE0 !important;
}
.pmg-shop .block-picker li a.unavailable,
.pmg-shop .block-picker li a.fully_booked {
	background: transparent;
	color: #C3CFC2;
	pointer-events: none;
	text-decoration: line-through;
}

/* ------------------------------------------------------------ cost + CTA -- */

.pmg-shop .wc-bookings-booking-cost {
	background: var(--soft);
	border: 0;
	border-radius: 18px;
	padding: 18px 22px;
	margin: 24px 0 0;
	font-size: 20px;
	font-weight: 950;
	color: var(--ink);
}

/*
 * WooCommerce styles its CTA as `.woocommerce button.button.alt` -- specificity
 * 0,3,1 -- which outranks a plain `.pmg-shop .button`. That is why the button
 * stayed WooCommerce purple. These selectors match or beat it, and because the
 * stylesheet is now enqueued last, ties resolve here.
 */
.pmg-shop button.button.alt,
.pmg-shop button.single_add_to_cart_button,
.pmg-shop .pmg-product button.button,
.pmg-shop .single_add_to_cart_button,
.pmg-shop .wc-bookings-booking-form-button,
.pmg-shop .button,
.pmg-shop button.button,
.pmg-shop a.button,
.pmg-shop .checkout-button,
.pmg-shop #place_order {
	display: inline-flex;
	align-items: center;
	justify-content: center;
	border: 0;
	border-radius: 999px;
	padding: 16px 30px;
	font: inherit;
	font-weight: 950;
	font-size: 16px;
	background: var(--green);
	color: var(--on-green);
	box-shadow: 0 10px 28px rgba(108, 194, 71, .24);
	cursor: pointer;
	transition: background .22s ease, transform .22s ease, box-shadow .22s ease;
	text-decoration: none;
	width: auto;
	float: none;
}
.pmg-shop button.button.alt:hover,
.pmg-shop button.single_add_to_cart_button:hover,
.pmg-shop .pmg-product button.button:hover,
.pmg-shop .single_add_to_cart_button:hover,
.pmg-shop .wc-bookings-booking-form-button:hover,
.pmg-shop .button:hover,
.pmg-shop button.button:hover,
.pmg-shop a.button:hover,
.pmg-shop .checkout-button:hover,
.pmg-shop #place_order:hover {
	background: #7BD453;
	transform: translateY(-2px);
	box-shadow: 0 14px 34px rgba(108, 194, 71, .32);
}
.pmg-shop .single_add_to_cart_button:active,
.pmg-shop #place_order:active { transform: translateY(0); }

/*
 * Bookings ships the CTA disabled until a date is chosen, and WooCommerce styles
 * that state as `.woocommerce button.button.alt.disabled` -- 0,4,1, which beats
 * a plain `.pmg-shop .single_add_to_cart_button.disabled` at 0,3,0. Matching its
 * shape is what finally stops the button rendering WooCommerce purple on page
 * load, which is the state a visitor sees first.
 */
.pmg-shop button.button.alt.disabled,
.pmg-shop button.button.alt:disabled,
.pmg-shop button.button.disabled,
.pmg-shop .single_add_to_cart_button.disabled,
.pmg-shop .single_add_to_cart_button:disabled {
	background: var(--line) !important;
	color: var(--muted) !important;
	box-shadow: none;
	cursor: not-allowed;
	transform: none;
	opacity: 1;
}
.pmg-shop button.button.alt.disabled:hover,
.pmg-shop button.button.alt:disabled:hover {
	background: var(--line) !important;
	transform: none;
	box-shadow: none;
}

/* The CTA is the end of the form, so it gets room rather than sitting small and
   left-aligned under the calendar. */
.pmg-shop .wc-bookings-booking-form-button {
	margin-top: 26px;
	min-width: 220px;
}

.pmg-shop #place_order { width: 100%; margin-top: 8px; }

/* -------------------------------------------------------------- notices -- */

.pmg-shop .woocommerce-message,
.pmg-shop .woocommerce-info,
.pmg-shop .woocommerce-error {
	border-radius: 18px;
	border: 1px solid var(--line);
	border-top: 0;
	background: var(--white);
	padding: 18px 22px;
	margin: 0 0 24px;
	font-weight: 700;
	color: var(--ink);
	box-shadow: 0 8px 24px rgba(31, 86, 37, .07);
	list-style: none;
	display: flex;
	flex-wrap: wrap;
	align-items: center;
	gap: 14px;
}
.pmg-shop .woocommerce-message::before,
.pmg-shop .woocommerce-info::before,
.pmg-shop .woocommerce-error::before { display: none; }
.pmg-shop .woocommerce-message { border-left: 5px solid var(--green); }
.pmg-shop .woocommerce-info { border-left: 5px solid var(--ink-2); }
.pmg-shop .woocommerce-error { border-left: 5px solid #C4564A; }
.pmg-shop .woocommerce-message .button { margin-left: auto; padding: 11px 22px; font-size: 14px; }

/* --------------------------------------------------- cart and checkout -- */

.pmg-shop .woocommerce-checkout h3,
.pmg-shop .woocommerce-cart h2,
.pmg-shop #order_review_heading {
	font-size: 26px;
	font-weight: 950;
	letter-spacing: -.02em;
	margin: 0 0 18px;
	color: var(--ink);
}

.pmg-shop .woocommerce-checkout .col2-set { display: grid; gap: 28px; }
.pmg-shop .woocommerce-checkout .col2-set .col-1,
.pmg-shop .woocommerce-checkout .col2-set .col-2 { width: 100%; float: none; }

.pmg-shop .woocommerce-billing-fields,
.pmg-shop .woocommerce-additional-fields,
.pmg-shop .woocommerce-checkout-review-order,
.pmg-shop .cart_totals,
.pmg-shop .woocommerce-order-details,
.pmg-shop .woocommerce-customer-details {
	background: var(--white);
	border: 1px solid var(--line);
	border-radius: var(--radius);
	box-shadow: var(--shadow);
	padding: 30px;
	margin: 0 0 26px;
}

.pmg-shop .form-row { padding: 0; margin: 0 0 18px; }
.pmg-shop .form-row label {
	display: block;
	font-weight: 900;
	font-size: 13px;
	letter-spacing: .07em;
	text-transform: uppercase;
	color: var(--muted);
	margin: 0 0 8px;
}
.pmg-shop .form-row .required { color: var(--green-dark); text-decoration: none; }

.pmg-shop .input-text,
.pmg-shop .form-row input[type="text"],
.pmg-shop .form-row input[type="email"],
.pmg-shop .form-row input[type="tel"],
.pmg-shop .form-row textarea,
.pmg-shop .form-row select,
.pmg-shop .select2-container .select2-selection--single {
	width: 100%;
	padding: 13px 16px;
	border: 1.5px solid var(--line);
	border-radius: 14px;
	background: var(--white);
	font: inherit;
	color: var(--ink);
	height: auto;
	transition: border-color .2s ease, box-shadow .2s ease;
}
.pmg-shop .input-text:focus,
.pmg-shop .form-row textarea:focus,
.pmg-shop .form-row select:focus {
	outline: none;
	border-color: var(--green);
	box-shadow: 0 0 0 4px rgba(108, 194, 71, .18);
}
.pmg-shop .form-row textarea { min-height: 110px; resize: vertical; }

.pmg-shop table.shop_table {
	width: 100%;
	border: 0;
	border-collapse: collapse;
	border-radius: 0;
	margin: 0;
}
.pmg-shop table.shop_table th,
.pmg-shop table.shop_table td {
	border: 0;
	border-bottom: 1px solid var(--line);
	padding: 14px 0;
	text-align: left;
	font-size: 16px;
}
.pmg-shop table.shop_table th { font-weight: 900; color: var(--muted); font-size: 13px; letter-spacing: .06em; text-transform: uppercase; }
.pmg-shop table.shop_table tfoot tr:last-child th,
.pmg-shop table.shop_table tfoot tr:last-child td {
	border-bottom: 0;
	font-size: 21px;
	font-weight: 950;
	color: var(--ink);
	padding-top: 18px;
}
.pmg-shop table.shop_table td:last-child,
.pmg-shop table.shop_table th:last-child { text-align: right; }

/* The booking's date/time summary inside the order lines. */
.pmg-shop .wc-booking-summary,
.pmg-shop .wc-booking-summary-list,
.pmg-shop dl.variation {
	margin: 6px 0 0;
	font-size: 14px;
	color: var(--muted);
	font-weight: 700;
}
.pmg-shop dl.variation dt, .pmg-shop dl.variation dd { display: inline; margin: 0; }
.pmg-shop dl.variation dd { margin-right: 10px; }

.pmg-shop #payment {
	background: var(--soft);
	border-radius: 20px;
	padding: 22px;
	margin-top: 22px;
}
.pmg-shop #payment ul.payment_methods {
	list-style: none;
	margin: 0 0 16px;
	padding: 0 0 16px;
	border-bottom: 1px solid var(--line);
}
.pmg-shop #payment ul.payment_methods li { margin: 0 0 8px; padding: 0; }
.pmg-shop #payment ul.payment_methods label { font-weight: 900; color: var(--ink); text-transform: none; letter-spacing: 0; font-size: 16px; }
.pmg-shop #payment .payment_box {
	background: var(--white);
	border-radius: 14px;
	padding: 14px 18px;
	margin: 10px 0 0;
	font-size: 15px;
	color: var(--muted);
}
.pmg-shop #payment .payment_box::before { display: none; }

/* -------------------------------------------- cart / checkout BLOCKS -- */

/*
 * This site's cart and checkout are the WooCommerce *block* checkout
 * (wp:woocommerce/checkout), not the classic shortcode, so the rules above --
 * #payment, .form-row, #place_order -- never match there. The block markup is
 * rendered client-side by React, so these class names come from WooCommerce
 * Blocks' own stable component API rather than from scraping the page.
 *
 * The classic rules are kept anyway: they still apply if the client ever swaps
 * the block back for the shortcode, which is a single click in the editor.
 */

.pmg-shop .wc-block-components-title,
.pmg-shop .wp-block-woocommerce-cart-order-summary-heading-block {
	font-weight: 950;
	letter-spacing: -.02em;
	color: var(--ink);
}

/*
 * ONE card again. The order summary is three nested elements --
 * .wc-block-components-sidebar > .wp-block-woocommerce-*-order-summary-block >
 * .wc-block-components-order-summary -- and styling more than one of them as a
 * card produced a rounded box inside a rounded box, with WooCommerce's own 5px
 * radius on the middle one showing through at the corners.
 *
 * The outer sidebar is the card; everything inside it is flattened.
 */
.pmg-shop .wc-block-components-sidebar {
	background: var(--white);
	border: 1px solid var(--line);
	border-radius: var(--radius);
	box-shadow: var(--shadow);
	padding: 26px;
}
.pmg-shop .wc-block-components-sidebar .wp-block-woocommerce-cart-order-summary-block,
.pmg-shop .wc-block-components-sidebar .wp-block-woocommerce-checkout-order-summary-block,
.pmg-shop .wc-block-components-sidebar .wc-block-components-order-summary,
.pmg-shop .wc-block-components-sidebar .wc-block-components-panel {
	background: none;
	border: 0;
	border-radius: 0;
	box-shadow: none;
	padding: 0;
}

/*
 * The bookable products have no featured image, so the order summary showed
 * WooCommerce's grey placeholder thumbnail -- a broken-picture icon sitting next
 * to the thing the customer just booked, which reads as an error. Only the
 * placeholder is hidden, matched on its filename: give a product a real photo
 * and the thumbnail appears on its own. The quantity badge lives in the same
 * container, so the container itself has to stay.
 */
.pmg-shop .wc-block-components-order-summary-item__image img[src*="woocommerce-placeholder"] {
	display: none;
}

/*
 * The quantity badge. It is position:absolute over the (hidden) thumbnail, and
 * WooCommerce sizes it with min-width alone -- fine for "10", but at "1" the
 * text node and its line-height decide the height, so the circle came out a
 * couple of pixels wide and read as an oval. Pinning both axes and centring the
 * digit with flex keeps it round at any count; the radius stays larger than the
 * box so it cannot go square if a third digit ever widens it.
 */
.pmg-shop .wc-block-components-order-summary-item__quantity {
	width: 24px;
	height: 24px;
	min-width: 24px;
	min-height: 24px;
	padding: 0;
	border-radius: 999px;
	display: flex;
	align-items: center;
	justify-content: center;
	line-height: 1;
	font-size: 12px;
	font-weight: 900;
}

/*
 * Trim the order summary down to what a customer checks before paying: what
 * they booked, when, and what it costs.
 *
 * Cut: the product's full marketing description (they read it on the product
 * page one click ago), and the per-unit price, which for a single booking is
 * the same number already shown on the right of the same line.
 *
 * Kept and promoted: the booking date and start time. That is the one detail
 * worth re-checking here and the only thing distinguishing two lines of the
 * same product -- so it reads as the date, not as a labelled field. The
 * "Broneeringu kuupäev:" label goes: nothing else on the line is a date, and
 * the label was longer than the value it introduced.
 */
.pmg-shop .wc-block-components-product-metadata__description,
.pmg-shop .wc-block-components-order-summary-item__individual-prices {
	display: none;
}
.pmg-shop .wc-block-components-product-details {
	margin: 4px 0 0;
	font-size: 14px;
	color: var(--ink);
	line-height: 1.4;
}
.pmg-shop .wc-block-components-product-details__name { display: none; }
/*
 * pre-line, because the booking summary is one entry carrying a newline: the
 * checkout joins separate entries with slashes, so the only way to put the
 * duration on its own line is to keep it inside one value. See
 * pmg_pages_booking_item_meta().
 */
.pmg-shop .wc-block-components-product-details__value { font-weight: 800; white-space: pre-line; }

/*
 * "Muuda" sends the customer back to the picker with their choice restored --
 * ticket counts cannot be edited on this page. Quiet, because it sits under
 * the booking they are here to confirm, not next to the buy button.
 */
.pmg-shop .pmg-item-edit {
	display: inline-block;
	margin-top: 4px;
	font-weight: 600;
	color: var(--pmg-green, #4B8E2B);
	text-decoration: underline;
	text-underline-offset: 2px;
}
.pmg-shop .pmg-item-edit:hover { color: var(--pmg-ink, #16281A); }

/*
 * The summary line was the smallest type on a page whose whole job is "is this
 * the right booking?". It is now the size of the thing it describes, and the
 * activity's own icon -- the same file the picker tiles use -- sits where the
 * (absent) product photo would, so two lines of different products are told
 * apart at a glance rather than by reading.
 *
 * The icon is a background on the image container, which stays in the DOM for
 * the quantity badge; shop.js tags the row with data-pmg-icon from the product
 * name, so a product without a match simply gets no icon.
 */
/*
 * One type scale for the whole summary. It had four weights in eight lines --
 * 950 on the heading, 900 on names and prices, 800 on the date, WooCommerce's
 * own 400 on the totals labels -- so nothing looked deliberate and every line
 * competed with the one above it. Two weights now, 900 for the two headings
 * that bracket the list and 800 for everything in it, and the sizes step
 * 18 / 16 / 14 instead of jumping 23 to 13.
 */
.pmg-shop .wc-block-components-sidebar .wc-block-components-title,
.pmg-shop .wp-block-woocommerce-cart-order-summary-heading-block {
	font-size: 18px;
	font-weight: 900;
	letter-spacing: -.01em;
	margin: 0 0 18px;
}
.pmg-shop .wc-block-components-order-summary-item {
	padding: 16px 0;
	font-size: 16px;
}
.pmg-shop .wc-block-components-order-summary-item__description .wc-block-components-product-name,
.pmg-shop .wc-block-components-order-summary-item__description .wc-block-components-product-name a {
	font-size: 16px;
	font-weight: 800;
	line-height: 1.3;
}
.pmg-shop .wc-block-components-order-summary-item__total-price {
	font-size: 16px;
	font-weight: 800;
	color: var(--ink);
}
.pmg-shop [data-pmg-icon] .wc-block-components-order-summary-item__image {
	width: 56px;
	min-width: 56px;
	height: 56px;
	border-radius: 16px;
	background: var(--green-soft) center / 30px 30px no-repeat;
	position: relative;
}
/* Toit and pidu have no SVG in the set; drawn as glyphs, like minigolf. */
.pmg-shop [data-pmg-icon="toit"] .wc-block-components-order-summary-item__image:before,
.pmg-shop [data-pmg-icon="pidu"] .wc-block-components-order-summary-item__image:before {
	position: absolute;
	inset: 0;
	display: flex;
	align-items: center;
	justify-content: center;
	font-size: 24px;
	line-height: 1;
}
.pmg-shop [data-pmg-icon="toit"] .wc-block-components-order-summary-item__image:before { content: "\1F37D"; }
.pmg-shop [data-pmg-icon="pidu"] .wc-block-components-order-summary-item__image:before { content: "\1F389"; }

/*
 * The product photo. One row had a real image and four had none, so the list
 * stepped in and out along its left edge. Every row gets the same tile now --
 * the icon above -- and the photo is dropped rather than shown on one line in
 * five.
 */
.pmg-shop [data-pmg-icon] .wc-block-components-order-summary-item__image img {
	display: none;
}

.pmg-shop [data-pmg-icon="darts"] .wc-block-components-order-summary-item__image {
	background-image: url(../img/icons/dartboard.svg);
}
.pmg-shop [data-pmg-icon="piljard"] .wc-block-components-order-summary-item__image {
	background-image: url(../img/icons/ball-8.svg);
}
/* Minigolf has no SVG in the set -- the picker draws it as an emoji, so this
   one is drawn the same way rather than inventing a second visual language. */
.pmg-shop [data-pmg-icon="minigolf"] .wc-block-components-order-summary-item__image:before {
	content: "\26F3";
	/* Taken out of flow deliberately. As a flex item of the tile its height came
	   from the flex algorithm, not from the tile: measured 28px on one row and
	   44px on the next in the same list. inset:0 makes the glyph's box the tile. */
	position: absolute;
	inset: 0;
	display: flex;
	align-items: center;
	justify-content: center;
	font-size: 26px;
	line-height: 1;
}

/*
 * "Vahesumma" restates the total: there is no shipping on a booking, prices
 * include VAT, and the only other row is "Kokku" with the same figure. Coupon
 * and fee rows are separate blocks and are untouched, so a discount would still
 * show -- and would bring its own before/after arithmetic with it.
 */
.pmg-shop .wp-block-woocommerce-checkout-order-summary-subtotal-block,
.pmg-shop .wp-block-woocommerce-cart-order-summary-subtotal-block {
	display: none;
}
/*
 * With it gone the block that held it collapses to its own rule and padding,
 * leaving two hairlines with an empty band between them above "Kokku". The
 * footer wrapper draws its own border, so this one is redundant either way.
 */
.pmg-shop .wp-block-woocommerce-checkout-order-summary-totals-block,
.pmg-shop .wp-block-woocommerce-cart-order-summary-totals-block {
	border-top: 0;
	padding-bottom: 0;
}

/*
 * Käibemaks belongs under the figure it is contained in, not above it: the
 * price includes VAT, so as a row before "Kokku" it read as something being
 * added on.
 *
 * WooCommerce renders it inside the totals block while "Kokku" sits in its own
 * wrapper, so the two are not siblings and `order` alone could not reach across
 * them. `display: contents` dissolves the totals block, which puts every row and
 * the footer in one flex column -- then the tax row is simply ordered last.
 */
.pmg-shop .wc-block-components-sidebar .wp-block-woocommerce-checkout-order-summary-block,
.pmg-shop .wc-block-components-sidebar .wp-block-woocommerce-cart-order-summary-block {
	display: flex;
	flex-direction: column;
}
.pmg-shop .wp-block-woocommerce-checkout-order-summary-totals-block,
.pmg-shop .wp-block-woocommerce-cart-order-summary-totals-block {
	display: contents;
}
.pmg-shop .wp-block-woocommerce-checkout-order-summary-taxes-block,
.pmg-shop .wp-block-woocommerce-cart-order-summary-taxes-block {
	order: 9;
}
/* Under the total it is a footnote to it, not a row of its own: no rule above,
   no bold, and the muted grey the rest of the small print uses. */
.pmg-shop .wp-block-woocommerce-checkout-order-summary-taxes-block .wc-block-components-totals-item,
.pmg-shop .wp-block-woocommerce-cart-order-summary-taxes-block .wc-block-components-totals-item {
	padding: 8px 0 0;
	border-bottom: 0;
	font-size: 14px;
	font-weight: 700;
	color: var(--muted);
}
.pmg-shop .wp-block-woocommerce-checkout-order-summary-taxes-block .wc-block-components-totals-wrapper,
.pmg-shop .wp-block-woocommerce-cart-order-summary-taxes-block .wc-block-components-totals-wrapper {
	border-top: 0;
	padding: 0;
}
/* "Sisaldab X € KM" is a footnote to the figure, so it sits under the figure.
   WooCommerce puts it in the totals-footer-item's description cell, which runs
   the full width left-aligned -- under the word "Kokku" rather than under the
   amount. WooCommerce renders it as a flex row, so justify-content is what
   moves it -- text-align does nothing to a flex line. */
.pmg-shop .wc-block-components-totals-footer-item-tax {
	justify-content: flex-end;
	text-align: right;
}

/*
 * The empty-cart state never gets read: shop.js redirects to the picker the
 * moment the last booking goes, and until that fires this is a cart glyph, a
 * paragraph about a shop that is not part of this design, and an unstyled black
 * "Sirvi poodi" pill. Hiding it means the page is blank for the frame or two
 * before the redirect instead of flashing something wrong.
 */
.pmg-shop .wc-block-checkout-empty,
.pmg-shop .wc-block-cart__empty-cart__title,
.pmg-shop .wp-block-woocommerce-empty-cart-block,
.pmg-shop .cart-empty,
.pmg-shop .return-to-shop {
	display: none;
}

/* -------------------------------------------------------- checkout form -- */

/*
 * The order summary was a card and the form beside it was not, so the fields
 * floated loose on the cream with nothing holding them. One card around the
 * whole left column, with the checkout's own steps as divided sections inside
 * it -- the same shape as the summary opposite.
 */
.pmg-shop .wc-block-checkout__main {
	background: var(--white);
	border: 1px solid var(--line);
	border-radius: var(--radius);
	box-shadow: var(--shadow);
	padding: 34px 32px;
}
/*
 * The gutter towards the sidebar is WooCommerce's
 * `.wc-block-components-sidebar-layout .wc-block-components-main { padding-right: 4.5283% }`
 * -- a percentage, so it grew with the viewport and the card sat visibly
 * narrower on the right than the left. Same specificity as the rule above, so
 * it took a third class to beat rather than another padding declaration. The
 * gap between card and summary is the grid's, not padding inside the card.
 */
.pmg-shop .wc-block-components-sidebar-layout .wc-block-checkout__main {
	padding-inline: 32px;
}
/* No rules between the sections: the headings already separate them, and a
   hairline every 26px turned one card into a stack of receipts. Space alone
   does the dividing. */
.pmg-shop .wc-block-checkout__main .wc-block-components-checkout-step {
	padding: 0 0 30px;
	margin: 0 0 30px;
	border-bottom: 0;
}
.pmg-shop .wc-block-checkout__main .wc-block-checkout__order-notes {
	padding-bottom: 0;
	margin-bottom: 24px;
	border-bottom: 0;
}
/*
 * The terms line and the note field are different in kind -- one is a field you
 * fill in, the other is the legal text you are agreeing to -- and a hairline
 * between them said only "these are two rows". It reads as its own quiet panel
 * instead: the page's cream on the white card, which separates far better than
 * a rule and needs no rule of its own.
 */
.pmg-shop .wc-block-checkout__main .wc-block-checkout__terms {
	margin: 0 0 22px;
	padding: 16px 18px;
	background: var(--cream);
	border-radius: 16px;
	border-top: 0;
	font-size: 14px;
	line-height: 1.5;
	color: var(--muted);
}
.pmg-shop .wc-block-checkout__main .wc-block-checkout__terms a { color: var(--ink); font-weight: 800; }
/* The submit block carries a 36px bottom margin, which inside a card is just a
   hole under the button. */
.pmg-shop .wc-block-checkout__main .wc-block-checkout__actions { margin-bottom: 0; }
.pmg-shop .wc-block-components-checkout-step__title,
.pmg-shop .wc-block-checkout__main .wc-block-components-title {
	font-size: 23px;
	font-weight: 950;
	letter-spacing: -.02em;
	color: var(--ink);
	margin: 0 0 16px;
}
/*
 * "Hetkel sooritad ostu külalisena." -- WooCommerce's guest-checkout notice.
 * There is no account step in this flow and no login link beside it, so it
 * announces a choice the customer was never offered. Out, along with the rest
 * of the step descriptions, which restate their own heading.
 */
.pmg-shop .wc-block-components-checkout-step__description,
.pmg-shop .wc-block-checkout__guest-checkout-notice { display: none; }

/*
 * Field spacing. WooCommerce sets a 1.5em row gap on the address grid and
 * another 16px margin under each input, so two consecutive fields sat ~40px
 * apart and one section of six fields ran longer than the whole summary beside
 * it. One gap, once.
 */
.pmg-shop .wc-block-checkout__main .wc-block-components-address-form,
.pmg-shop .wc-block-checkout__main .wc-block-components-address-address-wrapper {
	gap: 14px;
}
.pmg-shop .wc-block-checkout__main .wc-block-components-text-input,
.pmg-shop .wc-block-checkout__main .wc-block-components-country-input,
.pmg-shop .wc-block-checkout__main .wc-block-components-state-input,
.pmg-shop .wc-block-checkout__main .wc-block-components-combobox {
	margin-top: 0;
	margin-bottom: 0;
}
.pmg-shop .wc-block-checkout__main .wc-block-components-checkout-step__content > .wc-block-components-text-input + .wc-block-components-text-input {
	margin-top: 14px;
}

/*
 * White fields on a white card are invisible until you find the border, so
 * inside the card they get the page's own cream. They go back to white on
 * focus, which reads as the field waking up.
 */
.pmg-shop .wc-block-checkout__main .wc-block-components-text-input input,
.pmg-shop .wc-block-checkout__main .wc-block-components-textarea,
.pmg-shop .wc-block-checkout__main .wc-block-components-select__select,
.pmg-shop .wc-block-checkout__main .wc-block-components-combobox-control input {
	background: var(--cream);
}
.pmg-shop .wc-block-checkout__main .wc-block-components-text-input input:focus,
.pmg-shop .wc-block-checkout__main .wc-block-components-textarea:focus {
	background: var(--white);
}

/* Same reason: the payment card sits inside the big one, so it drops to cream
   and only the selected one fills in. */
.pmg-shop .wc-block-checkout__main .wc-block-components-radio-control-accordion-option {
	background: var(--cream);
}
.pmg-shop .wc-block-checkout__main .wc-block-components-radio-control-accordion-option:has(input:checked),
.pmg-shop .wc-block-checkout__main .wc-block-components-radio-control-accordion-option--checked-option-highlighted {
	background: var(--soft);
}

/* The summary follows you down a long form rather than scrolling away. */
@media (min-width: 1000px) {
	.pmg-shop .wc-block-components-sidebar {
		position: sticky;
		top: 24px;
	}
}

/*
 * Mobile: one order summary, not two.
 *
 * Below its own breakpoint WooCommerce renders the summary twice -- the sidebar
 * collapses to an accordion bar above the form, and a second copy is filled in
 * above "Esita tellimus" (.checkout-order-summary-block-fill-wrapper). The
 * second one is the better of the two: it is open, it is complete, and it sits
 * where you actually check the order before paying.
 *
 * The sidebar is hidden only when that copy is present, so if WooCommerce ever
 * stops filling it the summary does not vanish with it.
 */
@media (max-width: 700px) {
	.pmg-shop .wc-block-checkout:has(.checkout-order-summary-block-fill-wrapper) .wc-block-checkout__sidebar {
		display: none;
	}
	/* It is inside the form's card already -- a second bordered box around it
	   is a card in a card. */
	.pmg-shop .checkout-order-summary-block-fill-wrapper {
		background: none;
		border: 0;
		box-shadow: none;
		padding: 0;
		/* The submit button needs room of its own -- it is the last thing on the
		   page and should not look attached to the summary above it. */
		margin-bottom: 32px;
	}
	.pmg-shop .checkout-order-summary-block-fill-wrapper .wc-block-components-checkout-step__title {
		font-size: 18px;
	}
	/* Both on the three-class selector: at this width WooCommerce zeroes the
	   main column's padding through .wc-block-components-sidebar-layout
	   .wc-block-components-main, which ties with a two-class rule of ours and
	   wins on order -- measured 0px top and bottom, which is why the button sat
	   on the card's edge. */
	.pmg-shop .wc-block-components-sidebar-layout .wc-block-checkout__main {
		padding: 40px 18px 34px;
	}

	/* 90px of cream under the card is most of a thumb-scroll on a phone. */
	.pmg-shop .pmg-shop-main {
		padding: 26px 0 40px;
	}

	/*
	 * The sections were 30px apart, which on a 390px screen reads as two
	 * separate forms rather than one. Closer, but still further apart than the
	 * fields inside them.
	 */
	.pmg-shop .wc-block-checkout__main .wc-block-components-checkout-step {
		padding-bottom: 22px;
		margin-bottom: 22px;
	}
	.pmg-shop .wc-block-components-checkout-step__title,
	.pmg-shop .wc-block-checkout__main .wc-block-components-title {
		font-size: 21px;
		margin-bottom: 12px;
	}

	/*
	 * "Minigolf" was breaking as "Minigo / lf" and the date as "13.08.20 / 26".
	 * WooCommerce sets word-break on the summary rows, which splits inside a
	 * word once the column is narrow enough -- and the column is narrow because
	 * a 56px icon and the price are taking their share. Normal wrapping back on,
	 * plus a smaller icon to give the text the width it needed.
	 */
	.pmg-shop .wc-block-components-order-summary-item,
	.pmg-shop .wc-block-components-order-summary-item__description,
	.pmg-shop .wc-block-components-order-summary-item .wc-block-components-product-name,
	.pmg-shop .wc-block-components-order-summary-item .wc-block-components-product-details,
	.pmg-shop .wc-block-components-order-summary-item .wc-block-components-product-details__value {
		word-break: normal;
		overflow-wrap: normal;
		hyphens: none;
	}
	/* The date is one token to a reader; it should never break at all -- but the
	   value carries its own newline before the duration, so nowrap would put
	   both halves back on one line. pre-line keeps the break and still does not
	   wrap inside the date. */
	.pmg-shop .wc-block-components-order-summary-item .wc-block-components-product-details__value {
		white-space: pre-line;
	}
	.pmg-shop [data-pmg-icon] .wc-block-components-order-summary-item__image {
		width: 44px;
		min-width: 44px;
		height: 44px;
		border-radius: 12px;
		background-size: 24px 24px;
	}
	.pmg-shop .wc-block-components-order-summary-item__total-price {
		white-space: nowrap;
		padding-left: 10px;
	}
}

.pmg-shop .wc-block-checkout__terms {
	font-size: 14px;
	color: var(--muted);
	margin: 4px 0 18px;
}
.pmg-shop .wc-block-checkout__terms a { color: var(--green-dark); font-weight: 800; }

/*
 * The step rail shop.js puts above the checkout. Same shape as the picker's on
 * the Broneeri page, restated here because that one lives in a page stylesheet
 * the shop pages do not load.
 */
.pmg-shop .pmg-rail {
	display: flex;
	align-items: center;
	justify-content: center;
	max-width: 480px;
	margin: 0 auto 40px;
}
.pmg-shop .pmg-rail-step {
	display: flex;
	align-items: center;
	justify-content: center;
	width: 46px;
	height: 46px;
	flex: 0 0 auto;
	border-radius: 999px;
	border: 2px solid var(--line);
	background: var(--white);
	color: var(--muted);
	font-weight: 950;
	font-size: 17px;
}
.pmg-shop .pmg-rail-step.is-current {
	border-color: var(--green);
	background: var(--green);
	color: var(--white);
	box-shadow: 0 8px 22px rgba(108, 194, 71, .32);
}
.pmg-shop .pmg-rail-step.is-done { border-color: var(--green); color: var(--green-dark); }
.pmg-shop .pmg-rail-line { height: 2px; flex: 1 1 auto; background: var(--line); min-width: 20px; }
@media (max-width: 680px) {
	.pmg-shop .pmg-rail-step { width: 38px; height: 38px; font-size: 15px; }
}

/*
 * The remove control shop.js adds to each order-summary line. The Blocks
 * checkout summary is read-only and "Broneeri" skips the cart page entirely, so
 * without this there is no way to drop a booking once it is in.
 *
 * Deliberately quiet: this sits beside the thing the customer has just decided
 * to buy, so it reads as a small text link rather than a button competing with
 * "Esita tellimus". It only turns red on hover, once they mean it.
 */
.pmg-shop .pmg-remove-item {
	display: inline-block;
	margin-top: 4px;
	padding: 0;
	border: 0;
	background: none;
	color: var(--muted);
	font-family: inherit;
	/*
	 * A party order runs to five lines and every one of them carried this, at
	 * near the size of the product name -- the loudest thing in a summary whose
	 * job is to be read, not clicked. Footnote size, and it still turns red on
	 * hover once they mean it.
	 */
	font-size: 11px;
	font-weight: 600;
	text-decoration: underline;
	text-underline-offset: 2px;
	cursor: pointer;
	transition: color .18s ease;
}
.pmg-shop .pmg-remove-item:hover { color: #A8564A; }
.pmg-shop .pmg-remove-item:disabled { opacity: .5; cursor: default; text-decoration: none; }

/*
 * "Ettevõtte nimi" on a booking checkout. Six attempts at removing it through
 * WooCommerce settings and Blocks filters all failed -- the Blocks address form
 * builds its field list client-side -- so it goes out visually. The field stays
 * in the DOM and stays optional, which is what every one of those attempts was
 * trying to achieve anyway.
 */
.pmg-shop .wc-block-components-address-form__company,
.pmg-shop #billing-company,
.pmg-shop #shipping-company,
.pmg-shop .wc-block-components-text-input:has(#billing-company),
.pmg-shop .wc-block-components-text-input:has(#shipping-company) {
	display: none !important;
}

.pmg-shop .wc-block-components-text-input input,
.pmg-shop .wc-block-components-textarea,
.pmg-shop .wc-block-components-select__select,
.pmg-shop .wc-block-components-combobox-control input {
	border: 1.5px solid var(--line) !important;
	border-radius: 14px !important;
	background: var(--white);
	padding: 13px 16px;
	font: inherit;
	color: var(--ink);
}
.pmg-shop .wc-block-components-text-input.is-active input:focus,
.pmg-shop .wc-block-components-text-input input:focus,
.pmg-shop .wc-block-components-textarea:focus {
	outline: none;
	border-color: var(--green) !important;
	box-shadow: 0 0 0 4px rgba(108, 194, 71, .18);
}
.pmg-shop .wc-block-components-text-input label { color: var(--muted); }

.pmg-shop .wc-block-components-button,
.pmg-shop .wc-block-cart__submit-button,
.pmg-shop .wc-block-components-checkout-place-order-button {
	border-radius: 999px !important;
	background: var(--green) !important;
	color: var(--on-green) !important;
	font-weight: 950;
	padding: 16px 30px;
	border: 0 !important;
	box-shadow: 0 10px 28px rgba(108, 194, 71, .24);
	transition: background .22s ease, transform .22s ease, box-shadow .22s ease;
}
.pmg-shop .wc-block-components-button:hover,
.pmg-shop .wc-block-cart__submit-button:hover,
.pmg-shop .wc-block-components-checkout-place-order-button:hover {
	background: #7BD453 !important;
	transform: translateY(-2px);
	box-shadow: 0 14px 34px rgba(108, 194, 71, .32);
}

/* The "return to shop" / link-style buttons must not become green pills. */
.pmg-shop .wc-block-components-button.is-link,
.pmg-shop a.wc-block-components-button.is-link {
	background: none !important;
	color: var(--muted) !important;
	box-shadow: none;
	padding: 0;
	text-decoration: underline;
}

.pmg-shop .wc-block-components-totals-item {
	padding: 12px 0;
	font-size: 15px;
	font-weight: 800;
	border-bottom: 1px solid var(--line);
}
.pmg-shop .wc-block-components-totals-footer-item {
	border-bottom: 0;
	font-size: 20px;
	font-weight: 900;
	color: var(--ink);
}
.pmg-shop .wc-block-components-totals-footer-item .wc-block-components-totals-item__label,
.pmg-shop .wc-block-components-totals-footer-item .wc-block-components-totals-item__value {
	font-weight: 900;
}

.pmg-shop .wc-block-cart-items__row { border-bottom: 1px solid var(--line); }
.pmg-shop .wc-block-components-product-name {
	font-weight: 900;
	color: var(--ink);
	text-decoration: none;
}

/*
 * Payment options.
 *
 * A payment method is TWO elements: an outer
 * .wc-block-components-radio-control-accordion-option, which WooCommerce already
 * draws as a bordered card, wrapping a label (.__option) and a description panel
 * (.__accordion-content) that sits outside the label. Styling the label as the
 * card put a second rounded box inside the first, and since the label fills the
 * wrapper's content box it painted straight over the outer border -- which is
 * the overlap: "Maksmine kohapeal" in its own box, crossing the black outline,
 * with the description stranded outside on the cream.
 *
 * So the wrapper is the card and everything inside it is flat. The radio input
 * is position:absolute; left:16px, so the label's left padding is what keeps the
 * text clear of the dot -- a symmetric `padding: 14px 16px` drops the dot on top
 * of the first letters. The description is indented to the same 48px so it lines
 * up under the label rather than under the control.
 */
.pmg-shop .wc-block-components-radio-control-accordion-option {
	border: 1.5px solid var(--line);
	border-radius: 14px;
	background: var(--white);
	margin-bottom: 8px;
	overflow: hidden;
}
.pmg-shop .wc-block-components-radio-control-accordion-option:has(input:checked),
.pmg-shop .wc-block-components-radio-control-accordion-option--checked-option-highlighted {
	border-color: var(--green);
	background: var(--soft);
}
.pmg-shop .wc-block-components-radio-control__option {
	padding: 14px 16px 14px 48px;
	margin-bottom: 0;
}
/* A radio group with no accordion wrapper -- shipping, say -- is its own card. */
.pmg-shop .wc-block-components-radio-control__option:not(.wc-block-components-radio-control-accordion-option *) {
	border: 1.5px solid var(--line);
	border-radius: 14px;
	background: var(--white);
	margin-bottom: 8px;
}
.pmg-shop .wc-block-components-radio-control__option:not(.wc-block-components-radio-control-accordion-option *):has(input:checked) {
	border-color: var(--green);
	background: var(--soft);
}
/* Inside a card the label draws nothing of its own. */
.pmg-shop .wc-block-components-radio-control-accordion-option .wc-block-components-radio-control__option,
.pmg-shop .wc-block-components-radio-control-accordion-option .wc-block-components-radio-control__option-checked {
	border: 0;
	border-radius: 0;
	background: none;
}
.pmg-shop .wc-block-components-radio-control__option .wc-block-components-radio-control__description,
.pmg-shop .wc-block-components-radio-control__option .wc-block-components-radio-control__label {
	margin-left: 0;
}
.pmg-shop .wc-block-components-radio-control-accordion-content {
	margin: 0;
	padding: 0 16px 14px 48px;
	font-size: 14px;
	color: var(--muted);
}
.pmg-shop .wc-block-components-radio-control-accordion-content > div { margin: 0; }

/*
 * WooCommerce draws the option's own frame twice over, and both survived the
 * rules above because they are more specific than a plain class:
 *
 *   .wc-block-components-radio-control--highlight-checked .…--checked-option-highlighted
 *       { border-radius: 4px; box-shadow: inset 0 0 0 1.5px currentColor }
 *
 * -- that inset shadow is the black ring sitting inside our green border, and
 * its 4px radius is why the corners did not match -- and a `:after` pseudo that
 * paints a 1px frame on the last option plus a hairline divider between
 * adjacent ones. Dividers are for a flat list; these are separate cards with a
 * gap, so the frame is ours and the pseudo goes.
 */
.pmg-shop .wc-block-components-radio-control--highlight-checked .wc-block-components-radio-control-accordion-option--checked-option-highlighted,
.pmg-shop .wc-block-components-radio-control--highlight-checked label.wc-block-components-radio-control__option--checked-option-highlighted {
	border-radius: 14px;
	box-shadow: none;
}
.pmg-shop .wc-block-checkout__payment-method .wc-block-components-radio-control-accordion-option:after,
.pmg-shop .wc-block-checkout__payment-method .wc-block-components-radio-control__option:after,
.pmg-shop .wc-block-components-radio-control--highlight-checked div.wc-block-components-radio-control-accordion-option:after {
	display: none;
}

.pmg-shop .wc-block-components-notice-banner {
	border-radius: 18px;
	border-width: 1px;
	font-weight: 700;
}

/* Cross-sells and "new products" grids are shop furniture the design has no
   place for in a booking flow. */
.pmg-shop .wp-block-woocommerce-cart-cross-sells-block,
.pmg-shop .wc-block-product-new,
.pmg-shop .wc-block-grid { display: none !important; }

/* --------------------------------------------------------- order received -- */

.pmg-shop .woocommerce-order .woocommerce-thankyou-order-received {
	font-size: clamp(30px, 3.4vw, 44px);
	font-weight: 950;
	letter-spacing: -.03em;
	line-height: 1.05;
	color: var(--ink);
	margin: 0 0 24px;
}
/*
 * The confirmation opened on "Aitäh!" and then restated the order number, date,
 * total and payment method in a card -- all four of which appear again in
 * "Tellimuse andmed" directly below. The paragraph after it is the
 * cash-on-delivery instruction, which repeats the payment row in that table.
 *
 * The order number goes with the card, deliberately: it sat beside
 * "Broneering #1550" and the two are never the same number. WooCommerce
 * Bookings saves the booking as its own post immediately before the order, so
 * it takes the preceding ID. What the customer needs at the desk is the
 * booking, and that is now the only reference on the page.
 *
 * ul.* and the adjacent p, not a plainer selector: the card had its own
 * three-rule treatment here and a two-class hide rule lost to it.
 */
.pmg-shop ul.woocommerce-order-overview,
.pmg-shop ul.woocommerce-order-overview + p {
	display: none;
}

/*
 * The booking summary that Bookings prints inside the order table, on the
 * confirmation page. Three things were wrong with it.
 *
 * The product name rendered as a default browser-blue underlined link -- the
 * design's global a{color:inherit} does not reach here, because this markup is
 * WooCommerce's and sits outside .pmg-page.
 */
.pmg-shop .woocommerce-table--order-details a,
.pmg-shop .woocommerce-order-details a {
	color: var(--green-dark);
	font-weight: 800;
	text-decoration: none;
}
.pmg-shop .woocommerce-table--order-details a:hover { text-decoration: underline; }
/*
 * "Vahesumma" is the line-item total before shipping, tax and discounts. There
 * is no shipping on a booking, prices include VAT, and there is one item -- so
 * it restates "Kokku" every time. Same call as the checkout summary, where the
 * subtotal block is hidden for the same reason. A coupon would still print its
 * own row; it just would not have a "before" figure above it.
 * WooCommerce prints these footer rows with no classes at all, so this goes by
 * position. Subtotal is always the first row it outputs. */
.pmg-shop .woocommerce-table--order-details tfoot tr:first-child { display: none; }
/* "Piljard" and "× 1" are the same fact, so they sit on one line rather than
   the name floating alone above the booking. */
.pmg-shop .woocommerce-table__product-name {
	line-height: var(--lh-heading);
}
.pmg-shop .woocommerce-table__product-name .product-quantity {
	font-weight: 700;
	color: var(--muted);
}

/*
 * The booking read as a separate green box tacked under the product name -- so
 * one line item looked like two things, and the date, which is what the
 * customer is actually checking, sat below a reference number they will never
 * quote. No box: the product, the date and the reference are one block, ordered
 * by what matters. The inline margin-top:1em Bookings prints on the element
 * needs !important to beat.
 */
.pmg-shop .wc-booking-summary {
	display: flex;
	flex-direction: column;
	gap: 2px;
	background: none;
	border: 0;
	border-radius: 0;
	padding: 0;
	margin-top: 6px !important;
}
/* The date first, at reading size; the reference under it, quietly. */
.pmg-shop .wc-booking-summary-list { order: 1; margin: 0; padding: 0; list-style: none; }
.pmg-shop .wc-booking-summary-list li { margin: 0; font-size: var(--fs-body); font-weight: 800; color: var(--ink); }
.pmg-shop .wc-booking-summary-number { order: 2; font-size: 13px; font-weight: 700; color: var(--muted); }

/*
 * And the "Maksmata" chip. These bookings are deliberately paid at the venue,
 * so every one of them is unpaid by design -- telling the customer so on the
 * confirmation screen reads as a warning that something went wrong with their
 * booking. The page already states "Maksmine kohapeal" under Makseviis, and the
 * COD instructions above it say to show the confirmation at the desk, so
 * nothing is lost by dropping the chip. Scoped to .pmg-shop, so the status
 * stays visible in wp-admin where staff actually need it.
 */
.pmg-shop .wc-booking-summary-number .status-unpaid { display: none; }

/* ------------------------------------------------------------ responsive -- */

@media (max-width: 780px) {
	.pmg-shop .pmg-shop-main { padding: 34px 0 64px; }
	.pmg-shop .wc-bookings-booking-form,
	.pmg-shop form.cart,
	.pmg-shop .woocommerce-billing-fields,
	.pmg-shop .woocommerce-checkout-review-order,
	.pmg-shop .cart_totals,
	.pmg-shop .woocommerce-order-details,
	.pmg-shop .woocommerce-customer-details { padding: 22px; border-radius: 22px; }
	.pmg-shop .block-picker,
	.pmg-shop .wc-bookings-time-block-picker { grid-template-columns: repeat(auto-fill, minmax(84px, 1fr)); }
	.pmg-shop .single_add_to_cart_button,
	.pmg-shop .wc-bookings-booking-form-button { width: 100%; }
}

@media (prefers-reduced-motion: reduce) {
	.pmg-shop * { transition: none !important; }
}