/**
 * Sitewide premium visual language for standard Gutenberg-block page
 * content (WEBSITE-TRANCHE-004, activation prompt Section 8).
 *
 * Rather than hand-build a custom PHP template for every remaining page
 * (BMW Tuning, MHD Custom Tuning, the 5 BMW platform pages, Standalone
 * ECU/Motorsport, Dealer Services, Dealer File Service, Apply as a
 * Dealer, How It Works, Start Project, Contact -- 12 pages of real,
 * already-approved copy that doesn't need rewriting, only restyling),
 * this reskins WordPress's own CORE Gutenberg block class names
 * (wp-block-*), which every one of those pages already uses. One
 * stylesheet, applied sitewide, instead of 12 near-duplicate templates --
 * a genuine "reusable layout primitive" per Section 8's own instruction.
 *
 * Deliberately scoped to `.entry-content` only (WordPress's standard
 * post/page content wrapper, present regardless of which theme renders
 * it) -- never touches Blocksy's own header/footer/nav chrome, whose
 * exact markup this repository has no file-level visibility into (see
 * docs/modules/WEB-020_CHATGPT_REVIEW.md). This is the same safety
 * boundary WEB-026's token proposal drew: additive, never a guess at
 * Blocksy's internal selectors.
 *
 * Design tokens: WEB-026's provisional set (Electric Cyan / Space
 * Grotesk) -- the owner reacted positively to the homepage using this
 * exact combination ("home page looks much better"), which is the first
 * real-world signal on the open D3 accent/font decision, though still not
 * a formal final sign-off.
 */

/*
 * Post-launch stabilization (WEBSITE-TRANCHE-008): global body background
 * fallback. Blocksy's own default body background-color (a near-white
 * value from its stock color palette) was never overridden anywhere in
 * this theme -- normally fully hidden because every real page wrapper
 * (.tt-home, .tt-results, .tt-vt, .entry-content, .tt-service-hero) paints
 * its own dark background on top, but genuinely visible wherever those
 * wrappers don't fully cover the viewport: mobile rubber-band/overscroll
 * bounce at the top/bottom edge, any page shorter than the viewport, and
 * the moment before a section's own background paints on a slow load --
 * confirmed as the root cause of the header bar's own exposed-white
 * background above. This is a pure fallback -- every element with its own
 * real background (including every component above) is completely
 * unaffected; nothing "intentionally light" exists in this site's own
 * content areas to preserve here.
 */
body {
	background-color: var(--tt-color-obsidian, #0b0c0e);
}

.entry-content {
	background: var(--tt-color-bg, #0B0C0E);
	color: var(--tt-color-text-muted, #A6ABB1);
	font-family: var(--tt-font-body, 'Inter', sans-serif);
	line-height: var(--tt-leading-normal, 1.6);
	/* WEBSITE-TRANCHE-015 (owner video review, Section 3/16): was
	   --tt-space-7 (44px post-rescale, previously 48px) -- tightened to
	   --tt-space-6 (32px), the same normal-content-padding step every other
	   density change in this round targets. */
	padding: var(--tt-space-6, 2rem) var(--tt-space-5, 1.5rem);
	max-width: 900px;
	margin: 0 auto;
}

.entry-content h1,
.entry-content h2,
.entry-content h3,
.entry-content h4 {
	font-family: var(--tt-font-display, 'Space Grotesk', sans-serif);
	color: var(--tt-color-text, #F2F3F4);
	line-height: var(--tt-leading-tight, 1.1);
}

/* WEBSITE-TRANCHE-015 owner-video-review independent-review CONCERN #11
   (v0.14.0/v0.14.1): this block mapped article headings one full tier below
   style.css's own documented token intent (--tt-text-4xl is commented
   "H2-class usage", --tt-text-2xl "H3-class usage" -- this rule was using
   -2xl for h2 and -lg for h3), so real body-content h2s rendered at 24px
   against the governing prompt's 30-40px desktop target, and h3 rendered at
   18px, both undersized relative to every template-driven page's h2 (36px)
   and h3 (24px). Remapped one tier up to match the token system's own
   documented tiers -- no new tokens, no size invented. */
.entry-content h1 { font-size: var(--tt-text-5xl, 3rem); margin: 0 0 var(--tt-space-4, 1rem); }
.entry-content h2 {
	font-size: var(--tt-text-4xl, 2.25rem);
	/* WEBSITE-TRANCHE-015 (owner video review, Section 3): was
	   --tt-space-8 (56px post-rescale, previously 64px) -- every single h2
	   in every page's real body content paid this before it, on top of the
	   section-padding reductions elsewhere in this round. */
	margin: var(--tt-space-6, 2rem) 0 var(--tt-space-3, 0.75rem);
}
.entry-content h3 { font-size: var(--tt-text-2xl, 1.5rem); margin: var(--tt-space-5, 1.5rem) 0 var(--tt-space-2, 0.5rem); }

.entry-content > *:first-child { margin-top: 0; }

.entry-content p { margin: 0 0 var(--tt-space-4, 1rem); }
.entry-content a { color: var(--tt-color-accent, #00D9FF); }
.entry-content strong { color: var(--tt-color-text, #F2F3F4); }
.entry-content small { color: var(--tt-color-text-faint, #8A9098); font-size: var(--tt-text-sm, 0.875rem); }

.entry-content ul.wp-block-list,
.entry-content ol.wp-block-list {
	padding-left: var(--tt-space-5, 1.5rem);
}
.entry-content li { margin-bottom: var(--tt-space-2, 0.5rem); }

.entry-content hr.wp-block-separator {
	border: none;
	border-top: 1px solid var(--tt-color-border, #2A2D31);
	margin: var(--tt-space-7, 3rem) 0;
}

/* --- Buttons --- */
.entry-content .wp-block-button__link {
	font-family: var(--tt-font-display, 'Space Grotesk', sans-serif);
	font-weight: 600;
	background: var(--tt-color-accent, #00D9FF);
	color: #0B0C0E;
	border-radius: 6px;
	padding: var(--tt-space-3, 0.75rem) var(--tt-space-5, 1.5rem);
	text-decoration: none;
	transition: transform var(--tt-duration-fast, 120ms) var(--tt-ease-standard, ease);
}
.entry-content .wp-block-button__link:hover { transform: translateY(-1px); color: #0B0C0E; }
.entry-content .wp-block-button.is-style-outline .wp-block-button__link {
	background: transparent;
	color: var(--tt-color-text, #F2F3F4);
	border: 1px solid var(--tt-color-border, #2A2D31);
}
.entry-content .wp-block-buttons { gap: var(--tt-space-3, 0.75rem); }

/* --- Columns as compact cards --- */
.entry-content .wp-block-columns { gap: var(--tt-space-4, 1rem); margin: var(--tt-space-5, 1.5rem) 0; }
.entry-content .wp-block-column {
	background: var(--tt-color-bg-elevated, #16181B);
	border: 1px solid var(--tt-color-border, #2A2D31);
	border-radius: 10px;
	padding: var(--tt-space-5, 1.5rem);
}
.entry-content .wp-block-column > *:last-child { margin-bottom: 0; }

/* --- Images --- */
.entry-content figure.wp-block-image { margin: 0 0 var(--tt-space-4, 1rem); }
.entry-content figure.wp-block-image img { border-radius: 8px; display: block; width: 100%; height: auto; }
.entry-content figcaption { color: var(--tt-color-text-faint, #8A9098); font-size: var(--tt-text-sm, 0.875rem); margin-top: var(--tt-space-2, 0.5rem); }

/*
 * WEB-037 fix: real owner-reported defect -- two images on /bmw-tuning/
 * under "Proven Across the Platform Range" rendered visibly stretched
 * vertically. First pass (object-fit: cover below) stopped the outright
 * distortion but the owner correctly reported it "still the same" --
 * confirmed live the real root cause is one level up: this image gallery
 * is a WordPress Columns block (`wp-block-columns`, `display: flex`,
 * default `align-items: normal` == `stretch`). One sibling column in that
 * same row has enough real text content to make it much taller than the
 * others, and flexbox's default cross-axis stretch then forces EVERY
 * column in the row -- including the image-only ones -- to match that
 * height (measured live: a 150x150 image forced into a ~368x1500 box).
 * object-fit: cover alone just changes stretch into an extreme, heavily
 * cropped zoom of a square image into a very tall sliver -- still wrong,
 * just wrong in a different way. The real fix is align-self: flex-start
 * on the specific column that holds a thumbnail-sized image, so that
 * column sizes to its own natural content height regardless of a taller
 * sibling -- scoped narrowly (:has() on the size-thumbnail class, which
 * only these platform-gallery images use) so it does not touch any other
 * wp-block-columns layout sitewide (e.g. Dealer Services' text-and-link
 * "Service Paths" cards, which should keep their current equal-height
 * stretch behavior).
 *
 * WEB-038 follow-up: `align-self: flex-start` alone already fully fixes the
 * real bug (the column now sizes to its own content, so the image is never
 * height-constrained in the first place). The original repair additionally
 * applied `object-fit: cover` to *every* `.entry-content img` sitewide as a
 * blanket safety net -- inert on any image that keeps its natural
 * `height: auto` (object-fit only does anything once a box's height is
 * externally constrained), but a real doctrine violation per
 * `docs/prompts/active/WEBSITE-TRANCHE-007_REAL_TUNER_CONTENT_AND_INTAKE_STRATEGY.md`
 * Section 10 ("per-image focal point/object-position and stable aspect
 * ratios, not one global object-fit") and a latent risk for any future
 * content image that *does* end up in a constrained box for an unrelated
 * reason. Narrowed to the one real case that needs it: a thumbnail-sized
 * image inside a Columns block, the exact shape of the original bug. Real
 * per-image focal point (object-position) is handled separately, sitewide,
 * by inc/image-focal-point.php -- it does not depend on this rule.
 */
.entry-content .wp-block-column:has( > figure.wp-block-image.size-thumbnail ) {
	align-self: flex-start;
}
.entry-content .wp-block-column:has( > figure.wp-block-image.size-thumbnail ) img {
	object-fit: cover;
}

/* --- Tables (still used on the BMW platform pages) --- */
.entry-content .wp-block-table table { width: 100%; border-collapse: collapse; }
.entry-content .wp-block-table th,
.entry-content .wp-block-table td {
	border: 1px solid var(--tt-color-border, #2A2D31);
	padding: var(--tt-space-3, 0.75rem);
	text-align: left;
	color: var(--tt-color-text, #F2F3F4);
}
.entry-content .wp-block-table thead th { color: var(--tt-color-text-muted, #A6ABB1); font-weight: 600; }

@media (max-width: 640px) {
	/* WEBSITE-TRANCHE-009: real measurement (BMW hub page, /bmw-tuning/,
	   390px viewport) found .entry-content's own desktop-tuned rhythm --
	   64px top margin before every single h2, 48px section-divider hr
	   margins, full desktop-scale column-card padding -- a meaningful
	   contributor on every page built from real Gutenberg content (the
	   majority of the site) once wp-block-columns cards wrap to a single
	   column below 640px, not just the homepage/service-page primitives
	   already tightened in elite-components.css. */
	.entry-content { padding: var(--tt-space-6, 2rem) var(--tt-space-4, 1rem); }
	.entry-content h1 { font-size: var(--tt-text-3xl, 2.441rem); }
	/* CONCERN #11 repair: the desktop h2 bump above (24px -> 36px) would
	   overshoot the governing prompt's own mobile H2 target (26-32px) if left
	   unset here -- explicit literal value, same pattern already used by
	   elite-components.css's own .tt-section-header h2 mobile override. */
	.entry-content h2 { font-size: 1.75rem /* 28px */; margin-top: var(--tt-space-6, 2rem) !important; }
	.entry-content hr.wp-block-separator { margin: var(--tt-space-5, 1.5rem) 0 !important; }
	.entry-content .wp-block-columns { flex-wrap: wrap; gap: var(--tt-space-3, 0.75rem) !important; margin: var(--tt-space-4, 1rem) 0 !important; }
	.entry-content .wp-block-column { padding: var(--tt-space-4, 1rem) !important; }
}

/*
 * WEB-031: visible vehicle-context handoff banner (see
 * inc/vehicle-context-banner.php). Scoped the same way as the rest of this
 * file -- prepended inside .entry-content by the_content filter, so it
 * inherits nothing from Blocksy chrome and needs its own explicit styling.
 */
.tt-vehicle-context-banner {
	background: var(--tt-color-bg-elevated, #16181B);
	border: 1px solid var(--tt-color-accent, #00D9FF);
	border-radius: 8px;
	padding: var(--tt-space-4, 1rem) var(--tt-space-5, 1.5rem);
	margin: 0 0 var(--tt-space-6, 2rem);
}
.tt-vehicle-context-banner p {
	margin: 0;
	color: var(--tt-color-text, #F2F3F4);
}
.tt-vehicle-context-banner .tt-vcb-gen {
	color: var(--tt-color-text-muted, #A6ABB1);
}
.tt-vehicle-context-banner a {
	color: var(--tt-color-accent, #00D9FF);
}

/*
 * WEBSITE-TRANCHE-015 (owner video review, Section 14) -- Contact page
 * compaction. inc/t15-density-content-filters.php restructures the real,
 * unchanged the_content() copy (same text, same links, nothing rewritten)
 * into a compact card row for "Contact Routes" and a dense multi-panel grid
 * for "Information to Include" / "No Uploads, No Payment Details" /
 * "Response Expectations" -- these classes are the visual side of that
 * restructure. Scoped to `.entry-content` only, same boundary as every
 * other rule in this file.
 */
.tt-contact-route-grid {
	display: grid;
	grid-template-columns: repeat(auto-fit, minmax(220px, 1fr));
	gap: var(--tt-space-3, 0.75rem);
	margin: 0 0 var(--tt-space-4, 1rem);
}
.tt-contact-route-card {
	background: var(--tt-color-bg-elevated, #16181B);
	border: 1px solid var(--tt-color-border, #2A2D31);
	border-radius: 8px;
	padding: var(--tt-space-4, 1rem);
	margin: 0;
	font-size: var(--tt-text-sm, 0.875rem);
}
.tt-contact-info-grid {
	display: grid;
	grid-template-columns: repeat(auto-fit, minmax(240px, 1fr));
	gap: var(--tt-space-4, 1rem);
	margin: 0 0 var(--tt-space-4, 1rem);
}
.tt-contact-info-panel {
	background: var(--tt-color-bg-elevated, #16181B);
	border: 1px solid var(--tt-color-border, #2A2D31);
	border-radius: 8px;
	padding: var(--tt-space-4, 1rem);
}
.tt-contact-info-panel h3 {
	font-family: var(--tt-font-display, 'Space Grotesk', sans-serif);
	/* CONCERN #11 repair: this was --tt-text-base (16px), literally identical
	   to this panel's own body text, against the governing prompt's 20-28px
	   H3 target. */
	font-size: var(--tt-text-xl, 1.25rem);
	color: var(--tt-color-text, #F2F3F4);
	margin: 0 0 var(--tt-space-2, 0.5rem);
}
.tt-contact-info-panel > *:last-child { margin-bottom: 0; }
@media (max-width: 640px) {
	.tt-contact-route-grid,
	.tt-contact-info-grid { grid-template-columns: 1fr !important; }
}

/*
 * WEB-012 header submenu fix, re-homed here permanently.
 *
 * Originally applied as WordPress Customizer "Additional CSS" (see
 * docs/manual/WEB-012_BLOCKSY_SUBMENU_VISUAL_FIX_STEPS.md) -- but
 * Additional CSS is stored per active theme, and activating
 * timingtech-blocksy-child for the first time this tranche silently lost
 * it, regressing the BMW Tuning / Dealer Services / Vehicle Directory
 * header dropdowns back to white text on a white background. Found by
 * this tranche's own independent review pass against real staging, not
 * caught by any of this tranche's own test suites since none of them
 * inspect the desktop header dropdown submenu. Moved into a real,
 * version-controlled theme file so it can never again be silently lost to
 * a theme switch -- same fix, same exact selectors, unchanged.
 */
[data-header*="type-1"] .ct-header [data-id="menu"] .sub-menu {
	--dropdown-background-color: var(--theme-palette-color-8);
}

/*
 * Real gap found in the fix above after the owner reported the submenu was
 * still white in actual use: Blocksy renders TWO copies of each dropdown
 * submenu in the DOM (one with an `animated-submenu-block`/`-inline` class,
 * one without) -- the selector above only reaches the animated copy. Rather
 * than chase Blocksy's exact duplicate-markup structure further, this is a
 * direct, unconditional override on Blocksy's own `.sub-menu` class itself,
 * so it's correct regardless of which copy the browser actually renders.
 */
.ct-header .sub-menu {
	background-color: #1f1f1f !important;
}
.ct-header .sub-menu .ct-menu-link {
	color: #ffffff !important;
}

/*
 * WEB-035: header/nav depth + active-section identity.
 *
 * Every selector below targets real classes confirmed live via a direct
 * fetch of the rendered homepage HTML (WEB-035 build notes) -- .ct-header,
 * .header-menu-1, .ct-menu-link, .sub-menu, .mobile-menu -- the same
 * confirm-before-guess discipline the WEB-012 submenu fix above already
 * established, never a blind guess at Blocksy's internal structure.
 * Scoped to hover/focus/active states and depth (shadow, spacing, an
 * accent underline sweep) -- never touches layout structure Blocksy itself
 * owns, so a Blocksy update cannot silently break this.
 */
/*
 * Post-launch stabilization (WEBSITE-TRANCHE-008): real production visual
 * review found this rule never actually set a background-color on the
 * header bar itself -- only border/shadow "depth" -- so the header was
 * genuinely transparent, exposing the page's own unstyled light `body`
 * background (Blocksy's own default, see the body rule below) straight
 * through it. Confirmed the same on the pre-migration staging site too, so
 * this predates the domain cutover; not something the migration broke.
 */
.ct-header {
	background-color: var(--tt-color-charcoal, #131518);
	border-bottom: 1px solid var(--tt-color-border, #2a2d31);
	box-shadow: var(--tt-shadow-2, 0 4px 12px rgba(0,0,0,0.45));
}
.ct-header .header-menu-1.menu-container > ul.menu > li > a.ct-menu-link {
	position: relative;
	transition: color var(--tt-duration-base, 200ms) var(--tt-ease-standard, ease);
}
.ct-header .header-menu-1.menu-container > ul.menu > li > a.ct-menu-link::after {
	content: "";
	position: absolute;
	left: 0; right: 100%;
	bottom: -6px;
	height: 2px;
	background: var(--tt-color-accent, #00d9ff);
	transition: right var(--tt-duration-base, 200ms) var(--tt-ease-standard, ease);
}
.ct-header .header-menu-1.menu-container > ul.menu > li:hover > a.ct-menu-link::after,
.ct-header .header-menu-1.menu-container > ul.menu > li.current-menu-item > a.ct-menu-link::after,
.ct-header .header-menu-1.menu-container > ul.menu > li.current_page_item > a.ct-menu-link::after,
.ct-header .header-menu-1.menu-container > ul.menu > li.current_page_ancestor > a.ct-menu-link::after {
	right: 0;
}
.ct-header .header-menu-1.menu-container > ul.menu > li.current-menu-item > a.ct-menu-link,
.ct-header .header-menu-1.menu-container > ul.menu > li.current_page_item > a.ct-menu-link {
	color: var(--tt-color-accent, #00d9ff);
}

/* Dropdown visual depth -- the WEB-012 fix above guarantees a correct dark
   background; this adds the elevation/border/motion the elite doctrine
   calls for on top of that already-safe base. */
.ct-header .sub-menu {
	border: 1px solid var(--tt-color-border-metallic, #3a3f46) !important;
	border-radius: var(--tt-radius-md, 8px);
	box-shadow: var(--tt-shadow-3, 0 12px 32px rgba(0,0,0,0.5));
	padding: var(--tt-space-2, 0.5rem) 0;
	overflow: hidden;
}
.ct-header .sub-menu .ct-menu-link {
	transition: background-color var(--tt-duration-fast, 120ms) var(--tt-ease-standard, ease), padding-left var(--tt-duration-fast, 120ms) var(--tt-ease-standard, ease);
}
.ct-header .sub-menu li:hover > .ct-menu-link,
.ct-header .sub-menu li:focus-within > .ct-menu-link {
	background-color: var(--tt-color-bg-elevated-2, #1e2124);
	padding-left: calc(var(--tt-space-4, 1rem) + 4px);
}

/* Mobile drawer -- spacing/active-state only; Blocksy's own drawer
   background is not overridden here since no live regression report has
   ever named it (unlike the desktop submenu, which WEB-012/WEB-033 both
   had to fix), so this stays additive rather than a speculative rewrite. */
.mobile-menu.menu-container .menu-item.current-menu-item > a.ct-menu-link {
	color: var(--tt-color-accent, #00d9ff);
}

/*
 * WEBSITE-TRANCHE-009: header/logo rebuild.
 *
 * Real root cause (confirmed live against staging via
 * document.elementFromPoint + a walk of every matching CSSOM rule, not
 * assumed): `.ct-header`'s own background-color fix above (WEB-035/
 * TRANCHE-008) *is* applying -- the header element's own computed
 * background is already the correct charcoal. The visible white bar sits
 * one level deeper: Blocksy's own bundled CSS independently paints each
 * header BUILDER ROW's background via
 * `[data-header*="type-1"] .ct-header [data-row*="middle"]` (source:
 * siteground-optimizer-combined-css) using
 * `var(--theme-palette-color-8)`, which resolves to white and has never
 * been overridden -- a distinct bug from the `.ct-header` background
 * itself and from the dropdown-submenu bug fixed above (same
 * `--theme-palette-color-8` token, different property/selector, same root
 * cause pattern: an unstyled Blocksy default surfacing through). `!important`
 * (matching this file's own existing convention for exactly this class of
 * Blocksy-internal-specificity fight, see the `.ct-header .sub-menu` rule
 * above) rather than trying to out-specificity every current and future
 * header row variant individually.
 */
[data-header*="type-1"] .ct-header [data-row] {
	background: var(--tt-color-charcoal, #131518) !important;
}

/*
 * The logo itself: the Customizer's currently-set "site logo" image is a
 * raw raster export of this exact TimingTech wrench/wordmark, on an opaque
 * black canvas (confirmed live) -- a hard-edged "sticker" sitting on the
 * header once the white row bug above is fixed, not a real integrated
 * mark. WordPress's site-logo Customizer field is not REST-writable
 * (confirmed: no `theme_mods` field on `/wp/v2/settings`, no
 * `/blocksy/...` REST route -- docs/modules/WEB-020_CHATGPT_REVIEW.md), so
 * this repository cannot swap the underlying attachment directly; instead
 * the real `<img class="default-logo">` (untouched WP data) is visually
 * replaced and the genuinely transparent mark this tranche derived from
 * the owner's own vector-shaped PDF source
 * (assets/brand/logo/TimingTech Tuning Logo.PDF -- see
 * assets/images/timingtech-logo-mark.png's sibling files for the derived
 * set) is painted as a background-image on the anchor instead.
 *
 * WEBSITE-TRANCHE-009 live-site independent review (post-deploy, v0.4.1):
 * the first version of this rule used `display:none` on the old <img>,
 * which removes an element -- and its real `alt="TimingTech Tuning"` --
 * from the accessibility tree entirely, confirmed live as a genuine
 * regression (the header link had NO accessible name in the actual
 * server-rendered HTML, only gaining one via a JS listener that could
 * fail/be blocked/not have run yet). Fixed by using this theme's own
 * `.tt-sr-only` visually-hidden-but-accessible pattern instead of
 * `display:none` -- the old image stays in the accessibility tree (still
 * zero-size and invisible on screen), so its own real `alt` text keeps
 * supplying the anchor's accessible name natively, exactly as it did
 * before this tranche touched the header, with no JavaScript dependency.
 * inc/header-logo.php's aria-label script is kept only as a harmless,
 * no-longer-load-bearing extra reinforcement.
 */
/* WEBSITE-TRANCHE-015 real-tuner repair (Section 15): the header is still
   too tall on 14-15" laptops. Blocksy's own header row supplies no
   vertical-padding override in this child theme (confirmed: no existing
   `.ct-header [data-row]` padding rule anywhere in this codebase, so
   desktop height was entirely Blocksy's own default row padding plus this
   logo box's height) -- an explicit, modest row padding is set below
   alongside a ~16% shorter logo box (44px -> 37px, keeping its 190:44
   aspect ratio via `background-size:contain` so the mark itself is not
   distorted) for a real, coherent ~15% reduction rather than a logo-only
   change. Click/tap target size is unaffected -- the logo link's own
   hit-area is the full nav row height, not just the visible mark. */
.ct-header [data-row] {
	padding-top: 10px;
	padding-bottom: 10px;
}
.site-branding .site-logo-container {
	display: block;
	width: 160px;
	height: 37px;
	background-image: url("../images/timingtech-logo-mark-2x.png");
	background-repeat: no-repeat;
	background-position: left center;
	background-size: contain;
}
.site-branding .site-logo-container img.default-logo {
	position: absolute;
	width: 1px;
	height: 1px;
	padding: 0;
	margin: -1px;
	overflow: hidden;
	clip: rect(0, 0, 0, 0);
	white-space: nowrap;
	border: 0;
}
/* The redundant text wordmark next to the image logo -- our new mark
   already renders "TimingTech Tuning" as part of the graphic itself. */
.site-branding .site-title-container {
	display: none;
}
@media (max-width: 640px) {
	.site-branding .site-logo-container {
		width: 150px;
		height: 35px;
	}
}
