/*
 * Himadi content templates — supplementary styling only.
 * The ported sections themselves are built from real WordPress block
 * markup (wp-block-cover, wp-block-columns, wp-block-buttons, etc.) so they
 * pick up Spexo's own block-library CSS and the site's configured
 * theme.json color/typography tokens directly. This file only covers the
 * handful of things that markup doesn't already style.
 * Loaded site-wide — see inc/himadi-integration.php.
 */

/* Digital Marketing page — its 4 service cards (SEO/Content/Social/Email),
   always exactly 2 per row ("two cards above two cards below") regardless
   of viewport width — a real grid instead of the Home page's flex-wrap
   row, which was letting all 4 try to fit on one line and overflow past
   the narrow intro column next to the Services sidebar. Fixed 300px square
   columns (not 1fr) and its own capped width, independent of
   .himadi-dm-page-content's own (wider) max-width — the title/paragraph
   block above was widened to cut down on side whitespace, but the cards
   stay their original square size regardless of that. */
.himadi-dm-services-grid {
	display: grid;
	/* First brought down from 400px -> 370px to match the other card
	   grids, but still read as too big on this specific 4-card page --
	   shrunk further here (370 -> 300, 275 -> 220) per explicit
	   follow-up request, just for this grid. */
	grid-template-columns: repeat(2, 340px);
	gap: 24px;
	justify-content: center;
	max-width: 704px;
	margin: 30px auto 0;
}

.himadi-dm-services-grid .himadi-service-card {
	/* 250px let the "Social Media Marketing" card's paragraph (the
	   longest of the 4) overflow past the card's bottom edge by ~9px --
	   bumped up just enough to fit it. */
	height: 260px;
}

@media (max-width: 600px) {
	.himadi-dm-services-grid {
		grid-template-columns: 1fr;
		max-width: 400px;
	}
}

/* These 4 cards' titles range from one short word ("SEO") to three
   ("Social Media Marketing"), but .himadi-service-card-front (shared with
   Home's cards, which don't have this problem) centers the whole
   icon+title+paragraph block as a single unit — a longer title wrapping to
   a 2nd line makes that whole block taller, which shifts its centered
   icon/title further down than a card with a short one-line title right
   next to it in the same row. Anchoring from the top instead, with a
   fixed-height slot for the title, keeps every card's icon and title at
   the same position regardless of how long its own title is. */
.himadi-dm-services-grid .himadi-service-card-front {
	justify-content: flex-start;
	padding-top: 36px;
}

.himadi-dm-services-grid .himadi-service-card-front h5 {
	display: flex;
	align-items: center;
	justify-content: center;
	min-height: 54px;
}

/* Digital Marketing family pages (template-blank.php) — content spans the
   full container width, centered, instead of being squeezed into a 64%
   intro column beside the Services sidebar (which reads as "stuck on the
   left side of the page" once the sidebar box eats the other 36%). The
   sidebar now sits below as a horizontal row instead of a side column —
   see .himadi-services-sidebar--row below. */
.himadi-dm-page-content {
	max-width: 1150px;
	margin: 0 auto;
	text-align: center;
}

/* Intro title + paragraph at the top of Digital Marketing and its 4
   sub-pages (SEO, Content Marketing, Social Media Marketing, Email
   Marketing) -- explicit request to reduce both by 5px. The ">" child
   selector targets only these direct intro elements, not the h3/p text
   nested inside the .columns.himadi-card boxes further down the page
   (already sized separately). The paragraph's font-size is inline in the
   page content itself (17px), so !important is required to override it
   from here instead of editing that content directly. */
/* Matched to the exact same size as the .himadi-card boxes further down
   this page (.heading3 at 22px, box paragraphs at 14px) per explicit
   request -- the earlier standalone reductions (-5px, then -3px more)
   ended up far smaller than the boxes' own text, an inconsistent-looking
   mismatch rather than a deliberate size. */
.himadi-dm-page-content > h2 {
	font-size: 22px;
}

.himadi-dm-page-content > p {
	font-size: 14px !important;
}

/* The alternating image+text boxes (SEO/Content/Social/Email Marketing
   sub-pages) inherit text-align:center from .himadi-dm-page-content above
   — fine for the top title/intro paragraph, but it made box paragraphs
   and bullet lists (e.g. Content Marketing's "A Voice That Sounds Like
   You" format list) read ragged/inconsistent line-to-line. Left-align
   just the box content, not the intro above it. */
.himadi-dm-page-content .columns.himadi-card .col-md-6 {
	text-align: left;
}

.himadi-services-sidebar--row {
	max-width: 1150px;
	margin: 30px auto 0;
	text-align: center;
}

/* :root h3.wp-block-heading{color:var(--heading3-text-color)} in the
   vendor stylesheet outscores the plain .himadi-heading-blue class
   (:root pseudo-class + element+class beats a lone class), so "Our
   Digital Marketing Services" was rendering in the default dark heading
   color instead of blue despite having that class. */
h3.wp-block-heading.himadi-heading-blue {
	color: #2563eb !important;
}

.himadi-services-sidebar--row ul {
	display: flex;
	flex-wrap: wrap;
	justify-content: center;
	gap: 12px;
	/* !important: the base .himadi-services-sidebar ul rule (further down
	   this file) sets margin:0 shorthand and wins the cascade on source
	   order at equal specificity, otherwise zeroing this back out. */
	margin-top: 18px !important;
}

.himadi-services-sidebar--row li {
	margin-bottom: 0;
}

.himadi-services-sidebar--row a {
	padding: 10px 20px;
}

/* Sticky header — the logo+nav bar (Home/About Us/Services/.../Contact Us)
   stays pinned to the viewport top on scroll instead of scrolling away
   with the page. Only .tmpcoder-site-header itself (not the "Contact
   Sales:" phone-number bar above it, tmpcoder_header_before()) is made
   sticky, so that thin bar scrolls off normally and the nav takes its
   place at the very top — the usual pattern, and simpler than
   position:fixed since it needs no compensating body/content padding. */
.tmpcoder-site-header {
	position: sticky;
	top: 0;
	z-index: 999;
}

/* Spexo only centers/caps page content via the .page-content class, which
   is added by template-parts/content-page.php on the DEFAULT page template.
   Our custom Template Name pages don't go through that file, so their
   content was rendering full viewport width with no side margins at all
   (site-main itself has no width cap outside a WooCommerce archive body
   class). himadi-container is the same centering rule, used as an inner
   wrapper wherever our templates need it — including inside full-bleed
   (alignfull) colored sections, where only the background should bleed
   edge-to-edge and the content inside still needs to stay contained. */
.himadi-container {
	max-width: var(--tmpcoder-container-width, 1200px);
	margin: 0 auto;
	padding: 0 15px;
	box-sizing: border-box;
}

/* "Latest From The Blog" cards -- at window widths close to the site's
   1270px container width (e.g. ~1282px), the visible left/right margin
   shrinks to just a few px since there's so little room left outside the
   container. A fixed extra side padding here guarantees real, visible
   white space on both sides regardless of how close the window width is
   to the container's own max-width. */
.himadi-blog-preview-container {
	padding-left: 50px;
	padding-right: 50px;
}

/* Home page "About Us" / "Why Choose Us" / "Our Industry Experience" text
   columns (template-home.php) -- explicit request to reduce these three
   boxes' overall vertical height. The heading font-size itself is already
   correct (clamp(), confirmed via devtools at 1368px wide), so this
   tightens paragraph line-height/spacing only, not font-size, to shrink
   the block's height without making the text itself smaller. */
.himadi-tight-text p {
	line-height: 1.35;
	margin-bottom: 6px;
}

/* Default desktop heading sizes (tmpcoder-customizer-option-inline-css:
   52px/40px h1/h2) only ever looked right on a very wide/large monitor.
   WordPress already has its own tablet step-down for these same vars below
   1025px, but above that the full desktop size renders noticeably
   larger/more cramped on anything narrower than a wide monitor.

   This used to be a fixed px value applied via plain breakpoints (first
   1025-1440px, then widened to "1025px and up"), but that chases a moving
   target: the same nominal screen width (e.g. two laptops both sold as
   "1366px") can hand the browser a different EFFECTIVE CSS width depending
   on the OS's own display-scaling setting (Windows "Scale" 100/125/150%,
   macOS "Looks like" resolution, etc.) -- confirmed directly, two 1366px
   laptops side by side rendered this differently. No fixed breakpoint list
   can cover every OS-scaling combination; clamp() scales continuously with
   whatever the real viewport width turns out to be, so there's no specific
   width left to miss.

   clamp(MIN, preferred, MAX) -- preferred is a straight line through
   (1025px wide -> MIN) and (1920px wide -> MAX), the two ends already
   confirmed to look right; clamp() just holds it level outside that span
   instead of overshooting. Below the 1025px media query boundary, WordPress's
   own tablet/mobile vars (40/33px h1, 34/20px h2) take over unchanged.

   !important on all three -- confirmed via a real machine's devtools dump
   that tmpcoder-customizer-option-inline-css's own `:root, .editor-styles-
   wrapper { --heading1-font-size: 52px; ... }` block was ALSO present and
   matching alongside this rule. Both are plain `:root`, so they're equal
   specificity; without !important, whichever one WordPress happens to
   print later in <head> wins, and that print order isn't guaranteed to be
   the same across environments (plugin/customizer state can shift it) --
   which is exactly why this looked fixed on one machine/site and not
   another even though both had the same CSS file. !important removes that
   coin flip entirely. */
@media (min-width: 1025px) {
	:root {
		--heading1-font-size: clamp(44px, 0.894vw + 34.84px, 52px) !important;
		--heading2-font-size: clamp(34px, 0.670vw + 27.13px, 40px) !important;
		--heading3-font-size: clamp(19px, 0.335vw + 15.57px, 22px) !important;
	}
}

/* Default page.php pages with a featured image (Disclaimer, Certifications,
   Privacy Policy, Anti-Bribery Policy, etc.) — tmpcoder_post_thumbnail()'s
   .post-thumbnail wrapper (only ever used in the singular/is_singular()
   branch, from content-page.php — the non-singular <a> variant is never
   actually called anywhere in this theme) had no CSS anywhere, so the
   image rendered at its native pixel size with a gap on wider screens.
   Styled here as a hero banner (fixed height, cover, dim overlay) to match
   himadi_render_hero() on the ported templates, with the page title pulled
   up on top of it via negative margin — .post-thumbnail and .entry-content
   are siblings, not nested, so this is the only way to visually overlay
   text from one onto the other without a new PHP template for every one
   of these simple utility pages. */
.post-thumbnail {
	position: relative;
	height: 500px;
	overflow: hidden;
}

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

.post-thumbnail::after {
	content: "";
	position: absolute;
	inset: 0;
	background: rgba(0, 0, 0, 0.4);
}

/* Same pages' auto page title: unlike the Blog/Case Study listings, this
   h1 isn't wrapped in .page-header (page.php only adds that wrapper when
   the content has no blocks — see content-page.php's has_blocks() check),
   so it never picked up that wrapper's styling and just sat left, below
   the image, as plain dark text. Negative top margin pulls it up onto the
   image; the matching positive bottom margin pushes the rest of the
   content (the paragraphs right after it) back down by the same amount,
   so only the title overlaps the image, not the body text. */
.entry-content.page-content > h1.entry-title {
	position: relative;
	z-index: 1;
	text-align: center;
	color: #fff;
	margin-top: -280px;
	margin-bottom: 280px;
	/* Same rise-from-below scroll reveal as the rest of the site — targeted
	   by this existing selector rather than a marker class, same reasoning
	   as .page-header .entry-title/.blog-list-box elsewhere: this heading
	   is printed by content-page.php (a vendor file), not something we
	   template ourselves. */
	animation: himadi-fade-in-up 700ms ease-out both;
	animation-play-state: paused;
}

/* Certifications (page ID 48) — this auto-generated title (overlaid on
   the hero photo) repeated the page's own on-page heading a second time,
   per explicit request to remove it. */
body.page-id-48 .entry-content.page-content > h1.entry-title {
	display: none;
}

/* himadi_render_hero()'s own default min-height is 320px — every page using
   the shared hero (About Us, Career, Contact, Services, EVS Software, etc.)
   gets that automatically. Home is the one exception: it deliberately stays
   taller (850px, passed explicitly at the himadi_render_hero() call site in
   template-home.php), which is part of why the About Us card below it
   requires an actual scroll to reach rather than being visible on load. */
/* Scoped to .himadi-home-hero specifically, not every .wp-block-cover.
   alignfull on the Home page — it used to match ALL of them, which
   included the "Get Started With Himadi" cover further down the page
   and force-capped IT at 760px too regardless of its own much smaller
   inline min-height. */
body.home .himadi-home-hero.wp-block-cover.alignfull {
	/* !important because min-height:320px is set as an inline style on the
	   element (himadi_render_hero()) — a plain CSS class rule loses to that
	   regardless of specificity unless it's also marked important. Must be
	   kept in sync with the height passed in template-home.php's
	   himadi_render_hero() call — this rule wins the cascade over it. */
	min-height: 760px !important;
}

/* Home hero — left-aligned, two auto-rotating slides (himadi_render_home_hero()
   / himadi-hero-slider.js), matching the Spexo/Cleano demo hero layout
   (eyebrow + bold title + description + button, text on the left over the
   photo) instead of the centered single-title style every other page uses. */
.himadi-home-hero .wp-block-cover__inner-container {
	width: 100%;
	max-width: 1200px;
	margin: 0 auto;
	padding-left: 40px;
	padding-right: 40px;
	position: relative;
	align-items: flex-start;
	text-align: left;
	/* !important, and well clear of the ::after scrim's z-index:1 below --
	   .wp-block-cover is a flex container (core CSS), and this element is
	   an in-flow flex item while the scrim is an out-of-flow absolutely
	   positioned sibling; browsers don't reliably stack a flex item above
	   an absolutely-positioned sibling by z-index value alone the way two
	   plain positioned siblings would. Confirmed by testing: z-index:2
	   here (matching core's own default) still let the scrim paint over
	   the hero text; nothing lower than this reliably won. */
	z-index: 5 !important;
}

/* The two per-slide background photos (himadi_render_home_hero()) --
   stacked directly on top of each other and cross-faded in sync with the
   text via .is-active, same mechanism as .himadi-hero-slide below, so one
   photo change in the JS timer drives both the text and the photo behind
   it at once. */
.himadi-hero-bg {
	position: absolute;
	inset: 0;
	width: 100%;
	height: 100%;
	object-fit: cover;
	opacity: 0;
	transition: opacity 600ms ease;
}

/* White hero text over these two photos (a bright office desk, a light
   wood desk) read as "dull"/hard to read even at full white with a text
   shadow — both photos are simply too light behind it, and this hero runs
   with the overlay dim intentionally at 0% (see himadi_render_hero()'s
   docblock) so the photo itself stays untouched. A soft gradient fade
   here wasn't solid enough to fix it — per the Spexo/Cleano reference
   demo this is modeled on, the text sits on a near-solid dark panel, not
   a light tint, so this now goes almost fully opaque behind the text
   itself and only fades out (over a short span, not a long one) once
   past where the text ends. */
.himadi-home-hero::after {
	content: '';
	position: absolute;
	inset: 0;
	background: linear-gradient(90deg, rgba(0, 0, 0, 0.62) 0%, rgba(0, 0, 0, 0.55) 45%, rgba(0, 0, 0, 0.32) 60%, rgba(0, 0, 0, 0) 80%);
	pointer-events: none;
	z-index: 1;
}

.himadi-hero-bg.is-active {
	opacity: 1;
}

.himadi-hero-slider {
	position: relative;
	width: 100%;
	min-height: 320px;
}

.himadi-hero-slide {
	position: absolute;
	top: 0;
	left: 0;
	width: 100%;
	max-width: 640px;
	opacity: 0;
	visibility: hidden;
	transition: opacity 600ms ease;
	text-align: left;
}

.himadi-hero-slide.is-active {
	position: relative;
	opacity: 1;
	visibility: visible;
}

/* Manual slide navigation -- a single "next" arrow on the right edge,
   vertically centered, instead of dots along the bottom. Semi-transparent
   white circle (matching the old dots' contrast approach against a full
   photo background), solid on hover so it reads as clickable. */
.himadi-hero-next {
	position: absolute;
	top: 50%;
	right: 24px;
	transform: translateY(-50%);
	width: 46px;
	height: 46px;
	padding: 0;
	display: flex;
	align-items: center;
	justify-content: center;
	border: 1px solid rgba(255, 255, 255, 0.8);
	border-radius: 50%;
	background: rgba(255, 255, 255, 0.2);
	color: #fff;
	cursor: pointer;
	/* !important for the same reason as .himadi-hero-slider's z-index:5
	   above -- .himadi-hero-slider is a flex item spanning the full hero
	   width, and on mobile (where the text block runs taller relative to
	   the hero) its invisible box reaches down far enough to sit over this
	   button and swallow the click, even though the button paints visibly
	   on top of it. */
	z-index: 6 !important;
	transition: background 150ms ease, transform 150ms ease;
}

.himadi-hero-next:hover {
	background: rgba(255, 255, 255, 0.35);
	transform: translateY(-50%) scale(1.06);
}

.himadi-hero-next svg {
	width: 22px;
	height: 22px;
}

@media (max-width: 767px) {
	.himadi-hero-next {
		width: 38px;
		height: 38px;
		right: 14px;
	}

	.himadi-hero-next svg {
		width: 18px;
		height: 18px;
	}
}

.himadi-hero-eyebrow {
	display: inline-block;
	/* !important: same cause as h3.wp-block-heading.himadi-heading-blue
	   below — a vendor :root-prefixed heading-color rule ties this
	   selector's specificity, and without !important it's a coin flip
	   which one wins (here it was losing, rendering the whole hero text
	   dark instead of white/blue). */
	color: #60a5fa !important;
	font-size: 13px;
	font-weight: 600;
	text-transform: uppercase;
	letter-spacing: 0.5px;
	margin-bottom: 10px;
	/* Two layers: a tight, dark near-outline so the letterforms stay
	   crisply defined against any part of the photo, plus the original
	   soft blur behind that for depth. One shadow alone still took a
	   second look to read clearly. */
	text-shadow: 0 1px 2px rgba(0, 0, 0, 0.95), 0 2px 6px rgba(0, 0, 0, 0.7);
}

.himadi-hero-slide h1.wp-block-heading {
	/* !important: :root h1.wp-block-heading (vendor) ties this selector's
	   specificity exactly (2 classes + 1 element either way) — without it,
	   cascade order alone decided the winner and this title was rendering
	   in the vendor's dark heading color instead of white. */
	color: #fff !important;
	font-size: 40px;
	font-weight: 700;
	text-align: left;
	margin-top: 0;
	margin-bottom: 16px;
	text-shadow: 0 1px 3px rgba(0, 0, 0, 0.95), 0 2px 10px rgba(0, 0, 0, 0.75);
}

.himadi-hero-slide p {
	color: #fff !important;
	font-size: 16px;
	text-align: left;
	max-width: 560px;
	margin: 0 0 28px;
	text-shadow: 0 1px 2px rgba(0, 0, 0, 0.95), 0 2px 8px rgba(0, 0, 0, 0.8);
}

.himadi-hero-button {
	display: inline-block;
	background: #2563eb;
	color: #fff !important;
	font-weight: 600;
	text-decoration: none !important;
	padding: 14px 32px;
	border-radius: 4px;
	transition: background 200ms ease;
}

.himadi-hero-button:hover {
	background: #1d4ed8;
}

@media (max-width: 782px) {
	.himadi-home-hero .wp-block-cover__inner-container {
		padding-left: 20px;
		padding-right: 20px;
	}

	.himadi-hero-slide h1.wp-block-heading {
		font-size: 28px;
	}
}

/* Main header nav links (Home, About Us, Services, ...) — bumped up from
   Spexo's own 14px base. Their hover/current-page recolor (purple to sky
   blue) is handled further down, in the .site-navigation .menu li... block
   near .site-branding — that block already existed and already covered
   every state (hover, focus, current item, current ancestor) via
   var(--theme-link-color), it just needed its own var() fallback actually
   applied. */
.site-navigation > ul.menu > li > a,
body .tmpcoder-site-header nav.site-navigation > div.menu > ul > li > a {
	font-size: 16px;
}

/* !important needed here -- style.min.css's own default-state color rule
   is qualified as "body .tmpcoder-site-header nav.site-navigation>ul.menu>li>a"
   (extra body/.tmpcoder-site-header/nav ancestors), which out-specifies the
   plain ".site-navigation > ul.menu > li > a" selector above, so a plain
   color here was silently losing to that rule's var(--theme-text-color). */
body .tmpcoder-site-header nav.site-navigation > ul.menu > li > a,
body .tmpcoder-site-header nav.site-navigation > div.menu > ul > li > a {
	color: #2b2b2b !important;
}

/* The old "Contact Sales" header strip and its mobile icon-pair replacement
   are both gone now — the chat bubble (further down) covers call/WhatsApp
   on every screen size, so neither is needed any more. */

/* Legacy content classes still baked into page/post content edited under
   him-theme (Services pages, EVS Software, etc.) — a simple Bootstrap-style
   two-column grid, section wrappers, and a click-to-expand FAQ accordion.
   None of these exist in Spexo's own CSS, so without this the content
   rendered as plain unstyled text with visible "+" characters. Values
   below mirror him-theme's assets/css/app.css accordion colors. */
.site-main .row {
	display: flex;
	flex-wrap: wrap;
	margin-left: -15px;
	margin-right: -15px;
}

.site-main .col-md-6 {
	flex: 0 0 50%;
	max-width: 50%;
	padding: 0 15px;
	box-sizing: border-box;
	/* Centers a .col-md-6 used standalone (not paired inside a .columns
	   row, e.g. "Core Offerings"'s lone image) — a no-op when it IS a flex
	   row child, since two 50% items already fill 100% with no space left
	   for auto margins to redistribute. */
	margin: 0 auto;
}

.site-main .col-md-4 {
	flex: 0 0 33.3333%;
	max-width: 33.3333%;
	/* 30px (up from 15px) — EVS Software's image/paragraph rows read too
	   tight with just the base Bootstrap-style gutter. */
	padding: 0 30px;
	box-sizing: border-box;
	margin: 0 auto;
}

/* .col-md-8's missing pair (e.g. EVS Software's "Maintain Transparency"
   dashboard image + paragraph) — without this, an unstyled .col-md-8 falls
   back to a full-width block and stacks above its .col-md-4 sibling
   instead of sitting beside it in the same .row. */
.site-main .col-md-8 {
	flex: 0 0 66.6667%;
	max-width: 66.6667%;
	padding: 0 30px;
	box-sizing: border-box;
}

/* .col-md-12's missing pair too (EVS Software's stacked image-then-text
   rows, class="columns ... himadi-stack" with two col-md-12 children) --
   with no width rule at all, an unstyled div used as a flex item shrinks to
   fit its own content instead of stretching to the row's full width, which
   is why the dashboard/report screenshots rendered small with a lot of
   empty space around them instead of filling the box. */
.site-main .col-md-12 {
	flex: 0 0 100%;
	max-width: 100%;
	box-sizing: border-box;
}

@media (max-width: 767px) {
	.site-main .col-md-6,
	.site-main .col-md-4,
	.site-main .col-md-8 {
		flex-basis: 100%;
		max-width: 100%;
	}

	/* Background Verification's Employment/Personal/Documents rows carry an
	   inline style on the row itself (width:calc(100% + 240px);
	   margin-left/right:-120px; flex-wrap:nowrap) -- a "full-bleed" trick
	   for the wide desktop layout. Nothing overrode it on mobile, so the row
	   stayed nowrap and 240px wider than the screen, squeezing the image
	   and text column into one line instead of stacking them (the image
	   ended up overlapping the first paragraph). !important is required
	   here since a plain class rule can't beat that inline style. */
	.site-main .columns.himadi-card {
		flex-wrap: wrap !important;
		width: 100% !important;
		margin-left: 0 !important;
		margin-right: 0 !important;
	}

	/* Some of these image+text rows have the image column first in the HTML
	   (image, then title+paragraph), others have it second (title+paragraph,
	   then image) -- desktop hides that since they sit side by side either
	   way, but stacked on mobile it means the reading order flips row to
	   row. Force one consistent order everywhere on mobile: title+paragraph
	   first, image last -- regardless of which one comes first in the
	   markup. */
	.site-main .columns.himadi-card .col-md-6:has(.featured-drawing) {
		order: 2;
	}

	.site-main .columns.himadi-card .col-md-6:not(:has(.featured-drawing)) {
		order: 1;
	}
}

.site-main .columns.is-vcentered {
	display: flex;
	flex-wrap: wrap;
	align-items: center;
}

.site-main .featured-drawing {
	max-width: 100%;
	height: auto;
	border-radius: 6px;
}

/* Enlarged legacy image+text cards (Employment Background Verification /
   Personal Background Verification / Documents & Certification Check on
   the Background Verification page) — bigger box, bigger type/image.
   Higher specificity than the two base rules above so it wins without
   !important. */
.site-main .columns.himadi-card {
	padding: 80px;
	box-sizing: border-box;
}

/* EVS Software -- same box-compacting pass as Background Verification's
   page group (reduced padding, capped image width), applied here
   separately since this page was previously excluded from that group
   (it kept the plain white box, not the faded-blue background, but the
   same oversized 80px padding / full-width images still applied). Images
   here are full-width col-md-12 stacked above the text rather than
   beside it, so there's no column-width/gap fix needed like the
   side-by-side pages. */
body.page-id-30 .columns.himadi-card {
	/* Bumped from 24px -> 32px -> 40px per explicit follow-up requests --
	   slightly bigger box, both directions. */
	padding: 40px !important;
}

body.page-id-30 .columns.himadi-card .featured-drawing {
	/* Bumped from 420px -> 500px -> 560px -> 620px -> 680px per
	   explicit follow-up requests -- image size only, box/container
	   width controlled separately below. */
	max-width: 680px;
	margin: 0 auto;
	display: block;
}

/* EVS Software's sections sit in plain .container (same unconstrained
   class the BGC Component accordion had the same problem with) -- no CSS
   anywhere caps its width, so each box ran edge-to-edge with almost no
   side margin. Explicit request for visible white space on both sides,
   widened from 900px -> 980px -> 1060px per follow-up requests. */
body.page-id-30 .site-main .container {
	max-width: 1060px;
	margin-left: auto;
	margin-right: auto;
	padding-left: 20px;
	padding-right: 20px;
	box-sizing: border-box;
}

/* EVS Software's intro paragraph ("Himadi Employee Verification
   System...") -- a direct child of .container, not nested inside a
   .columns.himadi-card box like the other paragraphs on this page, so it
   never picked up any of the font-size rules those get. Matched to the
   same 14px as the SEO/Digital Marketing family's intro paragraph
   (.himadi-dm-page-content > p) per explicit request. The ">" direct-
   child selector is what keeps this from also matching the box
   paragraphs nested deeper inside .columns.himadi-card .col-md-12. */
body.page-id-30 .site-main .container > .col-md-12 p {
	font-size: 14px !important;
}

/* 80px padding on each side eats 160px of a 400px-wide phone screen,
   leaving only 240px for the image/text column that's supposed to fill
   the whole row width -- shrinking the image down to a small thumbnail
   next to the text instead of stacking full-width like the rest of the
   page. */
@media (max-width: 767px) {
	.site-main .columns.himadi-card {
		padding: 30px 20px;
	}
}

/* Same faded-box trial as Home's About Us/Why Choose Us/Industry
   Experience -- applied here to Background Verification, SEO, Content
   Marketing, Social Media Marketing, and Email Marketing per explicit
   request (not the other pages sharing this same .columns.himadi-card
   class, e.g. IT Services/EVS Software/Data Digitization/Security
   Services -- those keep the plain white box). */
body.page-id-22 .columns.himadi-card,
body.page-id-1460 .columns.himadi-card,
body.page-id-1462 .columns.himadi-card,
body.page-id-1464 .columns.himadi-card,
body.page-id-1466 .columns.himadi-card {
	background: #f4f7fc;
}

/* Same box-compacting pass as Home's About Us/Why Choose Us/Industry
   Experience, applied to this same page group -- less padding and a
   capped (not full-column-width) image so the box isn't as tall. Scoped
   to just these 5 page IDs (not the shared .columns.himadi-card class
   itself) so IT Services/EVS Software/Data Digitization/Security
   Services, which also use this class, are unaffected. */
body.page-id-22 .columns.himadi-card,
body.page-id-1460 .columns.himadi-card,
body.page-id-1462 .columns.himadi-card,
body.page-id-1464 .columns.himadi-card,
body.page-id-1466 .columns.himadi-card {
	padding: 30px !important;
	/* These rows carry an inline width:calc(100% + 240px);
	   margin-left/right:-120px "full-bleed" trick in the page content
	   itself (baked into the database, not this stylesheet) -- previously
	   harmless because the 80px padding left enough slack to absorb it,
	   but with padding trimmed to 30px there's no longer room, and the
	   row runs 240px past the container's right edge, clipping text.
	   !important is required to beat that inline style. */
	width: 100% !important;
	margin-left: 0 !important;
	margin-right: 0 !important;
}

/* .col-md-6 fixes each column at exactly 50% of the row regardless of
   the image's own (now much smaller, 320px-capped) size, leaving a big
   empty gap between the image and the text beside it. Shrinking the
   image's column down to its own content width, and letting the text
   column grow to fill what that frees up, is what actually closes the
   gap -- same fix as Home's About Us/Why Choose Us/Industry Experience
   needed for the same reason. */
body.page-id-22 .columns.himadi-card .col-md-6:has(.featured-drawing),
body.page-id-1460 .columns.himadi-card .col-md-6:has(.featured-drawing),
body.page-id-1462 .columns.himadi-card .col-md-6:has(.featured-drawing),
body.page-id-1464 .columns.himadi-card .col-md-6:has(.featured-drawing),
body.page-id-1466 .columns.himadi-card .col-md-6:has(.featured-drawing) {
	flex: 0 0 auto;
	max-width: none;
	width: auto;
}

/* flex-basis 0 (not auto) -- with "auto" the text column first requests
   its own natural/full content width before sharing space, which on
   rows without an explicit flex-wrap:nowrap (e.g. SEO's "The Long Game"
   row, which only gets its flex behavior from .columns.is-vcentered's
   default flex-wrap:wrap) was overflowing and wrapping the image column
   onto its own line below the text instead of staying beside it. "0" has
   the text column share only the space actually left over, and the
   explicit nowrap below removes the wrap option entirely as a second
   safety net. */
body.page-id-22 .columns.himadi-card .col-md-6:not(:has(.featured-drawing)),
body.page-id-1460 .columns.himadi-card .col-md-6:not(:has(.featured-drawing)),
body.page-id-1462 .columns.himadi-card .col-md-6:not(:has(.featured-drawing)),
body.page-id-1464 .columns.himadi-card .col-md-6:not(:has(.featured-drawing)),
body.page-id-1466 .columns.himadi-card .col-md-6:not(:has(.featured-drawing)) {
	flex: 1 1 0%;
	max-width: none;
}

@media (min-width: 768px) {
	body.page-id-22 .columns.himadi-card,
	body.page-id-1460 .columns.himadi-card,
	body.page-id-1462 .columns.himadi-card,
	body.page-id-1464 .columns.himadi-card,
	body.page-id-1466 .columns.himadi-card {
		flex-wrap: nowrap !important;
	}
}

body.page-id-22 .columns.himadi-card .featured-drawing,
body.page-id-1460 .columns.himadi-card .featured-drawing,
body.page-id-1462 .columns.himadi-card .featured-drawing,
body.page-id-1464 .columns.himadi-card .featured-drawing,
body.page-id-1466 .columns.himadi-card .featured-drawing {
	/* width:100% (fixed px here instead) was ambiguous now that its
	   column is auto/shrink-to-fit rather than a fixed 50% -- 100% of an
	   auto-width parent isn't well-defined, so pinning this to the same
	   320px directly avoids relying on that. */
	width: 320px;
	max-width: 100%;
}

.site-main .columns.himadi-card .featured-drawing {
	/* max-width:100% alone only ever caps the image at its native pixel
	   size (this JPG is ~380px wide) — it never stretches it to fill the
	   wider column, which is why removing the old fixed height:300px
	   wasn't enough to make it look bigger on its own. */
	width: 100%;
}

/* Stand-in for a not-yet-supplied image in a .col-md-6 image slot (SEO
   page's 4 boxes) — same 1:1 footprint the real .featured-drawing images
   on the Background Verification page render at (they're natively
   380x380 squares scaled to width:100%), so swapping in a real <img
   class="featured-drawing"> later needs no layout changes. */
.himadi-image-placeholder {
	width: 100%;
	aspect-ratio: 1 / 1;
	background: #eef0f2;
	border-radius: 6px;
}

/* Explicit request to reduce font size across all these shared
   .himadi-card boxes (Background Verification, EVS Software,
   SEO/Content/Social/Email Marketing), matching the same treatment
   already applied to Home's About Us/Why Choose Us/Industry
   Experience boxes. */
.site-main .columns.himadi-card .heading3 {
	font-size: 22px;
	line-height: 1.3;
	margin-bottom: 10px;
}

/* Matches the plain (no-box) intro paragraph above these boxes on the same
   pages (e.g. Background Verification's intro: inline font-size:17px;
   color:#555) -- box text was rendering at 18px with no color set (falling
   back to the theme's default text color, not #555), a visible mismatch
   between the box copy and the paragraph right above it. Applies to every
   .himadi-card box across all these pages (Background Verification, EVS
   Software, SEO/Content/Social/Email Marketing), since they all share this
   one class. Bullet lists inside these same boxes (e.g. Background
   Verification's "Documents & Certification Check" industries list,
   Content Marketing's bullet list) were rendering even smaller still —
   14px, color #777, from the theme's own default list styling — so they're
   matched to the exact same 17px/#555 here too. */
.site-main .columns.himadi-card p,
.site-main .columns.himadi-card li {
	font-size: 14px;
	color: #555;
	line-height: 1.5;
}

/* "Core Offerings" image+list row -- the image (now 320px, see
   body.page-id-24 img.featured-drawing above) sits inside a 50%-wide
   .col-md-6 (~600px), left-aligned by default (plain inline <img>), which
   left a wide blank strip between the image's own right edge and the list
   column beside it. Pushing the image column's content to the right (flex
   + justify-content:flex-end) and pulling the list column's left padding
   in closes that gap from both sides. */
/* "Core Offerings" heading -- inline font-size:32px in the page content
   itself, reduced by 3px per explicit request. :has() targets the specific
   h2 immediately before this row (no other unique hook on the heading
   itself) rather than every h2 on the page. */
.site-main h2:has(+ .row .himadi-core-offerings-list) {
	font-size: 29px !important;
}

/* "Why Choose Our IT Services" heading -- inline font-size:28px, reduced
   by 3px too per explicit follow-up request. :has() targets the specific
   h2 immediately before the IT-services card grid. */
.site-main h2:has(+ .himadi-card-grid-3) {
	font-size: 25px !important;
}

.site-main .row:has(.himadi-core-offerings-list) {
	/* Shifts the whole image+list row left, closer to the page's left
	   edge, per explicit request. */
	margin-left: -95px;
}

.site-main .row:has(.himadi-core-offerings-list) .col-md-6:has(.featured-drawing) {
	display: flex;
	justify-content: flex-end;
}

/* Nudges the image itself slightly left, off the column's own right edge,
   per explicit follow-up request. */
body.page-id-24 img.featured-drawing {
	margin-right: 40px;
}

.site-main .col-md-6.himadi-core-offerings-list {
	padding-left: 0;
}

/* IT Services' "Core Offerings" list — same 17px/#555 as everywhere else,
   matched to Background Verification's plain paragraph style per request.
   Not a .himadi-card box like the ones above, just a plain Bootstrap-style
   .row/.col-md-6 pair, so it needs its own rule; the <b>/<u> service-name
   labels inherit color from the browser default (black) rather than from
   the surrounding <li>, so they're targeted explicitly too. */
.site-main .himadi-core-offerings-list li,
.site-main .himadi-core-offerings-list li b,
.site-main .himadi-core-offerings-list li u {
	font-size: 14px;
	color: #555;
	line-height: 1.4;
}

/* Compacting the list itself -- the content's own inline padding-left:20px
   (doubled, since each <li> wraps a nested <ul>) and the browser's default
   per-<li> margin were the main source of the "very big" look, not just
   the font-size above. !important needed to beat that inline padding. */
.site-main .himadi-core-offerings-list ul {
	padding-left: 18px !important;
	margin: 0;
}

.site-main .himadi-core-offerings-list li {
	margin-bottom: 4px;
}

/* "Read More" toggle (assets/js/himadi-readmore.js) — tried first on the
   SEO page's first box, which ran to two long paragraphs. Collapsed state
   clips to a fixed height with a fade-out at the bottom so it still reads
   as a normal, evenly-sized box; expanding removes the height cap and the
   fade. White fade matches the page's plain white background behind these
   boxes — would need a different fade color if reused on a box sitting on
   a tinted background. */
.himadi-readmore-content {
	max-height: 280px;
	overflow: hidden;
	position: relative;
	transition: max-height 400ms ease;
}

.himadi-readmore-content::after {
	content: '';
	position: absolute;
	left: 0;
	right: 0;
	bottom: 0;
	height: 40px;
	background: linear-gradient(to bottom, rgba(255, 255, 255, 0), #fff);
	transition: opacity 200ms ease;
}

.himadi-readmore.is-expanded .himadi-readmore-content {
	max-height: 1000px;
}

.himadi-readmore.is-expanded .himadi-readmore-content::after {
	opacity: 0;
}

/* Pins the toggle to the bottom of the box (level with the image on the
   other side of the row) instead of sitting right under the text, however
   short the collapsed text happens to be — the column stretches to the
   row's full height (overriding is-vcentered's align-items:center, which
   would otherwise center this column's own short content and leave no
   room to push anything to a "bottom"), the read-more wrapper fills that
   full height, and margin-top:auto on the toggle's flex item claims all
   the leftover space above itself. That flex item is the <p> wpautop
   wraps around the lone <button> tag in the saved post content — not the
   button itself — since wpautop auto-wraps bare inline content it finds
   sitting directly inside a block-level element; margin-top:auto has to
   land on that actual flex child or it's a no-op. */
.site-main .columns.himadi-card .col-md-6:has(.himadi-readmore) {
	align-self: stretch;
	display: flex;
	flex-direction: column;
}

.himadi-readmore {
	display: flex;
	flex-direction: column;
	flex: 1;
}

.himadi-readmore > p {
	margin-top: auto;
	margin-bottom: 0;
}

.himadi-readmore-toggle {
	display: inline-block;
	padding-top: 16px;
	background: none;
	border: none;
	padding-left: 0;
	padding-right: 0;
	padding-bottom: 0;
	color: #2563eb;
	font-weight: 600;
	font-size: 15px;
	cursor: pointer;
}

.himadi-readmore-toggle:hover {
	text-decoration: underline;
}

/* Social Media Marketing's "Targeted Advertising and Influencer
   Partnerships" row: its image and paragraph happen to be almost exactly
   the same height, so is-vcentered's align-items:center has nothing to
   visibly center -- the heading sits flush with the image top, while
   every other box on the page (image and text noticeably different
   heights) shows the usual small vertical offset. Nudging this one down a
   bit makes it match that same centered look. */
.himadi-nudge-down {
	margin-top: 28px;
}

/* EVS Software's rows originally paired a short/wide image against several
   paragraphs of text in a narrow side-by-side column, which made the box
   balloon in height around a comparatively small-looking image, reading as
   a near-square block instead of a wide rectangle. Cut the base padding
   down for this page. */
.page-template-template-evs-software .columns.himadi-card {
	padding: 40px 50px;
	/* Off-white, per request -- before that a transparent blue tint
	   (rgba(37, 99, 235, 0.08), the same formula as the Contact Us form's
	   input focus glow), and before that flat #f4f7fc like the other pages. */
	background: #fbfaf8;
}

/* Every image+text row on EVS Software (Maintain Transparency, Dashboard –
   Faster Delivery, Deliver Values Fast, Candidate Registration Options x2,
   Report Generation) now stacks image on top, paragraph below, both full
   width, instead of side-by-side with the text squeezed into a narrow
   column that wrapped into a tall vertical stack of short lines — running
   the same text the full box width turns it into a couple of wide
   horizontal lines instead, which is what keeps the box's height down.
   These rows deliberately dropped "is-vcentered" from their class list, so
   they're no longer flex at all — their two .col-md-12 children just stack
   as plain blocks, in source order (image, then paragraph). */
/* !important -- some of these text columns carry their OWN inline
   margin-top percentage (e.g. "Deliver Values Fast": style="margin-
   top:4%") that otherwise wins over this plain class rule regardless of
   the fixed 24px intended here. */
.himadi-stack .col-md-12 + .col-md-12 {
	margin-top: 24px !important;
}

/* The paragraphs themselves carry inline margin-top percentages (2%, 4%,
   15%, varying per section, baked into the page content) on top of the
   24px above -- on a percentage basis that's a big, inconsistent gap
   (15% of a 900px-wide box is ~135px). !important is required to
   override that inline style from here instead of editing the content
   directly. */
.himadi-stack .col-md-12 + .col-md-12 p {
	margin-top: 0 !important;
}

/* "Deliver Values Fast" also has three literal <br><br><br> tags baked
   into the page content before its paragraph, adding roughly 3 blank
   line-heights' worth of extra gap on top of the margin above -- collapse
   them to zero height rather than editing the content directly. */
.himadi-stack .col-md-12 br {
	display: block;
	content: "";
	margin: 0;
	line-height: 0;
}

.site-main .heading3 {
	font-size: 22px;
	font-weight: 600;
	margin-top: 0;
}

.site-main .content-wrapper {
	padding: 20px 0;
}

/* Legacy content wraps each block ("Maintain Transparency", "Dashboard –
   Faster Delivery", etc.) in <section class="section is-medium">, but
   neither Spexo nor this file ever gave that class any spacing — sections
   were butting straight up against each other with zero gap. */
.site-main .section {
	padding: 40px 0;
}

/* Background Verification specifically — its 4 image+text boxes (each
   wrapped in one of these .section elements) were reading with a lot of
   white space both before the first box and between each one, since this
   40px padding stacks with the next section's own 40px top padding
   (~80px+ of pure gap) on top of the boxes' own small inline
   margin-bottom. Scoped to this template rather than changing the
   padding sitewide, where other pages rely on the taller spacing. */
.page-template-template-services .site-main .section {
	padding: 15px 0;
}

/* Sub-heading labels in legacy content (e.g. "Cost Efficiency" under "Why
   Choose Our IT Services") — bold, but lighter than the h2 above them. */
.site-main h4 {
	font-weight: 600;
}

/* BGC Component accordion (Background Verification page) -- no CSS
   anywhere actually constrains plain .container's width, so the
   accordion grid ran nearly edge-to-edge of the page with very little
   side margin. Explicit request for more left/right white space. */
.BGC_Component_tab > .container {
	padding-left: 60px;
	padding-right: 60px;
	box-sizing: border-box;
}

.BGC_Component_tab > .container > .apply_online_carrer > .row > h1 {
	text-align: center;
	/* Explicit request to make the whole BGC Component section (title +
	   every accordion item below) more compact -- scoped to this exact
	   selector so it doesn't touch the h1/page-title size used elsewhere
	   on the site. */
	font-size: 32px !important;
}

/* Card treatment with a brand accent bar — trying to bring back some of the
   presence the original him-theme version of this component had (a solid
   dark-maroon #610e15 block per row, white text) without going back to a
   full solid block, which read as too heavy/dated next to the rest of this
   page's light styling. Instead: a white card, spaced out with a visible
   shadow instead of a plain border, and a colored left edge so each row
   still reads as clearly "branded" and distinct rather than blending into a
   plain pastel list (the previous near-white background trials — up
   through #fffefb — had faded to the point of barely being visible as
   separate rows at all). Accent color trying #007FFF (Azure) per request --
   before that #0cafff, #4d4dff, Spexo's own actual theme blue/purple
   (--theme-primary-color: #5729d9), and the maroon (#610e15) first tried
   here. Easy to revert: this whole rule block replaces the flat
   pastel-list version that was here before, if this doesn't work out. */
/* Padding/margin trimmed and the heading/icon below shrunk -- explicit
   request to make the whole BGC Component accordion (every item) more
   compact, not just the section title. */
.site-main .accordion {
	background-color: #fff;
	border: none;
	border-left: 5px solid #007fff;
	overflow: hidden;
	color: #2b2b2b;
	padding: 10px 16px;
	cursor: pointer;
	display: flex;
	align-items: center;
	justify-content: space-between;
	border-radius: 6px;
	margin-bottom: 6px;
	box-shadow: 0 2px 10px rgba(0, 0, 0, 0.07);
	transition: box-shadow 150ms ease, border-left-color 150ms ease;
}

.site-main .accordion:hover {
	border-left-color: #0063cc;
	box-shadow: 0 4px 16px rgba(0, 0, 0, 0.12);
}

.site-main .accordion:hover h2 {
	color: #007fff;
}

.site-main .accordion.active {
	border-left-color: #0063cc;
	border-radius: 6px 6px 0 0;
}

.site-main .accordion h2 {
	text-transform: capitalize;
	display: inline-block;
	font-size: 15px;
	line-height: 1.3;
	margin: 0;
	font-weight: 600;
	color: inherit;
	transition: color 150ms ease;
}

.site-main .accordion .icon {
	flex: 0 0 auto;
	background: #dff0ff;
	color: #007fff;
	cursor: pointer;
	width: 24px;
	height: 24px;
	text-align: center;
	line-height: 22px;
	border-radius: 50%;
	font-size: 16px;
	margin-left: 12px;
	transition: background-color 150ms ease, color 150ms ease;
}

.site-main .accordion.active .icon {
	background-color: #007fff;
	color: #fff;
}

/* "BGC Component" (Background Verification page) wraps its two-column
   accordion grid in #acc_tab_hmdf, itself a flex item of the outer .row
   alongside the "BGC Component" <h1>. As a flex item it defaults to
   shrink-to-fit instead of filling the row, so its .col-md-6 children's
   50% widths were computing against that too-small width — the whole grid
   rendered narrower than the page container and sat left-aligned with a
   large empty gap on the right instead of spanning/centering properly. */
#acc_tab_hmdf {
	flex: 1 1 100%;
	width: 100%;
}

/* Sits directly under its .accordion header once expanded -- pulled up to
   touch it (negative margin) and given the same accent-colored left edge +
   white card shadow, with square top corners so the two read as one
   continuous card instead of two separate boxes with a visible gap between
   them.

   Scoped to #acc_tab_hmdf (the BGC Component's own wrapper) rather than
   the previous ".site-main .text" -- Contact Form 7 gives every text
   input a plain "text" class too (class="wpcf7-form-control wpcf7-text ...
   text"), so the old broad selector was also matching every text/email/tel
   field in the "Get Started With Himadi" form on every page and painting
   them this same light-blue background. */
/* #himadi-career-openings (Career page's "Current Openings" accordion,
   himadi_render_career_openings()) shares this same expanded-panel look --
   same .accordion/.text markup pattern, just a different wrapper id. */
#acc_tab_hmdf .text,
#himadi-career-openings .text {
	margin: -10px 0 10px;
	font-size: 15px;
	display: none;
	background-color: #eaf4ff;
	border-left: 5px solid #007fff;
	padding: 16px 20px;
	letter-spacing: 0.3px;
	border-radius: 0 0 6px 6px;
	box-shadow: 0 4px 16px rgba(0, 0, 0, 0.12);
}

#acc_tab_hmdf .text p,
#himadi-career-openings .text p {
	margin: 0;
}

#himadi-career-openings .text {
	line-height: 1.7;
}

#himadi-career-openings .text h4 {
	margin: 22px 0 10px;
	font-size: 15px;
	font-weight: 700;
	color: #1e2b4d;
}

#himadi-career-openings .text h4:first-child {
	margin-top: 0;
}

#himadi-career-openings .text ul {
	margin: 0 0 14px;
	padding-left: 20px;
}

#himadi-career-openings .text li {
	margin-bottom: 10px;
}

#himadi-career-openings .text li ul {
	margin-top: 10px;
}

/* "Our Journey" ascending staircase timeline (About page) — per an exact
   reference design supplied by the client's SEO consultant (5 steps
   rising left-to-right, connected by a single straight dashed line, each
   step's content — square dot, year, blue pill label, description —
   anchored below its dot). Built as real HTML/CSS/SVG rather than
   embedding the reference as an image, so text stays selectable/editable
   and on-brand. The 5 dot positions are evenly spaced in both x and y
   (10/30/50/70/90% across), which is what makes them collinear — a
   single <line> connects all 5 exactly, no polyline/per-segment math
   needed. */
.himadi-journey-section {
	/* Off-white, but a cooler/grayer tone than the Testimonials section's
	   #f6f5f2 (warmer) — deliberately different, not reused, per explicit
	   request. */
	background-color: #f4f6f8;
}
.himadi-journey-title {
	text-align: center;
	color: #2563eb;
	font-size: 50px;
	font-weight: 800;
	text-transform: uppercase;
	margin: 0;
}

.himadi-journey-subtitle {
	text-align: center;
	color: #1e2b4d;
	font-size: 20px;
	font-weight: 700;
	text-transform: uppercase;
	margin: 8px 0 0;
}

.himadi-journey {
	position: relative;
	/* Every dot/line coordinate below is a percentage of this height, so
	   shrinking it compresses the whole diagram proportionally (steeper
	   line, less vertical space) rather than shifting any point out of
	   place — a small reduction from 460px per request. */
	height: 410px;
	margin-top: 60px;
	margin-bottom: 20px;
}

.himadi-journey-line {
	position: absolute;
	inset: 0;
	width: 100%;
	height: 100%;
}

.himadi-journey-line line {
	stroke: #2563eb;
	stroke-width: 3;
	stroke-dasharray: 10 8;
}

.himadi-journey-step {
	position: absolute;
	transform: translateX(-50%);
	width: 220px;
	text-align: center;
}

/* Each step now rises in two separate phases instead of one:
   .himadi-journey-step-box (dot+year+badge) and .himadi-journey-desc (the
   paragraph) both use this same rise-from-bottom animation, but on
   different delay schedules below — every step's BOX appears first, in
   chronological order (2012, then 2018, then 2023, then 2025, then 2026,
   one clearly after another), and only once all 5 boxes have finished
   does the text phase begin, itself staggered the same way. Previously
   both were one combined element revealing together with only a small
   150ms gap between steps, which read as "everything together" rather
   than a boxes-then-text sequence. */
.himadi-journey-rise {
	animation: himadi-journey-rise-kf 700ms ease-out both;
	animation-play-state: paused;
}

@keyframes himadi-journey-rise-kf {
	from {
		opacity: 0;
		transform: translateY(40px);
	}
	to {
		opacity: 1;
		transform: translateY(0);
	}
}

/* nth-of-type, not nth-child: .himadi-journey-line (the SVG) is the
   actual first child of .himadi-journey, which shifted a plain nth-child
   count off by one and left the last step (2026) with no delay at all. */
.himadi-journey-step:nth-of-type(1) .himadi-journey-step-box {
	animation-delay: 0ms;
}

.himadi-journey-step:nth-of-type(2) .himadi-journey-step-box {
	animation-delay: 400ms;
}

.himadi-journey-step:nth-of-type(3) .himadi-journey-step-box {
	animation-delay: 800ms;
}

.himadi-journey-step:nth-of-type(4) .himadi-journey-step-box {
	animation-delay: 1200ms;
}

.himadi-journey-step:nth-of-type(5) .himadi-journey-step-box {
	animation-delay: 1600ms;
}

/* Each step's text now follows right after its OWN box (box delay + 350ms,
   a short natural gap) instead of waiting for every box in the whole
   sequence to finish first — that old wait-for-all-boxes approach left the
   later years' text appearing up to ~4s after their box, reading as stuck
   or delayed. */
.himadi-journey-step:nth-of-type(1) .himadi-journey-desc {
	animation-delay: 350ms;
}

.himadi-journey-step:nth-of-type(2) .himadi-journey-desc {
	animation-delay: 750ms;
}

.himadi-journey-step:nth-of-type(3) .himadi-journey-desc {
	animation-delay: 1150ms;
}

.himadi-journey-step:nth-of-type(4) .himadi-journey-desc {
	animation-delay: 1550ms;
}

.himadi-journey-step:nth-of-type(5) .himadi-journey-desc {
	animation-delay: 1950ms;
}

.himadi-journey-dot {
	display: block;
	width: 14px;
	height: 14px;
	margin: 0 auto 14px;
	background: #2563eb;
}

.himadi-journey-year {
	display: block;
	color: #1e2b4d;
	font-size: 22px;
	font-weight: 800;
	margin-bottom: 8px;
}

.himadi-journey-badge {
	display: inline-block;
	background: #2563eb;
	color: #fff;
	font-weight: 700;
	font-size: 13px;
	letter-spacing: 0.5px;
	text-transform: uppercase;
	padding: 8px 20px;
	border-radius: 20px;
	margin-bottom: 14px;
}

.himadi-journey-step p {
	margin: 0;
	color: #37415c;
	font-size: 14px;
	line-height: 1.6;
}

@media (max-width: 900px) {
	.himadi-journey {
		height: auto;
	}

	.himadi-journey-line {
		display: none;
	}

	.himadi-journey-step {
		position: static;
		transform: none;
		width: 100%;
		margin-bottom: 36px;
	}

	.himadi-journey-step:last-child {
		margin-bottom: 0;
	}
}

/* Vision/Mission/Values section (template-about.php) -- replaces the
   default x-large (~56px) top/bottom padding with a smaller fixed value,
   shortening the section's vertical length per request. */
.himadi-vmv-section {
	padding-top: 28px;
	padding-bottom: 28px;
}

/* Vision / Mission / Values — only the icon turns around on hover, the
   heading and text stay put (unlike the front/back flip cards elsewhere). */
.himadi-vmv-icon {
	transition: transform 600ms;
}

.wp-block-column:hover > .himadi-vmv-icon {
	transform: rotateY(360deg);
}

.himadi-icon-circle {
	width: 90px;
	height: 90px;
	border-radius: 50%;
	background: rgba(255, 255, 255, 0.12);
	display: flex;
	align-items: center;
	justify-content: center;
	margin: 0 auto 16px;
}

.himadi-icon-circle img {
	max-width: 40px;
	max-height: 40px;
}

.himadi-icon-circle.is-light {
	background: var(--theme-background-color, #f3f3f3);
}

/* Why Choose Us / Industry Experience photos (choose.jpg, industry.jpg) ran
   a bit dark/moody compared to About Us's photo -- lightened just these
   two, not About Us, since only these two were flagged. */
body.home .himadi-fill-image img[src*="choose.jpg"],
body.home .himadi-fill-image img[src*="industry.jpg"] {
	filter: brightness(1.15);
}

/* Fill-width feature images (About / Why Choose Us columns etc.) instead of
   rendering at their small natural size inside a much wider column. */
.himadi-fill-image img {
	/* Width stays fixed at the Background Verification page's own image
	   width (520px); height is stretched taller instead of following the
	   photo's native ratio. Same fixed width AND height on all three
	   (About Us / Why Choose Us / Industry Experience) so every box is the
	   exact same size -- they all share this one rule, nothing per-box. */
	width: 520px;
	max-width: 100%;
	height: 460px;
	object-fit: fill;
	border-radius: 10px;
}

.himadi-fill-image {
	border-radius: 10px;
}

/* About Us box specifically -- explicit request to reduce its overall
   height. Measured directly (pixel boundary of the card background):
   narrowing the row's own max-width to 1100px made it TALLER, not
   shorter -- 844px vs the original 785px -- because the text column lost
   width and its 4 paragraphs wrapped onto more lines than before. Kept at
   the shared container width instead (more room for the text column),
   with just the photo shrunk, which is what actually reduces the row's
   height. */
/* Shrunk further (420x360 -> 260x230) and switched fill to cover --
   explicit request to reduce the box's width too, without reducing
   content or re-wrapping the paragraphs onto more lines (which is what
   happened the first time the row's own max-width was narrowed). The
   text column below is pinned to its current natural width (flex: 0 0
   650px) so it neither grows into the space this frees up nor shrinks
   and re-wraps -- all of the savings come out of the image alone,
   shrinking the row's total width with no height side effect. object-fit
   switched from fill to cover so the smaller box doesn't stretch/distort
   the photo the way a fixed, non-matching width/height would. */
/* Sized to match the SEO/Digital-Marketing page's .featured-drawing
   images exactly (verified via computed style: 320x320px), per explicit
   request -- applies to all three (About Us / Why Choose Us / Industry
   Experience), same as before. */
.himadi-about-box .himadi-fill-image img {
	width: 320px;
	height: 320px;
	object-fit: cover;
}

/* Was a fixed flex:0 0 650px, sized for when the image beside it was
   260px wide -- the image has since been bumped to 320px (matching the
   SEO page's photos) without this being updated, so the fixed 650px text
   column no longer fit in the row's remaining width and was overflowing
   past the box's right edge (clipped once overflow:hidden was added to
   .himadi-about-box to fix a separate issue). flex:1 instead of a fixed
   pixel width means it always fills whatever space is actually left next
   to the image, regardless of the image's own size. */
.himadi-about-box > .wp-block-column:not(:has(.himadi-fill-image)) {
	flex: 1 1 0;
	min-width: 0;
}

/* The row itself defaults to filling 100% of .himadi-container regardless
   of how small its children are (Gutenberg core's own .wp-block-columns
   width:100%), so shrinking the image/text above alone just left empty
   space in the middle instead of actually shrinking the box -- capping
   the row's own max-width to roughly image + gap + text + the card's own
   left/right padding is what makes it hug its (now smaller) content.

   margin auto: on the About Us row this class sits directly on the
   .himadi-container itself, which already centers via its own margin:0
   auto -- but Why Choose Us / Industry Experience put this class on the
   .wp-block-columns row NESTED inside a separate .himadi-container
   wrapper, which has no self-centering of its own. Without this, those
   two rows default to the box model's normal left-alignment inside their
   parent, landing 100px further left than the About Us row above them
   (confirmed by measuring left/right edges directly) instead of lining
   up with it. */
.himadi-about-box {
	max-width: 1040px;
	margin-left: auto;
	margin-right: auto;
	/* Without this, text near the bottom-right corner can render past the
	   box's own rounded corner (border-radius doesn't clip children on its
	   own) -- most visible on the Industry Experience box, where the last
	   line of the (collapsed, read-more'd) paragraph sat partly outside the
	   rounded white card. Clips all child content to the box's own shape. */
	overflow: hidden;
}

/* !important -- same specificity-tie cause as the heading-size fix
   above: .himadi-card's own padding:40px (defined later in this file) is
   equal specificity to this single-class selector, so without
   !important it would win regardless of this rule existing. */
.himadi-about-box {
	padding-top: 0 !important;
	/* Matches the SEO page box group's 30px padding, so there's visible
	   white space below the content before the box background ends,
	   same as that page -- the earlier 0 here removed it entirely. */
	padding-bottom: 30px !important;
}

/* Matched to the exact same size as the SEO page's .himadi-card boxes
   (.heading3 at 22px, paragraphs at 14px) per explicit request, same
   reasoning as the Digital Marketing intro text earlier -- the standalone
   reductions tried first (26px/13px) were a mismatch with the rest of the
   site's boxes rather than a deliberate size.

   !important -- confirmed via devtools computed value (17px, not 14px)
   that an older, unrelated rule -- .himadi-card p { font-size:17px }
   below, from matching Background Verification's inline 17px copy before
   any of this box-compacting work started -- has equal specificity to
   this plain "p" selector and is defined later in the file, so it was
   winning the tie regardless of this rule's intent. */
/* SEO page's .columns.himadi-card p has no margin-bottom override at
   all, so its paragraph gap is just the browser default UA margin for
   <p> (1em of its own 14px font-size = 14px). The earlier 4px value
   here was an undershoot of that -- it killed the visible white gap
   between paragraphs instead of matching it. 14px matches it exactly. */
.himadi-about-box p {
	line-height: 1.5 !important;
	margin-bottom: 14px !important;
	font-size: 14px !important;
}

/* Matching SEO's .heading3 style exactly, not just its font-size -- the
   vendor's default h2 styling pulls font-family/weight/letter-spacing/
   text-transform from the --heading2-* custom properties, while .heading3
   (a theme-custom class, not a real h3 default) only ever sets font-size
   and font-weight, inheriting everything else from the page's plain body
   font. Forcing all of these explicitly here, rather than relying on the
   --heading2-* vars resolving to the same values, is what actually
   guarantees an identical look rather than just an identical font-size. */
.himadi-about-box h2.wp-block-heading {
	font-size: 22px !important;
	font-family: inherit !important;
	font-weight: 600 !important;
	letter-spacing: normal !important;
	text-transform: none !important;
	line-height: 1.3 !important;
}

/* "About Us" / "Why Choose Us" / "Our Industry Experience" eyebrow label
   above the heading -- shares .himadi-eyebrow (22px) with every other
   section label site-wide, which SEO's boxes don't have at all (just a
   single h3, no label above it). Shrinking it here is what actually
   closes the remaining visual size gap against SEO's boxes, since the
   22px label stacked above an already-22px heading still reads as a
   bigger combined block than SEO's single heading alone. */
.himadi-about-box .himadi-eyebrow,
.wp-block-column.himadi-tight-text > .himadi-eyebrow {
	font-size: 14px !important;
	margin-bottom: 4px;
}

.himadi-about-box .wp-block-buttons {
	margin-top: 0;
}

/* About Us / Why Choose Us / Industry Experience (Home page) -- these
   columns had no gap at all between the image and the text beside it, so
   the image's right edge ran right up against the heading/paragraph with
   almost no breathing room. Real fix is spacing between the columns, not
   the image's own height (tried that first -- reverted above -- it
   didn't touch the actual problem). */
body.home .wp-block-columns.himadi-card {
	gap: 48px;
	/* Trial: soft faded tint instead of plain white, so the box reads as
	   its own card against the page background and gives the dark
	   paragraph text a little more contrast to sit on. Easy to drop this
	   line to go back to the plain white .himadi-card default. */
	background: #f4f7fc;
}

/* The image no longer fills its whole 50%-wide column (it's fixed at
   520px now), so the column's own leftover width was adding a second,
   much bigger gap in front of the gap above -- the text column still
   started at the 50% mark instead of right after the actual photo. Shrink
   the image's column down to the image's own size so the text starts
   right after it. */
body.home .wp-block-columns.himadi-card > .wp-block-column:has(.himadi-fill-image) {
	flex: 0 0 auto;
	width: auto;
}

@media (max-width: 767px) {
	.himadi-fill-image,
	.himadi-fill-image img {
		height: 300px;
	}

	/* Same fix as Background Verification's rows: About Us/Industry
	   Experience have the image column first in the HTML, Why Choose Us has
	   it second -- side by side on desktop that's invisible, but stacked on
	   mobile the order flips row to row. Force one consistent order: title
	   and paragraph first, image last, on every row. */
	body.home .wp-block-columns.himadi-card > .wp-block-column:has(.himadi-fill-image) {
		order: 2;
	}

	body.home .wp-block-columns.himadi-card > .wp-block-column:not(:has(.himadi-fill-image)) {
		order: 1;
	}
}

.himadi-checklist {
	list-style: none;
	margin: 20px 0;
	padding: 0;
}

.himadi-checklist li {
	display: flex;
	align-items: flex-start;
	gap: 10px;
	margin-bottom: 12px;
}

.himadi-checklist svg {
	flex: 0 0 auto;
	width: 18px;
	height: 18px;
	margin-top: 3px;
	color: var(--theme-accent-color, #2e9e3f);
}

/* Compact pill list for a long flat set of short items (e.g. Background
   Verification's 14 check types) — a .himadi-checklist reads fine for a
   handful of items with real descriptions, but turns into a very tall wall
   of near-identical rows once there are a dozen-plus one- or two-word ones;
   pills let them sit compactly instead. */
.himadi-tag-list {
	display: flex;
	flex-wrap: wrap;
	gap: 10px;
	list-style: none;
	margin: 20px 0;
	padding: 0;
}

.himadi-tag-list li {
	background: var(--theme-background-color, #f3f3f3);
	border: 1px solid var(--theme-global-border-color, #ddd);
	color: var(--theme-primary-color, #610e15);
	font-size: 14px;
	font-weight: 600;
	padding: 8px 16px;
	border-radius: 999px;
}

.himadi-eyebrow {
	display: block;
	text-align: center;
	text-transform: uppercase;
	letter-spacing: 2px;
	font-size: 22px;
	font-weight: 700;
	color: #2563eb;
	margin-bottom: 8px;
}

/* Trying blue section headings on Simple Process / Why Choose Us. */
.himadi-heading-blue {
	color: #2563eb;
}

/* Home's "Our Services" eyebrow/heading only -- 1px smaller than the
   shared .himadi-eyebrow (22px) and the theme's default h2 size, per
   explicit request scoped to just this section, not every eyebrow/h2
   on the page. */
.himadi-services-eyebrow {
	font-size: 21px;
}

.himadi-services-heading.wp-block-heading {
	font-size: calc(var(--heading2-font-size, 40px) - 1px) !important;
}

/* "Our Services"/"What We Do?" (Home) only -- the shared
   .himadi-services-eyebrow/.himadi-services-heading classes above are
   also used by "The Simple Process", "Latest From The Blog" and "Get
   Started With Himadi", so reducing those directly would shrink all of
   them; these two extra classes (added in template-home.php) scope the
   3px reduction to just this one heading pair. */
.himadi-our-services-eyebrow {
	font-size: 18px;
}

.himadi-our-services-title.wp-block-heading {
	font-size: calc(34.6px - 3px) !important;
}

/* White card wrapper (rounded corners + soft shadow), matching the
   reference's card treatment — used for About Us / Why Choose Us. */
.himadi-card {
	background: #fff;
	border-radius: 10px;
	box-shadow: 0 4px 20px rgba(0, 0, 0, 0.08);
	padding: 40px;
}

/* Match the body-copy size used on Background Verification / About Us
   (those paragraphs carry an explicit inline font-size:17px) — Home's About
   Us / Why Choose Us / Industry Experience paragraphs had no override and
   fell back to the theme's small 14px base, reading noticeably smaller. */
.himadi-card p {
	font-size: 17px;
	line-height: 1.7;
}

/* EVS Software's body copy is raw legacy post_content (the_content() in
   template-evs-software.php, not theme markup), so it has no font-size of
   its own and fell back to the same too-small 14px base as Home's About Us
   text did — matching that same 17px fix here. */
.page-template-template-evs-software .page-content p {
	font-size: 17px;
	line-height: 1.7;
}

/* WordPress core's block-library CSS (wp-includes/blocks/columns/style.css)
   sets .wp-block-columns { align-items: initial !important }, which silently
   wins over both an inline align-items style and core's own
   .are-vertically-aligned-center class — so the verticalAlignment:"center"
   noted in the wp:columns block comments (About Us / Why Choose Us / Our
   Industry Experience) never actually took effect and the shorter text
   column stayed pinned to the top next to the taller image. Only
   !important here can beat !important there. */
.himadi-card.wp-block-columns {
	align-items: center !important;
}


/* Fixed 3-column grid for .himadi-service-card sets ("Why Choose Our IT
   Services", etc.) that need a guaranteed N-per-row layout. Deliberately
   NOT wp-block-columns/wp-block-column: WordPress core's block-library CSS
   forces .wp-block-columns to flex-wrap:nowrap!important above 782px width
   (real Columns blocks are fixed-row, not a wrapping grid), which no inline
   style can override — that's what squeezed all 6 IT-services cards into
   one overflowing row instead of wrapping into two. */
.himadi-card-grid-3 {
	display: grid;
	/* First brought down from 1fr/300px to 340x275 to match the Simple
	   Process / Home "What We Do?" cards -- still read as too big on this
	   specific 6-card grid, so shrunk further here (340->260, 275->210)
	   per explicit follow-up request, just for this grid. */
	grid-template-columns: repeat(3, 260px);
	justify-content: center;
	gap: 24px;
	margin-top: 40px;
}

.himadi-card-grid-3 .himadi-service-card {
	height: 210px;
}

@media (max-width: 767px) {
	.himadi-card-grid-3 {
		grid-template-columns: 1fr;
	}
}

/* Individual white service cards ("What We Do?") — flip on hover, front
   face shows icon + heading, back face (the "turn around" effect from the
   reference demo's flip-box widgets) shows the description text only. */
.himadi-service-card {
	display: block;
	height: 300px;
	perspective: 1200px;
	text-decoration: none;
	color: inherit;
}

.himadi-service-card-inner {
	position: relative;
	width: 100%;
	height: 100%;
	text-align: center;
	transition: transform 600ms;
	transform-style: preserve-3d;
}

.himadi-service-card:hover .himadi-service-card-inner,
.himadi-service-card.himadi-flipped .himadi-service-card-inner {
	transform: rotateY(180deg);
}

.himadi-service-card-front,
.himadi-service-card-back {
	position: absolute;
	inset: 0;
	display: flex;
	flex-direction: column;
	align-items: center;
	justify-content: center;
	/* Same pastel blue the "Contact Us" side panel used to have (it's since
	   been redone as a chat bubble with a plain white panel -- see
	   himadi_render_contact_tab()), per request -- this rule is unscoped so
	   it's the default for every page using
	   .himadi-service-card, but IT Services (24) and Digital Marketing
	   (1451) have their own more-specific override further down that keeps
	   them on their separate faded-blue tint, so in practice this only
	   changes Home's six cards. Before this: rgba(37, 99, 235, 0.09), and
	   earlier today: sky blue (#87ceeb), a purple tint of the theme's own
	   primary (#5729d9), Gulf Blue, Lavender Blue, Blue Turquoise, teal,
	   indigo, and faded sky blue (#f6fbff). Faded down from 0.85 opacity to
	   0.5 per request. */
	background: rgba(219, 234, 254, 0.5);
	border-radius: 10px;
	box-shadow: 0 4px 20px rgba(0, 0, 0, 0.08);
	padding: 30px;
	backface-visibility: hidden;
}

.himadi-service-card-back {
	transform: rotateY(180deg);
}

/* IT Services (24) and Digital Marketing (1451) reuse this same card
   markup in their own post content -- the 0.09 tint that reads right on
   Home didn't look good here, so these pages get a lighter version instead
   of changing it everywhere. */
body.page-id-24 .himadi-service-card-front,
body.page-id-24 .himadi-service-card-back,
body.page-id-1451 .himadi-service-card-front,
body.page-id-1451 .himadi-service-card-back {
	background: rgba(37, 99, 235, 0.05);
}

/* IT Services page's "Core Offerings" image -- its own post content sets
   inline width:100%;height:100% (object-fit:cover), which stretched it to
   fill its column at 557x644px, much bigger than the standard 320x320
   .featured-drawing size used everywhere else on this site. !important
   needed to beat that inline style. */
body.page-id-24 img.featured-drawing {
	width: 320px !important;
	height: 320px !important;
	max-width: 100%;
}

.himadi-service-card-front svg {
	width: 48px;
	height: 48px;
	color: #2563eb;
	margin: 0 auto 16px;
	/* .himadi-service-card-front is an absolutely-positioned flex column
	   with a definite height (inset:0 inside the fixed-height
	   .himadi-service-card) -- when a card's icon+title+paragraph content
	   is taller than that fixed height (easy to hit after shrinking
	   several of these card grids), the flex algorithm's default
	   flex-shrink:1 squashed the icon's own height down to just a few px
	   (sometimes 0) to make everything fit, while width stayed at its
	   scaled 36px -- a badly distorted, near-invisible icon. The icon
	   should never be the thing that shrinks to absorb overflow. */
	flex-shrink: 0;
}

.himadi-service-card-front h5 {
	margin: 0;
}

.himadi-service-card-back p {
	margin: 0;
	color: #666;
}

/* Home page "What We Do?" cards only (himadi-services-grid-home, added in
   template-home.php) — .himadi-service-card is shared with the Simple
   Process row right below it and with IT Services/Digital Marketing page
   content, so sizing is scoped here instead of changed globally. Very
   slight shrink: columns 370px -> 340px, fixed card height 300px -> 275px. */
.himadi-services-grid-home .wp-block-column {
	flex: 0 0 340px !important;
}

.himadi-services-grid-home .himadi-service-card {
	height: 275px;
}

/* Simple Process cards (himadi_render_simple_process(), himadi-integration.php
   — shared by Home and the Services template) — same very-slight shrink as
   the "What We Do?" cards above: columns 370px -> 340px, height 300px -> 275px. */
.himadi-services-grid-process .wp-block-column {
	flex: 0 0 340px !important;
}

.himadi-services-grid-process .himadi-service-card {
	height: 275px;
}

/* Plain static info box — same card look as the service cards, but no
   flip/hover (used for Founder Message / Corporate Citizenship). */
.himadi-info-box {
	background: #fff;
	border-radius: 10px;
	box-shadow: 0 4px 20px rgba(0, 0, 0, 0.08);
	padding: 55px 50px;
	min-height: 380px;
	height: 100%;
	box-sizing: border-box;
	display: flex;
	flex-direction: column;
	justify-content: center;
	text-align: center;
}

.himadi-info-box h3 {
	margin-top: 0;
	margin-bottom: 18px;
	/* Matched to the 22px box-title size used everywhere else (Home's
	   About Us/Why Choose Us/Industry Experience, Background
	   Verification, EVS Software, the Digital Marketing sub-pages) so
	   About Us's own boxes aren't the one place still at the old 26px. */
	font-size: 22px;
}

.himadi-info-box--wide h2 {
	margin-top: 0;
	margin-bottom: 22px;
	font-size: 22px;
}

.himadi-info-box p {
	margin: 0;
	color: #666;
	/* Matched to the 14px/1.5 body-text size used everywhere else, same
	   reasoning as the h3 font-size above -- was the old 17px/1.7. */
	font-size: 14px;
	line-height: 1.5;
}

.himadi-info-box p + p {
	margin-top: 16px;
}

/* Wide variant used for "Your Trusted Partner" — height:auto instead of
   the base 380px min-height so it hugs its (now 3-paragraph) content, and
   max-width:100% so it fills the full .himadi-container width instead of
   being capped at 1100px, reading as a wide rectangle rather than a
   near-square block once that content ended up tall. Padding is trimmed
   down from the original 60px/100px, which left a big empty border around
   the text even at full width. */
.himadi-info-box--wide {
	height: auto;
	min-height: 0;
	max-width: 100%;
	padding: 35px 40px;
}

.himadi-info-box--wide p {
	font-size: 14px;
	line-height: 1.5;
}

/* Flat variant used for Founder Message / Corporate Citizenship, side by
   side in a two-column row. Only zeroes out the base class's fixed 380px
   min-height (which forced a tall square-ish block regardless of content);
   height:100% is deliberately kept from the base class so the two boxes
   still stretch to match each other via the columns row's default flex
   stretch behavior, rather than each sizing independently to its own
   paragraph length (which made Founder — the longer paragraph — visibly
   taller than Corporate). */
.himadi-info-box--flat {
	min-height: 0;
	padding: 35px 50px;
}

/* IT Services page's "Back-End IT Support" / "Front-End IT Support" boxes
   reuse this same --flat variant, but as plain block elements they fill
   their whole 50%-wide column -- capped narrower and centered within that
   column per explicit request, without affecting the About Us page's
   Founder Message / Corporate Citizenship boxes that also use this class. */
body.page-id-24 .himadi-info-box--flat {
	max-width: 480px;
}

/* Each box individually centered in its own 50% column left a big gap
   between them (their facing/inner edges, not just their outer edges,
   had empty space) -- pushing the first box right and the second box
   left instead closes that middle gap down to just the row's own 24px
   gutter, while the pair as a whole stays visually centered. */
/* Direct-child combinators throughout (not descendant/space) -- these two
   boxes are nested inside an OUTER single-column intro row too (also a
   .wp-block-column:first-child), which a plain descendant selector was
   matching for BOTH boxes instead of each box's own immediate column. */
body.page-id-24 .wp-block-columns > .wp-block-column:first-child > .himadi-info-box--flat {
	margin-left: auto;
	margin-right: 0;
}

body.page-id-24 .wp-block-columns > .wp-block-column:last-child > .himadi-info-box--flat {
	margin-left: 0;
	margin-right: auto;
}

/* Founder Message / Corporate Citizenship (About Us) each carry an inline
   width:calc(100% + 50px) "full-bleed" trick for the desktop 2-column row,
   but only Founder Message also has margin-left:-50px to re-center itself
   -- Corporate Citizenship instead just uses justify-content:flex-start,
   which balances out fine side-by-side on desktop but leaves the two edges
   misaligned once they stack on top of each other on mobile. Reset both
   back to a plain full-width box on mobile so they line up. */
@media (max-width: 767px) {
	.himadi-info-box--flat {
		width: 100% !important;
		margin-left: 0 !important;
	}
}

/* Safety net: buttons were stretching into tall vertical bars on the Home
   page — the columns they sit in now default to align-items:stretch (we
   removed the vertical-centering that used to mask it), which was
   apparently reaching the button itself as a flex item somewhere in the
   chain. Force them back to normal button sizing regardless of parent
   flex context. */
.site-main .wp-block-buttons {
	display: block;
}

.site-main .wp-block-button,
.site-main .wp-block-button__link {
	display: inline-block;
	align-self: flex-start;
	height: auto;
	width: auto;
	flex: none;
}

/* Active-page AND hover indicator on the main nav — Spexo only styles
   .current-menu-item for its mobile dropdown menu (not the desktop nav),
   and its hover state just recolors the text using --theme-primary-color
   (currently a purple, not the blue used everywhere else on this site,
   and with no underline at all) — unlike the reference demo, where both
   the active page AND whatever's being hovered get the same blue
   underline. */
/* box-shadow, not a ::before/::after pseudo-element — "Services" and any
   other dropdown-parent item already uses both pseudo-elements for its own
   arrow icon (base rule sets `content` for the icon, :hover rule just
   rotates it), so a pseudo-element based underline here risked overriding
   that icon's content/replacing it with an empty box on those items. A
   real box-shadow on the link itself can't collide with that. */
/* The nav row is vertically centered inside .tmpcoder-site-header's fixed
   15px top/bottom padding, so growing the link's own padding just pushed
   the shadow further toward that boundary instead of away from it. The
   fix is more room in the header itself, not the link.

   padding-top added (vendor's own 15px, previously left alone) and
   padding-bottom brought down from 16px -- explicit request to bring the
   whole header bar down to a 120px-tall row (it measured 145px, matching
   the logo's own 120px height plus this padding and the logo's own
   margin-top below). Trimming both, plus the logo's margin-top, closes
   that gap down to the logo's actual height. */
.tmpcoder-site-header {
	padding-top: 0;
	padding-bottom: 0;
}

/* Site logo (custom_logo attachment) — no CSS anywhere constrains it, so
   it rendered at its native pixel size: previously near-invisible (the
   attachment was wired to a broken 100x23 derivative — see the WordPress
   media library fix), and even at its correct 200x123 resolution it would
   be too tall for the nav row without a display height set here. */
.site-branding img {
	/* Bumped from 70px — the logo file has "YOUR SATISFACTION IS OUR
	   FUTURE..." baked into the image itself, below the HMDS wordmark;
	   at 70px tall (scaled down from the native 200x123 file) that
	   tagline text shrank to the point of being illegible, not just
	   small. Trying a taller display size so it actually reads. Bumped
	   again from 80px to 90px, a small nudge up, once the newer logo
	   file (2026-09) was in place, then to 100px for a little more
	   presence, then to 120px since the "YOUR SATISFACTION IS OUR
	   FUTURE..." tagline baked into the image is a fixed fraction of the
	   whole graphic's height — no amount of bolding it in the source file
	   fixes it being illegibly small at a shorter display height, only
	   scaling the whole image up does. Back down to 100px per explicit
	   request, now that the tagline itself has been redrawn bigger/bolder
	   directly in the source file — its size is still tied to the same
	   height value (one <img>, can't size two parts of one image
	   independently via CSS), but a smaller overall logo was worth trying
	   now that the tagline no longer needs as much help to read. Bumped
	   back up to 120px per follow-up request — back to the size used
	   right before that 100px experiment. Reduced to 105px per explicit
	   request alongside trimming .tmpcoder-site-header's own padding to
	   120px total height -- a 120px-tall logo with zero padding touched
	   both edges of the row exactly, leaving no breathing room, so this
	   keeps a small margin inside that 120px row instead. */
	/* Nudged down slightly from 105px, then again from 98px -- header
	   wraps tightly around the logo's own height (padding is 0), so this
	   is a small reduction to the overall header bar height. */
	height: 88px;
	width: auto;
	/* The actual cause of it always sitting a bit low no matter what:
	   <img> defaults to display:inline, which — even alone in its own
	   line box — reserves a few extra pixels below the baseline for the
	   inherited font's descenders. That invisible strip under the image
	   was the whole asymmetry; the wrapping <a>/.site-branding were
	   sized correctly all along. display:block removes the image from
	   inline layout entirely, so there's no leftover space to account
	   for and normal flex centering (.site-header's align-items:center)
	   just works. Now that it's mathematically centered against the nav
	   row, a small margin-top nudged it down slightly per explicit
	   request — it read as sitting a touch high once truly centered.
	   Removed now that .tmpcoder-site-header's own padding has been
	   trimmed to fit the header to a 120px-tall row matching the logo's
	   own height -- keeping this margin would have added it right back. */
	display: block;
	margin-top: 0;
}

/* .site-header (the row holding logo + nav) used to be widened to 1500px
   here, independently of var(--tmpcoder-container-width) (the shared width
   every other section/page content uses) -- that made the header bar a
   different width than the content below it, so the two edges didn't line
   up on wide screens (the "distorted compared to a site like aajtak.in"
   complaint: aajtak.in keeps one consistent container width for header and
   content alike). Now that the site-wide container width is set to 1270px
   (Customizer: Appearance > Customize > Layout > Container Width
   (Desktop)), the header no longer needs its own separate override --
   removing this block lets .site-header fall back to the same
   var(--tmpcoder-container-width) as everything else, so header and
   content edges line up. */

/* .site-branding sits as a flex item inside .site-header (align-items:
   center in style.min.css) but was still stretching to the row's full
   height instead of sizing to its own content — tmpcoder-theme.css makes
   .site-branding itself `display:flex; flex-direction:column;
   justify-content:center`, which only centers ITS OWN children within
   whatever height IT ends up with, and it was ending up exactly as tall
   as the row (matching nav's height) rather than just as tall as the logo.
   Forcing it to size to content here is what makes that inner
   justify-content:center actually have room to do anything. */
.site-branding {
	align-self: center;
	/* Vendor CSS allocates this a fixed 30% of the header row, far more
	   than the logo itself needs -- that unused leftover space (not any
	   gap/margin) is what was pushing "Home" so far right. Capping it to
	   the logo's actual content width closes that gap instead. */
	max-width: 220px !important;
	/* Small nudge right, away from the header's own left edge. */
	margin-left: 30px;
}

/* Shrinking .site-branding above only moves where .site-navigation's own
   box STARTS -- it doesn't by itself move "Home" closer, because
   .site-navigation itself (not the <ul>, confirmed by measuring
   getBoundingClientRect() + computed styles at runtime) has
   justify-content:flex-end from tmpcoder-theme.min.css, pushing the whole
   menu to the right edge of its own ~950px-wide box and leaving empty
   space on the left regardless of where that box starts. Left-aligning it
   instead is what actually pulls "Home" up against the logo.
   Desktop only (min-width matches style.css's own 1024px mobile-menu
   breakpoint) -- below that, .site-navigation also contains the hamburger
   toggle button instead of the menu list, and flex-start pushed that
   toggle away from the row's right edge, leaving an odd gap next to it. */
@media (min-width: 1025px) {
	.site-header .site-navigation {
		justify-content: center !important;
		/* Bumped from 90px -- pushes the whole nav (starting with "Home")
		   further left, per explicit request. */
		padding-right: 130px;
	}
}

/* On common laptop screens (~1280-1400px) the fixed 90px push-right above
   leaves "Contact Us" with too little room before the header-contact
   buttons' fixed position on the far right, causing an overlap that
   doesn't show up on a wide monitor. Easing it back at this range gives
   both enough breathing room without affecting wide screens. */
@media (min-width: 1025px) and (max-width: 1400px) {
	.site-header .site-navigation {
		/* Bumped from 20px -- measured gap between "Contact Us" and the
		   header-contact icons at this range was as little as ~9px
		   (1263px-wide viewport, i.e. a 1280px window minus a vertical
		   scrollbar), which reads as touching once real-browser font
		   rendering/subpixel differences are added on top of a headless
		   measurement. 50px keeps a safe buffer across the whole range. */
		padding-right: 50px;
	}
}

/* Below ~1200px the 20px padding above still isn't enough -- confirmed by
   testing every width from 1025px up: "Contact Us" visibly collides with
   the phone icon from roughly 1030px to 1150px (not just a single
   previously-assumed laptop width). Closing that gap from both sides:
   drop the nav's own right padding entirely, and pull the Call Us/WhatsApp
   icons' fixed offset in from 60px to 12px, since they're icon-only here
   anyway (see the max-width:1400px rule below) and don't need the wider
   margin a wide monitor has room for. */
@media (min-width: 1025px) and (max-width: 1200px) {
	.site-header .site-navigation {
		padding-right: 0;
	}

	.himadi-header-contact {
		right: 12px;
	}
}

.site-navigation .menu li > a {
	display: inline-block;
}

/* Hardcoded #2563eb instead of var(--theme-link-color) — the site's
   Customizer accent color is a purple (#5729d9), which was winning over
   this var()'s own #2563eb fallback (the same sky blue used for the
   "Contact Sales" phone numbers above the header) and made every hovered,
   current, or dropdown-open top-level nav item show a purple underline
   with blue-looking text (the OTHER rule below, plus style.min.css's own
   var(--theme-primary-color) rules, only ever got the text half fixed —
   this box-shadow bar is what stayed purple). !important guards against
   style.min.css's own hover/current rules on the same var(), which are
   already fighting each other on specificity. */
.site-navigation .menu li.current-menu-item > a,
.site-navigation .menu li.current_page_item > a,
.site-navigation .menu li.current-menu-ancestor > a,
.site-navigation .menu li > a:hover,
.site-navigation .menu li > a:focus {
	box-shadow: 0 3px 0 0 #1d4ed8 !important;
}

.site-navigation .menu li.current-menu-item > a,
.site-navigation .menu li.current_page_item > a,
.site-navigation .menu li.current-menu-ancestor > a,
.site-navigation .menu li > a:hover,
.site-navigation .menu li > a:focus {
	color: #1d4ed8 !important;
}

/* Home page "Latest from the Blog" section previously used a separate,
   wider 1600px container instead of the shared var(--tmpcoder-container-
   width) -- at a 1600px-wide screen specifically, that left the 4 cards
   spanning edge-to-edge with no side white space at all, inconsistent
   with every other section on the site (now standardized to 1270px, see
   the Customizer's Container Width setting). Removing the override here
   lets it fall back to .himadi-container's own shared max-width, same as
   everywhere else. */

/* Home page "Latest from the Blog" section — 4 posts in one row, matching
   the main Blog page's 4-column grid, rather than auto-fit wrapping
   unpredictably depending on viewport width. */
.himadi-blog-preview-grid {
	display: grid;
	grid-template-columns: repeat(4, 1fr);
	gap: 24px;
	margin-top: 30px;
}

@media (max-width: 1024px) {
	.himadi-blog-preview-grid {
		grid-template-columns: repeat(2, 1fr);
	}
}

@media (max-width: 600px) {
	.himadi-blog-preview-grid {
		grid-template-columns: 1fr;
	}
}

.himadi-blog-preview-card {
	background: #fff;
	border: 1px solid var(--theme-global-border-color, #e5e5e5);
	border-radius: 6px;
	overflow: hidden;
}

.himadi-blog-preview-card img {
	width: 100%;
	height: 170px;
	object-fit: cover;
	display: block;
	transition: transform 400ms ease;
}

/* .himadi-blog-preview-card already has overflow:hidden, which is what
   clips the zoomed image back to the card's rounded corners instead of it
   spilling out over the text below. */
.himadi-blog-preview-card:hover img {
	transform: scale(1.08);
}

.himadi-blog-preview-card-body {
	padding: 18px;
}

.himadi-blog-preview-card-body .himadi-blog-date {
	font-size: 13px;
	color: #888;
	margin: 0 0 6px;
}

.himadi-blog-preview-card-body h3 {
	margin: 0 0 10px;
	font-size: 18px;
	line-height: 1.35;
}

.himadi-blog-preview-card-body h3 a {
	text-decoration: none;
	color: inherit;
}

.himadi-blog-preview-card-body p {
	font-size: 14px;
	color: #666;
	margin: 0 0 12px;
}

/* "What Our Clients Say" (himadi_render_testimonials()) — Strong
   Testimonials plugin content (wpm-testimonial post type), rendered with
   the same white-card grid look as the blog preview above instead of the
   plugin's own stock shortcode/template, so it matches the rest of the
   page's card styling. */
/* Testimonials slider — 2 cards per slide, now auto-advancing between the
   2 slides (himadi-testimonial-slider.js) instead of requiring a manual
   dot click, per explicit request. No photos: card is just
   quote → name → stars, per explicit "dont add photos just client name"
   instruction. */
/* Explicit request to reduce the horizontal width of the two testimonial
   boxes -- capped narrower than the full .himadi-container (1270px) and
   centered, same pattern as Home's About Us/Why Choose Us/Industry
   Experience boxes. */
.himadi-testimonial-slider {
	position: relative;
	overflow: hidden;
	margin-top: 14px;
	/* Widened back out from 1000px per explicit follow-up request. */
	max-width: 1150px;
	margin-left: auto;
	margin-right: auto;
}

/* Sliding transition (himadi-testimonial-slider.js) instead of a plain
   show/hide toggle — clicking dot 2 sends the current slide off to the
   left while the next one slides in from the right to replace it (and
   the reverse when going back). The active slide is position:relative
   (in normal flow, so it drives the slider's actual height); every other
   slide is position:absolute so it doesn't add extra height while
   off-screen mid-transition. */
.himadi-testimonial-slide {
	display: grid;
	grid-template-columns: repeat(2, 1fr);
	gap: 24px;
	position: absolute;
	top: 0;
	left: 0;
	width: 100%;
	transform: translateX(100%);
	transition: transform 450ms ease;
}

.himadi-testimonial-slide.is-active {
	position: relative;
	transform: translateX(0);
}

.himadi-testimonial-slide.is-prev {
	transform: translateX(-100%);
}

@media (max-width: 782px) {
	.himadi-testimonial-slide {
		grid-template-columns: 1fr;
	}
}

.himadi-testimonial-card {
	background: #fff;
	border-radius: 10px;
	box-shadow: 0 4px 20px rgba(0, 0, 0, 0.08);
	/* Trimmed down to 10px (30px -> 22px -> 14px -> 10px) to reduce the
	   card's vertical length, but that read as text touching the box
	   edges with no breathing room -- brought back up to 24px per
	   follow-up request. */
	padding: 24px;
}

.himadi-testimonial-quote {
	/* Matched to the Simple Process cards' own body text
	   (.himadi-service-card-front p, computed: 14px/#777/line-height
	   21.7px ≈ 1.55) -- font-size already matched, color/line-height
	   didn't. */
	color: #777;
	font-size: 14px;
	line-height: 1.55;
	margin: 0 0 6px;
}

.himadi-testimonial-author-name {
	margin: 0 0 2px;
	font-size: 14px;
	font-weight: 700;
}

.himadi-testimonial-stars {
	color: #f5b400;
	letter-spacing: 2px;
	margin: 0;
}

.himadi-testimonial-dots {
	display: flex;
	justify-content: center;
	gap: 8px;
	margin-top: 30px;
}

.himadi-testimonial-dot {
	width: 10px;
	height: 10px;
	padding: 0;
	border: none;
	border-radius: 50%;
	background: #d1d5db;
	cursor: pointer;
}

.himadi-testimonial-dot.is-active {
	background: #2563eb;
}

/* "By The Numbers" stat rings (himadi_render_stats()) — plain CSS
   conic-gradient rings styled roughly after the reference layout's
   circular stat widgets. --pct starts at the real value here (server-
   rendered) but assets/js/himadi-stat-counter.js resets it to 0 on load
   and animates it back up (together with the number's digits) once
   scrolled into view, so this static rule is really just the ring's
   at-rest/no-JS fallback value. */
.himadi-stats-grid {
	display: grid;
	grid-template-columns: repeat(auto-fit, minmax(160px, 1fr));
	gap: 40px;
	margin-top: 10px;
	text-align: center;
}

/* Ring shrunk 168px -> 130px and number/label font sizes reduced to
   match, per explicit request. */
.himadi-stat-ring {
	position: relative;
	width: 130px;
	height: 130px;
	border-radius: 50%;
	background: conic-gradient(#2563eb calc(var(--pct, 75) * 1%), #111827 0);
	margin: 0 auto 16px;
}

.himadi-stat-ring-inner {
	position: absolute;
	inset: 10px;
	background: #fff;
	border-radius: 50%;
	display: flex;
	align-items: center;
	justify-content: center;
	padding: 0 6px;
}

.himadi-stat-number {
	font-size: 18px;
	font-weight: 700;
	color: #111;
	white-space: nowrap;
}

.himadi-stat-label {
	font-size: 12px;
	font-weight: 600;
	margin: 0;
}

.himadi-icon-circle.is-light img {
	max-width: 34px;
	max-height: 34px;
	/* select-checks.png / fill-information.png / Get-Background-report.png
	   were flat red line-art on a transparent background (color baked into
	   the pixels, from him-theme), recolored blue via a hue-rotate filter
	   to match the site's current color direction. That filter is gone now
	   — turned out the 3 source PNGs weren't all the exact same starting
	   red (Get-Background-report.png was a visibly different red than the
	   other two), so identical hue-rotate math landed on two different
	   blues instead of one. Recolored the pixels directly to the same
	   #2563eb for all three instead, so there's no per-image hue drift
	   left to compensate for. */
}

/* Background Verification / IT Services — now that the Services sidebar
   column is gone on these two pages (template-services.php), the intro
   fold (eyebrow, title, paragraphs) spans the full row instead of a 64%
   column and reads oddly left-pinned across that width, so it's centered
   instead. The eyebrow ("Background Verification" / "IT Services") and
   IT Services' intro paragraph both carry their own inline
   text-align:left / max-width from the stored ACF field HTML — !important
   and margin:auto are needed to actually override/center those rather
   than just the wrapper's own alignment. */
.himadi-service-intro-centered {
	text-align: center;
}

.himadi-service-intro-centered .himadi-eyebrow {
	text-align: center !important;
}

.himadi-service-intro-centered p {
	margin-left: auto;
	margin-right: auto;
	/* Matched to the SEO/Digital-Marketing page's own intro paragraph
	   (.himadi-dm-page-content > p, 14px !important) -- the inline
	   font-size:17px in this page's content needs the same override. */
	font-size: 14px !important;
}

/* Services page: content + sticky-ish "Services" link list */
.himadi-services-sidebar {
	background: var(--theme-background-color, #f7f7f7);
	border: 1px solid var(--theme-global-border-color, #e5e5e5);
	border-radius: 6px;
	padding: 20px;
}

.himadi-services-sidebar .wp-block-heading {
	margin-top: 0;
}

.himadi-services-sidebar ul {
	list-style: none;
	margin: 0;
	padding: 0;
}

.himadi-services-sidebar li {
	margin-bottom: 10px;
}

.himadi-services-sidebar li:last-child {
	margin-bottom: 0;
}

/* Same light lavender-blue as the BGC Component accordion headers
   (.site-main .accordion, below) instead of the old solid
   var(--theme-primary-color)/var(--theme-secondary-color) fill (a vivid
   purple + near-black) — softer, and consistent with the accordion's own
   color language on this same page. */
.himadi-services-sidebar a {
	display: block;
	padding: 14px 18px;
	/* !important: tmpcoder-theme.min.css's "body .site-main .page-content a
	   { text-decoration: underline }" (meant for inline links in ordinary
	   body copy) outscores a plain .himadi-services-sidebar a selector, since
	   this sidebar happens to sit inside .page-content on these templates —
	   was showing an underline under every sidebar button regardless of the
	   text-decoration:none already declared here. */
	text-decoration: none !important;
	/* White box, blue text -- swapped from the previous pastel-blue-fill /
	   dark-navy-text look, per request. */
	color: #2563eb;
	border-radius: 4px;
	background: #fff;
	border: 1px solid #dbe4ff;
	transition: background-color 150ms ease;
}

.himadi-services-sidebar a:hover {
	background-color: #eef2ff;
	color: #2563eb;
}

/* The middle item (Digital Marketing) gets an off-white button instead of
   the light-blue fill, so it stands apart as the visual center of the
   3-item list — a positional accent, not tied to which page is current.
   Scoped to the Services template specifically: template-blank.php's
   Digital Marketing family pages reuse .himadi-services-sidebar for their
   own 4-item SEO/Content/Social/Email list, where there's no "middle"
   item to single out. */
.page-template-template-services .himadi-services-sidebar li:nth-child(2) a {
	background: #fafafa;
	border-color: #e5e5e5;
	color: #333;
}

.page-template-template-services .himadi-services-sidebar li:nth-child(2) a:hover {
	background-color: #f0f0f0;
	color: #333;
}

/* Career / Contact / Home enquiry form cards.
   The shared Contact Form 7 forms still carry their old Bulma-esque markup
   (.columns/.column.is-6 field pairs, a hardcoded 625px message box) from
   him-theme — Spexo has no CSS for any of that, so fields were rendering at
   raw browser-default width, left-aligned with a lot of dead space next to
   them. This reconstructs the intended two-up field layout and gives every
   control a real, full-width, bordered input style. */
.himadi-form-card {
	/* A subtly different off-white from the section's own #f6f5f2
	   background (template-home.php's wp-block-cover) — close enough to
	   read as "off-white" per request, but still distinct enough (plus
	   the box-shadow below) that the card doesn't visually disappear into
	   the section behind it. */
	background: #fdfcfa;
	border-radius: 6px;
	/* Trimmed from 16px 20px -- same vertical-length reduction. */
	padding: 12px 20px;
	box-shadow: 0 4px 20px rgba(0, 0, 0, 0.08);
}

/* Contact Us page's "Get Started With Himadi" box specifically -- it fills
   its whole 58%-wide column by default, reading as a big box next to the
   map. Capped narrower and its own padding/field sizing trimmed further,
   without affecting the same card reused at the bottom of Home (that one
   is already a reasonable size in its own, narrower, centered section). */
body.page-template-template-contact-php .himadi-form-card {
	max-width: 560px;
	padding: 16px 20px;
}

body.page-template-template-contact-php .himadi-offices {
	/* width:auto (the default) makes margin-left shrink the box instead of
	   shifting it, since a block box with width:auto solves "available
	   width = container - margins" -- max-content keeps it sized to its
	   own content so margin-left actually moves it right. */
	width: max-content;
	margin-left: 90px;
}

body.page-template-template-contact-php .himadi-form-card .columns {
	gap: 10px;
	margin-bottom: 0;
}

body.page-template-template-contact-php .himadi-form-card input[type="text"],
body.page-template-template-contact-php .himadi-form-card input[type="email"],
body.page-template-template-contact-php .himadi-form-card input[type="tel"],
body.page-template-template-contact-php .himadi-form-card select,
body.page-template-template-contact-php .himadi-form-card textarea {
	padding: 5px 8px;
	font-size: 12px;
}

body.page-template-template-contact-php .himadi-form-card textarea {
	min-height: 50px;
}

.himadi-form-card .columns {
	display: flex;
	flex-wrap: wrap;
	gap: 16px;
	margin: 0 0 4px;
}

.himadi-form-card .column {
	flex: 1 1 100%;
	min-width: 0;
}

.himadi-form-card .column.is-6 {
	flex-basis: calc(50% - 8px);
}

/* The Career form (Contact Form 7 id 82) uses a different Bootstrap-style
   grid than Contact/Home's .columns/.column.is-6 above — .col-sm-6/
   .col-sm-12 wrapping .input-block, with no .row/flex container around
   them (they're direct children of <form>). inline-block avoids needing
   to make <form> itself a flex container, which would also affect the
   plain <p>-wrapped fields Contact/Home's forms use. */
/* font-size:0 on the form / restored on the columns: two inline-block
   elements each set to width:50% add up to exactly 100% of the parent
   with zero room left over for the whitespace text node the raw HTML
   leaves between them (a newline between "</div>" and the next "<div
   class="col-sm-6">"), which was enough to push the second column onto
   its own line instead of sitting beside the first — First Name/Last
   Name were rendering stacked instead of paired despite col-sm-6 being
   exactly what col-sm-12's siblings intended. */
.himadi-form-card form {
	font-size: 0;
}

.himadi-form-card .col-sm-6,
.himadi-form-card .col-sm-12 {
	display: inline-block;
	vertical-align: top;
	box-sizing: border-box;
	padding: 0 8px;
	/* Trimmed further (16px -> 10px -> 6px) -- explicit request to keep
	   reducing the form's overall vertical length. */
	margin-bottom: 6px;
	font-size: 1rem;
}

.himadi-form-card .col-sm-6 {
	width: 50%;
}

.himadi-form-card .col-sm-12 {
	width: 100%;
}

@media (max-width: 600px) {
	.himadi-form-card .col-sm-6 {
		width: 100%;
	}
}

.himadi-form-card textarea.wpcf7-textarea {
	/* height, not just min-height — the CF7 shortcode's own rows="10"
	   attribute otherwise sizes the box taller regardless of min-height,
	   which was the biggest single contributor to the card's overall
	   height. (Actual class is wpcf7-textarea, not .input-block.textarea —
	   that selector never matched anything.) Shrunk further (80px -> 60px)
	   per explicit request to keep reducing the form's vertical length. */
	height: 60px;
	min-height: 60px;
}

.himadi-form-card input[type="file"] {
	display: block;
	margin-top: 8px;
}

.himadi-form-card .form-field,
.himadi-form-card > form > p {
	margin-bottom: 10px;
}

.himadi-form-card .field-label,
.himadi-form-card .mdb-main-label,
.himadi-form-card .country_details,
.himadi-form-card label {
	display: block;
	margin-bottom: 4px;
	font-weight: 600;
	/* Trimmed from 14px -- explicit request, labels/inputs looked too
	   big. */
	font-size: 12px;
}

.himadi-form-card input[type="text"],
.himadi-form-card input[type="email"],
.himadi-form-card input[type="tel"],
.himadi-form-card select,
.himadi-form-card textarea {
	display: block;
	width: 100%;
	box-sizing: border-box;
	/* Trimmed further (10px 12px -> 8px 12px -> 6px 10px) -- same
	   vertical-length reduction as the field spacing above. */
	padding: 6px 10px;
	border: 1px solid var(--theme-global-border-color, #ddd);
	border-radius: 4px;
	font-family: inherit;
	/* Trimmed from 15px -- same font-size reduction as the labels. */
	font-size: 13px;
	transition: border-color 150ms ease, box-shadow 150ms ease;
}

.himadi-form-card input[type="text"]:focus,
.himadi-form-card input[type="email"]:focus,
.himadi-form-card input[type="tel"]:focus,
.himadi-form-card select:focus,
.himadi-form-card textarea:focus {
	outline: none;
	border-color: var(--theme-link-color, #2563eb);
	box-shadow: 0 0 0 3px rgba(37, 99, 235, 0.15);
}

.himadi-form-card .inputBox {
	display: block;
	width: 100% !important;
}

.himadi-form-card .wpcf7-form-control-wrap {
	display: block;
}

.himadi-form-card .submit_buttons {
	margin-top: 8px;
}

.himadi-form-card input.wpcf7-submit {
	width: auto;
	background: var(--theme-button-background, var(--theme-primary-color, #610e15));
	color: var(--button-text-color, #fff);
	border: none;
	border-radius: var(--button-border-radius, 4px);
	padding: 12px 28px;
	font-weight: 600;
	cursor: pointer;
}

.himadi-form-card input.wpcf7-submit:hover {
	/* Deliberately not var(--theme-button-background-hover) — it resolves
	   to pure white in this site's color settings, which combined with the
	   button's white text made it go fully invisible on hover instead of
	   just changing shade. Fixed darker-blue shade instead, matching the
	   button's own var(--theme-button-background) blue. */
	background: #3f6fd1;
}

/* Career page — "Apply Online" heading slides down into place from above,
   the same entrance-animation treatment as the Contact page's slide-in
   columns, just on the vertical axis. */
.himadi-slide-in-down {
	animation: himadi-fade-in-down 700ms ease-out both;
	animation-play-state: paused;
}

@keyframes himadi-fade-in-down {
	from {
		opacity: 0;
		transform: translateY(-40px);
	}
	to {
		opacity: 1;
		transform: translateY(0);
	}
}

/* Section headings/cards across the site (Home "What We Do?"/"Simple
   Process"/"Why Choose Us"/blog preview, About Us, Career's form card, and
   below) rise up into place from below on scroll — same technique as
   .himadi-slide-in-down above, just the opposite vertical direction. */
.himadi-slide-in-up {
	animation: himadi-fade-in-up 700ms ease-out both;
	animation-play-state: paused;
}

@keyframes himadi-fade-in-up {
	from {
		opacity: 0;
		transform: translateY(40px);
	}
	to {
		opacity: 1;
		transform: translateY(0);
	}
}

/* Home "Our Services" flip-cards and "Simple Process" icon cards — grows
   up from a smaller scale to full size as it scrolls into view ("appears
   fully from inside"), instead of sliding in from a direction like the
   sections around it. Same paused/.himadi-in-view mechanism as every other
   entrance animation here (see assets/js/himadi-scroll-reveal.js). */
.himadi-scale-in {
	animation: himadi-scale-in-kf 600ms ease-out both;
	animation-play-state: paused;
}

@keyframes himadi-scale-in-kf {
	from {
		opacity: 0;
		transform: scale(0.75);
	}
	to {
		opacity: 1;
		transform: scale(1);
	}
}

/* Staggered by column position so cards grow in one after another rather
   than all at once — same stagger amount already used for the blog
   listing cards below. :nth-child(3n+2)/(3n) (rather than a flat
   nth-child(2)/(3)) repeats the same 1-2-3 stagger pattern every 3 items,
   so it works both for a single 3-card row (Home's "Our Services"/"Simple
   Process") and a multi-row 3-column grid (IT Services' 6-card
   .himadi-card-grid-3) without the second row losing its stagger. */
.himadi-scale-in:nth-child(3n + 2) {
	animation-delay: 120ms;
}

.himadi-scale-in:nth-child(3n) {
	animation-delay: 240ms;
}

/* Same tmpcoder_get_blog_list() cards print a "by [Author]" byline
   (tmpcoder_posted_by(), .byline span) next to the date/comment count —
   all posts here are published under one shared team account, so the
   author name is just noise rather than useful info. */
.blog-list-box .byline {
	display: none;
}

/* Blog listing cards (tmpcoder_get_blog_list()) — title + date only, no
   excerpt. The description paragraph made cards read cluttered/long; the
   date (already printed via tmpcoder_posted_on(), .blog-date li) plus the
   title is enough to identify a post before clicking through. */
.blog-list-box .blog-des {
	display: none;
}

/* Blog listing page — wider container (1600px vs. the theme's default
   1200px cap) so the 4-column grid's cards get noticeably bigger instead
   of reading cramped with a lot of unused white space on both sides of
   the page at typical desktop widths. Scoped to body.blog specifically
   (the posts-index page) rather than changing the site's container width
   generally. */
body.blog .site-main .page-content {
	max-width: 1600px;
}

/* Blog listing grid — 4 cards per row instead of the vendor's default 3
   (style.css's .blog-list-box is 33.33% width); posts_per_page is set to
   8 (wp_options) so this renders as 2 full rows of 4 rather than 2 rows
   of 3 plus a partial row. */
body .site-main .blog-part .blog-list-box {
	width: calc(25% - 30px);
}

@media (max-width: 1024px) {
	body .site-main .blog-part .blog-list-box {
		width: calc(50% - 30px);
	}
}

@media (max-width: 767px) {
	body .site-main .blog-part .blog-list-box {
		width: calc(100% - 30px);
	}
}

/* Reverted from a 1:1 square crop back to the vendor's original 16:9 —
   these blog thumbnails are graphic banners with the post title baked
   into the image edge-to-edge (e.g. "HOW BGV CHECKS WORK FOR CRIMINAL
   RECORDS? A GUIDE FOR HR LEADERS"), and the square crop was cutting off
   both sides of that text. 16:9 is close enough to these images' native
   ~1.91:1 ratio that object-fit:cover barely trims them, keeping the
   full banner text readable. */
body .site-main .page-content .tmpcoder-blog-list .blog-list-img img {
	aspect-ratio: 16 / 9;
	object-fit: cover;
}

/* Blog listing and Case Study listing card titles (.blog-list-content
   .entry-title) share a vendor rule (style.css) with word-break:break-all
   -- meant to force-truncate an overly long single unbroken string, but
   applied unconditionally it breaks ordinary titles mid-word ("Criminal"
   splitting into "C" / "riminal" across lines) since the browser prefers
   breaking at an arbitrary character over wrapping at the next space.
   overflow-wrap:break-word only forces a mid-word break as a last resort,
   when a single word truly doesn't fit -- normal titles wrap at spaces
   like everywhere else on the site. */
body .site-main .page-content .blog-list-content .entry-title {
	word-break: normal;
	overflow-wrap: break-word;
}

/* Blog listing (index.php → tmpcoder_archive_markup()) and the Case Study
   listing (page-case-study.php) share the same vendor/theme-function
   markup for their page title (.page-header .entry-title) and post cards
   (.blog-list-box, from tmpcoder_get_blog_list()) — targeted here by their
   existing class names instead of editing those vendor functions, same as
   himadi_fix_legacy_content_markup() elsewhere avoids touching vendor code.
   Cards stagger in by column position as they enter (reusing the "Our
   Story" timeline's stagger delays), rather than all rising at once. */
.page-header .entry-title,
.blog-list-box {
	animation: himadi-fade-in-up 700ms ease-out both;
	animation-play-state: paused;
}

.blog-list-box:nth-child(2) {
	animation-delay: 120ms;
}

.blog-list-box:nth-child(3) {
	animation-delay: 240ms;
}

.blog-list-box:nth-child(4) {
	animation-delay: 360ms;
}

.blog-list-box:nth-child(n + 5) {
	animation-delay: 480ms;
}

/* Phone + WhatsApp quick-contact links, injected by
   himadi-header-contact.js as a child of the OUTER
   <header class="tmpcoder-site-header"> (full page width), not the inner
   .site-header row -- that inner row is capped at ~1200px and centered
   with almost no spare room to the right of the nav menu inside it (same
   fix the old DNV badge needed). position:absolute against the outer
   header (already position:relative in the vendor CSS) gives it the real,
   full page-width right edge to pin to, clear of "Contact Us". Hidden
   below 1024px since the header switches to the hamburger layout there. */
.himadi-header-contact {
	position: absolute;
	top: 50%;
	right: 60px;
	transform: translateY(-50%);
	display: flex;
	align-items: center;
	gap: 10px;
	z-index: 2;
}

.himadi-header-contact-item {
	display: flex;
	align-items: center;
	gap: 6px;
	font-size: 16px;
	font-weight: 700;
	white-space: nowrap;
	color: #6b6b6b;
	text-decoration: none;
	transition: color 150ms ease;
}

.himadi-header-contact-item:hover {
	color: var(--theme-primary-color, #5729d9);
}

.himadi-header-contact-item .himadi-header-contact-icon {
	display: flex;
	align-items: center;
	justify-content: center;
	flex-shrink: 0;
}

.himadi-header-contact-item svg {
	width: 16px;
	height: 16px;
	flex-shrink: 0;
	color: inherit;
}

/* Raised from 1200px -- on common laptop screens (~1280-1366px wide) the
   widened header/menu (see .site-header max-width and .site-navigation
   padding-right above) left "Contact Us" and these buttons with no room
   and they started overlapping. Switching to icon-only sooner (at 1400px)
   frees up enough space before that overlap point is reached. */
@media (max-width: 1400px) {
	.himadi-header-contact-item span {
		display: none;
	}

	.himadi-header-contact-item {
		padding: 7px;
	}
}

/* Raised from 1024px -- even icon-only (see the max-width:1400px rule
   above) and pulled in to right:12px (see the max-width:1200px rule
   above), there still isn't room: tested every width from 1025px up and
   "Contact Us" keeps colliding with these icons as late as ~1150px.
   Hiding them up to the point that's actually confirmed clear (1200px,
   where the nav's own padding-right:0 rule above also stops) avoids
   fighting over the last few pixels on a genuinely too-narrow row. */
@media (max-width: 1200px) {
	.himadi-header-contact {
		display: none;
	}
}

/* Site-wide chat bubble + two-page panel (himadi_render_contact_tab(),
   himadi-contact-tab.js) — trialling Spexo/Cleano's own demo chat-widget
   look (a round bubble fixed to the bottom-right corner) in place of the
   vertical "Contact Us" tab this replaced. Easy to revert: swap this whole
   block and the PHP/JS it styles back to the tab+side-panel version if this
   doesn't work out. */
.himadi-chat-bubble {
	position: fixed;
	right: 24px;
	bottom: 24px;
	width: 74px;
	height: 74px;
	border-radius: 50%;
	display: flex;
	align-items: center;
	justify-content: center;
	/* Trying #1877F2 (Facebook blue), per request -- before that Deep Sky
	   Blue (#00bfff), Electric Violet (#6f00ff), #4d4dff, #1ca9c9, Cadet
	   Blue (#5f9ea0), Turquoise (#40e0d0), Aquamarine (#7fffd4), an
	   eyeballed magenta/pink (#c2126b) trying to match the Cleano demo's
	   own bubble, Iris (#5d3fd3), Ruby (#e0115f), a bright "Bleu de France"
	   blue (#318ce7), bright cyan (#00ccff), a deep teal (#007791),
	   Cambridge Blue (#a3c1ad), and originally the same navy (#1e2b4d) as
	   the panel header. */
	background: #1877f2;
	color: #fff;
	border: none;
	cursor: pointer;
	box-shadow: 0 6px 20px rgba(0, 0, 0, 0.25);
	z-index: 999;
	transition: background 150ms ease, transform 150ms ease;
}

.himadi-chat-bubble:hover {
	background: #145dbf;
	transform: scale(1.05);
}

.himadi-chat-bubble svg {
	width: 44px;
	height: 44px;
}

.himadi-chat-panel {
	position: fixed;
	right: 24px;
	bottom: 110px;
	width: 360px;
	max-width: calc(100vw - 48px);
	max-height: 70vh;
	background: #fff;
	border-radius: 12px;
	box-shadow: 0 10px 40px rgba(0, 0, 0, 0.25);
	overflow: hidden;
	opacity: 0;
	transform: translateY(16px) scale(0.97);
	pointer-events: none;
	transition: opacity 200ms ease, transform 200ms ease;
	z-index: 1000;
	color: #1a1a1a;
}

.himadi-chat-panel.is-open {
	opacity: 1;
	transform: translateY(0) scale(1);
	pointer-events: auto;
}

.himadi-chat-page {
	display: none;
	flex-direction: column;
	max-height: 70vh;
}

.himadi-chat-page.is-active {
	display: flex;
}

.himadi-chat-header {
	display: flex;
	align-items: center;
	justify-content: space-between;
	gap: 10px;
	padding: 16px 18px;
	background: #1e2b4d;
	color: #fff;
	font-weight: 600;
}

.himadi-chat-back,
.himadi-chat-close {
	background: none;
	border: none;
	color: #fff;
	cursor: pointer;
	padding: 0;
	line-height: 1;
	flex: 0 0 auto;
}

.himadi-chat-back {
	font-size: 18px;
}

.himadi-chat-close {
	font-size: 24px;
}

.himadi-chat-header span {
	flex: 1 1 auto;
}

.himadi-chat-body {
	padding: 20px;
	overflow-y: auto;
}

.himadi-chat-greeting {
	margin: 0 0 16px;
	color: #444;
	font-size: 14px;
}

/* Teaser speech-bubble -- pops up near the chat bubble a few seconds after
   page load (himadi-contact-tab.js) to invite a click, same greeting text
   as the chat log's first message. Dismissible on its own via the X, or by
   clicking it to open the panel; either way it won't show again for the
   rest of the browser session (sessionStorage). */
.himadi-chat-teaser {
	position: fixed;
	right: 24px;
	bottom: 112px;
	max-width: 240px;
	background: #fff;
	color: #1a1a1a;
	border-radius: 18px;
	padding: 14px 30px 14px 16px;
	box-shadow: 0 6px 20px rgba(0, 0, 0, 0.2);
	z-index: 998;
	opacity: 0;
	transform: translateY(10px);
	pointer-events: none;
	transition: opacity 200ms ease, transform 200ms ease;
	cursor: pointer;
}

/* Speech-bubble tail -- two stacked triangles (a slightly larger white one
   on top of a transparent-bordered one) pointing down toward the smiley
   chat bubble icon below, so the teaser reads as the icon "speaking"
   rather than a floating card. */
.himadi-chat-teaser::after {
	content: "";
	position: absolute;
	right: 28px;
	bottom: -9px;
	width: 0;
	height: 0;
	border-left: 10px solid transparent;
	border-right: 2px solid transparent;
	border-top: 11px solid #fff;
	filter: drop-shadow(2px 3px 2px rgba(0, 0, 0, 0.08));
}

.himadi-chat-teaser.is-visible {
	opacity: 1;
	transform: translateY(0);
	pointer-events: auto;
}

.himadi-chat-teaser p {
	margin: 0;
	font-size: 14px;
	font-weight: 600;
}

.himadi-chat-teaser-close {
	position: absolute;
	top: 6px;
	right: 8px;
	background: none;
	border: none;
	color: #888;
	font-size: 16px;
	line-height: 1;
	cursor: pointer;
	padding: 2px;
}

/* Quick-reply topic buttons + the resulting conversation log, both inside
   the chat panel's intro page, above the existing call/WhatsApp/message
   actions -- a simple rule-based "chatbot": clicking a topic appends a
   user bubble and a canned bot reply bubble to the log instead of calling
   any backend/AI. */
.himadi-chat-log {
	display: flex;
	flex-direction: column;
	gap: 8px;
	margin-bottom: 14px;
}

.himadi-chat-msg {
	margin: 0;
	font-size: 14px;
	line-height: 1.4;
	padding: 8px 12px;
	border-radius: 10px;
	max-width: 85%;
}

.himadi-chat-msg--bot {
	background: #f0f5ff;
	color: #1e2b4d;
	align-self: flex-start;
	border-bottom-left-radius: 2px;
}

.himadi-chat-msg--user {
	background: #1877f2;
	color: #fff;
	align-self: flex-end;
	border-bottom-right-radius: 2px;
}

.himadi-chat-msg--bot a {
	color: #1e2b4d;
	font-weight: 600;
	text-decoration: underline;
}

.himadi-chat-topics {
	display: flex;
	flex-wrap: wrap;
	gap: 8px;
	margin-bottom: 16px;
}

.himadi-chat-topic {
	background: #fff;
	color: #1e2b4d;
	border: 1px solid #c7d7f5;
	border-radius: 999px;
	padding: 6px 12px;
	font-size: 13px;
	font-weight: 600;
	cursor: pointer;
	transition: background 150ms ease;
}

.himadi-chat-topic:hover {
	background: #f0f5ff;
}

.himadi-chat-action {
	display: flex;
	align-items: center;
	gap: 10px;
	width: 100%;
	background: #f0f5ff;
	color: #1e2b4d;
	border: none;
	border-radius: 8px;
	padding: 12px 14px;
	margin-bottom: 10px;
	font-size: 14px;
	font-weight: 600;
	text-decoration: none;
	cursor: pointer;
	transition: background 150ms ease;
}

.himadi-chat-action:last-child {
	margin-bottom: 0;
}

.himadi-chat-action:hover {
	background: #dbe8ff;
}

.himadi-chat-action svg {
	width: 18px;
	height: 18px;
	flex: 0 0 auto;
	color: #2563eb;
}

.himadi-chat-page--form .himadi-form-card {
	padding: 0;
	box-shadow: none;
	background: transparent;
}

.himadi-chat-page--form .himadi-form-card .field-label,
.himadi-chat-page--form .himadi-form-card .mdb-main-label,
.himadi-chat-page--form .himadi-form-card .country_details,
.himadi-chat-page--form .himadi-form-card label {
	color: #333;
}

.himadi-chat-page--form .himadi-form-card input[type="text"],
.himadi-chat-page--form .himadi-form-card input[type="email"],
.himadi-chat-page--form .himadi-form-card input[type="tel"],
.himadi-chat-page--form .himadi-form-card select,
.himadi-chat-page--form .himadi-form-card textarea {
	background: #fff;
	border-color: #c7d7f5;
	color: #1a1a1a;
}

.himadi-chat-page--form .himadi-form-card select option {
	color: #1a1a1a;
}

.himadi-chat-page--form .himadi-form-card ::placeholder {
	color: #888;
}

@media (max-width: 480px) {
	.himadi-chat-panel {
		right: 12px;
		bottom: 88px;
		width: calc(100vw - 24px);
	}

	.himadi-chat-bubble {
		right: 16px;
		bottom: 16px;
	}
}

/* Case study listing grid (page-case-study.php) */
.himadi-case-study-grid {
	display: grid;
	grid-template-columns: repeat(auto-fill, minmax(300px, 1fr));
	gap: 24px;
}

/* Footer business info block, hooked before Spexo's own footer.
   Colors matched to the Spexo/Cleano demo footer (a single neutral light
   gray band, not the lavender-tinted two-tone this used before) per
   request -- was #f3f2f7 here / #ece9f5 on the copyright bar below,
   matching himadi.com's live two-tone look instead. */
/* Trimmed (50px/30px -> 24px/16px) -- explicit request to reduce the
   footer's overall vertical height. */
.himadi-footer-info {
	background: #e9e9ec;
	color: #666;
	padding: 24px 20px 16px;
	margin-top: 0 !important;
}

/* Bottom copyright bar, hooked after .himadi-footer-info -- same neutral
   gray as it, separated by a thin top border instead of a color shift,
   matching the Cleano demo's continuous single-band footer. */
.himadi-footer-copyright {
	background: #e9e9ec;
	border-top: 1px solid #e5e5e9;
	color: #666;
	text-align: center;
	padding: 16px 20px;
}

.himadi-footer-copyright p {
	margin: 0;
	font-size: 13.5px;
}

/* Belt-and-braces: force zero space between the testimonials section and
   whatever follows it (normally .himadi-footer-info) — !important because
   no plain-specificity override reliably beat whatever was adding the gap
   here (couldn't be traced to any margin/padding this codebase controls
   directly; possibly Elementor's active global kit CSS on this install). */
.himadi-testimonials-section {
	margin-bottom: 0 !important;
}

/* "TESTIMONIALS" eyebrow + "What Our Client's Say?" heading -- explicit
   request to reduce their text size and the vertical space around them.
   Scoped to this section specifically rather than the shared
   .himadi-eyebrow class (used for other section labels like "Our
   Services" too) or the global h2 size. */
.himadi-testimonials-section .himadi-eyebrow {
	font-size: 16px;
	margin-bottom: 4px;
}

.himadi-testimonials-section h2.wp-block-heading {
	font-size: 26px !important;
	margin-top: 0;
	margin-bottom: 0;
}

main#content.site-main {
	padding-bottom: 0 !important;
	margin-bottom: 0 !important;
}

.himadi-footer-info a {
	color: #2563eb;
}

.himadi-footer-info h2,
.himadi-footer-info .wp-block-heading {
	color: #1a1a1a;
	font-size: 18px;
	/* Trimmed from 16px -- same vertical-length reduction as the section
	   padding above. */
	margin-bottom: 10px;
}

.himadi-footer-cols {
	max-width: var(--tmpcoder-container-width, 1200px);
	margin: 0 auto;
	display: flex;
	flex-wrap: wrap;
	gap: 32px;
}

.himadi-footer-cols > div {
	flex: 1 1 220px;
	min-width: 0;
}

.himadi-footer-cols ul {
	list-style: none;
	margin: 0;
	padding: 0;
}

.himadi-footer-cols li {
	margin-bottom: 8px;
}

/* Digital Marketing's SEO/Content/Social/Email sub-pages, nested under it
   in the footer's "Services" menu -- indented with a left rule so they
   read as children of "Digital Marketing" rather than four more
   top-level entries, per request. */
.himadi-footer-cols li > ul {
	margin: 8px 0 12px 4px;
	padding-left: 14px;
	border-left: 2px solid #dbe4ff;
	list-style: none;
}

.himadi-footer-cols li > ul li {
	margin-bottom: 6px;
}

.himadi-footer-cols li > ul li a {
	font-size: 14px;
	color: #7c8aa5;
}

.himadi-footer-cols li > ul li a:hover {
	color: #2563eb;
}

/* Two phone numbers, each on its own line (himadi_footer_business_info()). */
.himadi-footer-phones a {
	display: inline-block;
	margin-top: 4px;
}

/* Was 4 plain text links (Facebook / Twitter / LinkedIn / WhatsApp) --
   replaced with icon-only links (inline SVGs, himadi_footer_business_info())
   plus a 5th for Instagram. aria-label on each <a> carries the accessible
   name now that there's no visible text. */
.himadi-footer-social {
	display: flex;
	gap: 12px;
	margin-top: 12px;
}

.himadi-footer-social a {
	display: inline-flex;
	align-items: center;
	justify-content: center;
	width: 36px;
	height: 36px;
	border-radius: 50%;
	background: #fff;
	color: #2563eb;
	box-shadow: 0 2px 8px rgba(0, 0, 0, 0.08);
	transition: background 200ms, color 200ms;
}

.himadi-footer-social a:hover {
	background: #2563eb;
	color: #fff;
}

/* Each platform's own brand color, same as the icons used before the
   uniform-blue icon-button treatment. */
.himadi-footer-social a[aria-label="Facebook"] { color: #1877f2; }
.himadi-footer-social a[aria-label="Twitter"] { color: #1da1f2; }
.himadi-footer-social a[aria-label="Instagram"] { color: #e4405f; }
.himadi-footer-social a[aria-label="LinkedIn"] { color: #0a66c2; }
.himadi-footer-social a[aria-label="WhatsApp"] { color: #25d366; }

.himadi-footer-social a[aria-label="Facebook"]:hover { background: #1877f2; color: #fff; }
.himadi-footer-social a[aria-label="Twitter"]:hover { background: #1da1f2; color: #fff; }
.himadi-footer-social a[aria-label="Instagram"]:hover { background: #e4405f; color: #fff; }
.himadi-footer-social a[aria-label="LinkedIn"]:hover { background: #0a66c2; color: #fff; }
.himadi-footer-social a[aria-label="WhatsApp"]:hover { background: #25d366; color: #fff; }

.himadi-footer-social svg {
	width: 18px;
	height: 18px;
	fill: currentColor;
}

@media (max-width: 767px) {
	.himadi-services-layout {
		flex-direction: column;
	}
}

/* Contact page — office-info/map column (now on the left) slides in from
   the left, form column (now on the right) slides in from the right, both
   meeting in the center. */
.himadi-slide-in-left {
	animation: himadi-timeline-from-left 700ms ease-out both;
	animation-play-state: paused;
}

.himadi-slide-in-right {
	animation: himadi-timeline-from-right 700ms ease-out both;
	animation-play-state: paused;
}

/* This is the actual bug behind every earlier "map and form appear
   together" report on the Contact page, through several rounds of JS
   timing fixes that all correctly changed WHEN .himadi-in-view got added
   but never fixed anything visible: himadi-timeline-from-left/-right were
   referenced above by name but never defined anywhere in this file. A CSS
   animation-name with no matching @keyframes is not an error — the browser
   silently ignores it and the element just renders at its normal static
   state, with the JS/animation-delay/play-state timing all working exactly
   as designed but with nothing for any of it to actually animate. Defining
   them now (a smaller, subtler travel distance than the hero/-far variant's
   220px, matching a content column rather than a full-width hero) is what
   makes this page's slide-in-left/-right classes do anything visible at
   all for the first time. */
@keyframes himadi-timeline-from-left {
	from {
		opacity: 0;
		transform: translateX(-80px);
	}
	to {
		opacity: 1;
		transform: translateX(0);
	}
}

@keyframes himadi-timeline-from-right {
	from {
		opacity: 0;
		transform: translateX(80px);
	}
	to {
		opacity: 1;
		transform: translateX(0);
	}
}


/* Home page "About Us" card — same left/right meet-in-center effect as
   above, but reusing the hero's larger 220px keyframes (himadi-hero-from-left/
   -right, further down) for a more dramatic "far" travel distance. Unlike
   the hero itself, this plays once via the generic .himadi-in-view
   paused/running switch rather than the hero's replay-every-scroll
   mechanism, so it's safe to use lower on the page. 220px was chosen
   because it's already proven not to trigger the "pushed fully outside the
   viewport" IntersectionObserver bug documented below — the hero uses the
   same distance successfully on this same page. */
.himadi-slide-in-left-far {
	animation: himadi-hero-from-left 700ms ease-out both;
	animation-play-state: paused;
}

.himadi-slide-in-right-far {
	animation: himadi-hero-from-right 700ms ease-out both;
	animation-play-state: paused;
}

/* Page hero (himadi_render_hero()) — title/subtitle travel much further
   than the timeline/contact-column slides above so the entrance reads
   clearly on a full-width hero instead of blending into the page load.
   The subtitle is held back slightly so the title visibly leads it in. */
/* Unlike every other entrance animation in this file (which plays once and
   stays revealed — see .himadi-in-view below), the hero replays every time
   it scrolls into view. That needs a different mechanism: the paused/running
   toggle used everywhere else only pauses/resumes at the current frame, so
   once a paused animation finishes it just stays parked on its end frame —
   toggling animation-play-state again doesn't restart it. Here the base
   state carries no animation property at all (just hidden), and
   .himadi-in-view is what assigns the animation — going from "no animation"
   to "animation: X" is a genuine value change, which is what makes the
   browser actually restart it from frame zero each time the class is
   re-added (see assets/js/himadi-scroll-reveal.js's persistent hero
   observer, which never unobserves and toggles the class both ways). */
.himadi-hero-slide-in-left,
.himadi-hero-slide-in-right {
	opacity: 0;
}

.himadi-hero-slide-in-left.himadi-in-view {
	animation: himadi-hero-from-left 900ms cubic-bezier(0.16, 1, 0.3, 1) both;
}

.himadi-hero-slide-in-right.himadi-in-view {
	animation: himadi-hero-from-right 900ms cubic-bezier(0.16, 1, 0.3, 1) both;
	animation-delay: 150ms;
}

@keyframes himadi-hero-from-left {
	from {
		opacity: 0;
		transform: translateX(-220px);
	}
	to {
		opacity: 1;
		transform: translateX(0);
	}
}

@keyframes himadi-hero-from-right {
	from {
		opacity: 0;
		transform: translateX(220px);
	}
	to {
		opacity: 1;
		transform: translateX(0);
	}
}

/* Generic scroll-trigger switch: JS adds this to any of the element-level
   entrance-animation classes above once the element enters the viewport.
   (The timeline's own .himadi-in-view rule further up handles its
   parent-marker → child-animates case separately.)
   !important is required here, not stylistic: JS adds .himadi-in-view
   directly to the target element, so it competes on CSS specificity against
   whatever selector paused that element's animation. A single-class pause
   selector (e.g. .blog-list-box) ties with this rule and source order
   happens to favor us, but a multi-class/descendant pause selector (e.g.
   .page-header .entry-title, two classes) outranks a plain .himadi-in-view
   and would stay paused forever regardless of source order — which is
   exactly what happened to the Blog/Case Study page titles before this was
   added. !important sidesteps needing every future pause selector kept
   deliberately lower-specificity than this one.
   Note: keep entrance-animation travel distances viewport-relative-safe
   (small px offsets, not vw/vh) — IntersectionObserver measures an
   element's post-transform position, so a large enough offset can push it
   fully outside the viewport and it will never register as intersecting,
   leaving it permanently stuck invisible (this happened with an earlier
   70vw "About Us" cross-in effect, since removed). */
.himadi-in-view {
	animation-play-state: running !important;
}

@media (prefers-reduced-motion: reduce) {
	.himadi-slide-in-left,
	.himadi-slide-in-right,
	.himadi-slide-in-left-far,
	.himadi-slide-in-right-far,
	.himadi-slide-in-down,
	.himadi-slide-in-up,
	.himadi-hero-slide-in-left,
	.himadi-hero-slide-in-right,
	.himadi-scale-in,
	.himadi-journey-rise {
		animation: none !important;
		opacity: 1 !important;
		transform: none !important;
	}
}

/* The office-info block (the_content() on the Contact page: an address
   heading/paragraph followed by a Google Maps embed) — reordered so the
   map appears first with the address centered underneath it, both
   centered as one unit rather than the map's default left-aligned,
   address-on-top layout. */
.himadi-offices {
	display: flex;
	flex-direction: column;
	align-items: center;
	text-align: center;
}

.himadi-offices > div {
	order: 1;
}

.himadi-offices h3,
.himadi-offices > p {
	order: 2;
}

.himadi-offices h3 {
	margin-top: 24px;
}

.himadi-offices iframe {
	display: block;
	/* Was the embed's own inline width="500px" height="300" -- shrunk per
	   explicit request. !important needed to beat those inline attributes
	   (width/height attributes behave like inline styles for replaced
	   elements such as iframe). */
	width: 400px !important;
	height: 240px !important;
	max-width: 100%;
	border-radius: 6px;
}

/* Intro-row/Services-sidebar "poke past the edges" layout (Digital
   Marketing's template-blank.php). The offset is only applied once the
   viewport is wide enough to actually have that much slack outside
   .himadi-container's own max-width — below 1300px the container already
   fills the full viewport width (minus its own 15px side padding), so a
   fixed negative margin had zero real room and clipped content past the
   true browser edge instead of "poking out" (confirmed by real overflow
   testing at 1024/1400px, not just eyeballing a wide desktop viewport). */
.himadi-intro-col {
	flex-basis: 64%;
	padding-right: 30px;
	box-sizing: border-box;
}

.himadi-services-col {
	flex-basis: 36%;
}

@media (min-width: 1300px) {
	.himadi-intro-col {
		flex-basis: calc(64% + 50px);
		flex-shrink: 0;
		margin-left: -50px;
	}

	.himadi-services-col {
		flex-basis: calc(36% + 50px);
		flex-shrink: 0;
	}
}

/* Single blog post — real left sidebar (himadi_single_post_markup(),
   replacing tmpcoder_single_post_markup() wholesale) with Categories/
   Recent Posts/Tags stacked in one column beside the post content,
   matching the vendor (Cleano/Spexo demo) sidebar's widget order. */
.himadi-single-post-layout {
	display: flex;
	align-items: flex-start;
	/* Sidebar (Categories/Recent Posts/Tags) sits before the content column
	   in markup (himadi-integration.php), so a smaller gap here pulls the
	   sidebar right, closer to the featured image/content column, instead
	   of leaving a wide empty strip between them. */
	gap: 15px;
	padding-top: var(--wp--preset--spacing--x-large);
	padding-bottom: var(--wp--preset--spacing--x-large);
}

.himadi-single-post-sidebar {
	flex: 0 0 280px;
	/* Shifts the sidebar box (Categories/Recent Posts/Tags) right, away
	   from the page's left edge and closer to the content column, instead
	   of changing the image itself. The content column is flex:1 so it
	   simply shrinks to absorb this, no overflow. */
	margin-left: 30px;
}

.himadi-single-post-content {
	flex: 1 1 0;
	min-width: 0;
}

/* tmpcoder_get_single_blog()'s own .page-content wrapper caps itself at
   var(--tmpcoder-container-width) (1200px) with its own 15px/15px side
   padding — meant for when it's the ONLY thing inside .site-main at full
   page width. Nested inside the narrower .himadi-single-post-content
   column instead, that max-width never binds (the column is already well
   under 1200px) but the 30px of left+right padding still does, eating
   into the column and leaving the featured image/content visibly
   narrower than the sidebar-to-content-edge width beside it — the
   .himadi-container that wraps the whole sidebar+content row already
   provides that outer framing padding once, so this inner copy is pure
   double-padding. */
.himadi-single-post-content .page-content {
	max-width: none !important;
	padding-left: 0 !important;
	padding-right: 0 !important;
}

/* Blog post featured image: the theme's own global .post .wp-post-image
   rule (tmpcoder-theme.css, 2 classes) was out-specifying a plain
   .blog-detail-img img selector (1 class + 1 element), so it silently
   won and kept the image at its 500px/400px/300px sizes no matter what
   was set here. Including .wp-post-image's own class in the selector
   below (2 classes + 1 element) out-specifies it instead. Scoped to
   .blog-detail-img so only single blog posts are affected. */
.blog-detail-img img.wp-post-image {
	max-height: 380px;
	width: 100%;
	/* object-fit:cover was cropping the bottom of the banner (the "A
	   GUIDE FOR HR LEADERS" text) to fill the fixed 380px height —
	   contain keeps the box size but shows the full image, uncropped. */
	object-fit: contain;
}
@media (max-width: 1399px) {
	/* height:auto (not a fixed max-height) so the image just scales down
	   with its own aspect ratio intact — a fixed max-height + object-fit:
	   cover here was cropping the bottom off the banner text. */
	.blog-detail-img img.wp-post-image {
		max-height: none;
		height: auto;
		width: 65%;
		margin: 0 auto;
	}
}

/* Blog post title and body text matched to the SEO/Digital-Marketing
   page (template-blank.php's hero h1 + .himadi-dm-page-content > p),
   verified via computed-style comparison between the two pages:
   - h1: same font-family/weight already; blog's h1 was 3px smaller
     (removed), unmargined (SEO has ~4.8px top/bottom) and left-aligned
     (SEO is centered) — all three now matched.
   - p: font-family/size/weight/line-height/color already matched the
     SEO page exactly; only text-align differed (SEO centered, blog
     left) — matched.
   - h3: SEO's .heading3 card headings are a fixed 22px vs the theme's
     global ~20px heading3 clamp used here — matched. */
.blog-detail-content h1 {
	text-align: left;
	/* body .site-main .page-content h1 { margin:0 } (style.css) outranks a
	   plain .blog-detail-content h1 selector (2 classes+2 elements vs 1
	   class+1 element) — !important needed to match the SEO page's
	   ~4.8px top/bottom heading margin instead of 0. */
	margin: 4.8px auto !important;
	/* Alignment/spacing/weight match the SEO page exactly (see above),
	   but the size itself is intentionally smaller than the SEO page's
	   ~47px — a blog post title doesn't need to be as large as a service
	   page's hero heading. */
	font-size: calc(var(--heading1-font-size) - 16px);
	/* Narrower column than the full content width, so the title/text
	   block reads as a compact column instead of stretching
	   edge-to-edge. Text within it is left-aligned (not centered) to
	   match the paragraphs/headings/lists below — multi-line centered
	   body copy is hard to read, and mixed alignment looked
	   inconsistent. */
	max-width: 70%;
}
.blog-detail-content p {
	color: #555;
	text-align: left;
	font-size: 12px;
	max-width: 70%;
	margin-left: auto;
	margin-right: auto;
}
.blog-detail-content h3 {
	font-size: 18px;
	text-align: left;
	max-width: 70%;
	margin-left: auto;
	margin-right: auto;
}
.blog-detail-content ul,
.blog-detail-content ol {
	text-align: left;
	max-width: 70%;
	/* body .site-main .blog-detail-description ul { margin:0 } (style.css,
	   2 classes+2 elements) outranks a plain .blog-detail-content ul
	   selector (1 class+1 element) and was zeroing out the auto margins
	   below, leaving the list flush at the far left instead of centered
	   like the paragraphs/heading above it — !important needed. */
	margin-left: auto !important;
	margin-right: auto !important;
	/* The theme's default ul padding-left (style.css) pushes the bullet
	   marker well left of where the box itself starts, so list text
	   looked shifted left of the paragraphs above it even though both
	   boxes share the same max-width/margin. list-style-position:inside
	   puts the bullet flush with the box edge instead, lining list text
	   up with the paragraph text above it. */
	padding-left: 0;
	list-style-position: inside;
}

/* The comment form (#comment-respond) sits inside a post whose content
   has an unclosed <div> (a known legacy-content issue — see this
   theme's CLAUDE.md), so in the rendered DOM it ends up nested inside
   .blog-detail-content even though it's written well after that block
   in the template source. That meant the .blog-detail-content p rule
   above (max-width:70%, margin:auto, text-align:left) was also hitting
   every <p> in this form (.comment-form-comment/-author/-email/-url
   are all <p> tags) — capping Comment's width:100% down to 70% and
   centering it, which left room for Name to sit on the same flex line
   instead of wrapping below it as the theme intends. Resetting that
   here, scoped to just the comment form. */
.comment-respond p {
	max-width: none !important;
	margin-left: 0 !important;
	margin-right: 0 !important;
}

/* Comment textarea: the whole #respond box (.comment-respond, below) is
   already narrowed to 75% width to match the author box's width/right
   edge — so the textarea itself just needs to fill 100% of that
   already-narrowed box (its default) rather than being shrunk again on
   top of it, which is what made it fall short of Website's/the author
   box's right edge. */
.comment-respond .comment-form-comment textarea {
	display: block;
	width: 100%;
}

/* Name/Email/Website inputs on the comment form: each column is 1/3 of
   the now-75%-wide #respond box (not the theme's original 33.33% of
   the FULL page width), so together they span the box's full width —
   Website's right edge lines up with the author box's right edge. A
   small margin-right gives clear gaps between the three boxes instead
   of them nearly touching the next label. */
.comment-respond .comment-form-author,
.comment-respond .comment-form-email,
.comment-respond .comment-form-url {
	width: 33.33% !important;
}
.comment-respond .comment-form-author input,
.comment-respond .comment-form-email input,
.comment-respond .comment-form-url input {
	width: 180px;
	margin-right: 20px;
}

/* Author box (.tmpcoder-author-box, the "hd_backoffice" strip) was
   stretching full-width via its own display:flex with no width set —
   narrowed here. The vendor selector (style.css, 3 classes + body
   element) outranks a plain .tmpcoder-author-box, so !important is
   needed. */
.tmpcoder-author-box {
	width: 75% !important;
	margin: 0 auto;
}

/* Author box + "Leave a Reply" comment form were left-aligned flush
   with the content column's edge, while the title/paragraphs/list
   above are centered in a narrower 70% column (see .blog-detail-content
   rules above) — shifted right to align under that column instead. */
.comment-respond {
	width: 75%;
	margin: 0 auto;
}

/* The theme's own "Tags:" pill row (tmpcoder_show_tags(), printed inline
   after the content) is now redundant — the same tags already show in
   the sidebar's "Tags" section to the left. */
.himadi-single-post-content .wp-post-tags {
	display: none;
}

/* Case study posts — centered main title only; the body's own paragraph
   blocks (Industry/Size/About the Company/etc.) are left-aligned below,
   not centered — unlike regular blog posts which are left-aligned
   throughout. himadi_single_post_markup() adds this modifier class only
   for posts in the "case-study" category. */
.himadi-single-post-layout--case-study .blog-detail-content h1 {
	text-align: center;
}

/* This particular case study's post_content is hand-authored with a
   literal <center> tag wrapping everything (forcing text-align:center at
   the HTML level, not just via CSS) plus its own inline color:#333 and
   font-family:Arial,sans-serif (a copy-paste artifact from wherever this
   was originally written) — !important needed to match it to the same
   font as a regular blog post's body text (.blog-detail-content p above:
   Poppins, 12px, #555) and to left-align the "Industry"/"Size"/"About the
   Company"/etc. paragraphs and bullet lists (reading badly centered)
   without fighting the <center> tag. The inline font-family specifically
   is why this read as a visibly different, un-Poppins typeface even
   after size/color were already matched. */
.himadi-single-post-layout--case-study .blog-detail-description,
.himadi-single-post-layout--case-study .blog-detail-description p,
.himadi-single-post-layout--case-study .blog-detail-description li {
	font-family: 'Poppins', sans-serif !important;
	font-size: 12px !important;
	color: #555 !important;
}

.himadi-single-post-layout--case-study .blog-detail-description p,
.himadi-single-post-layout--case-study .blog-detail-description ul,
.himadi-single-post-layout--case-study .blog-detail-description li {
	text-align: left !important;
}

/* This content also hand-inserts a standalone <br /> between every block
   (</p><br/><p>, </ul><br/><p>, ...) purely for spacing — on top of each
   <p>'s own margin, that produced a very tall gap between sections like
   "About the Company"/"Industry"/"Size". Hiding just those (via the
   adjacent-sibling selector, so a <br/> genuinely inside a <p> — e.g.
   the "Industry<br/>IT" label/value break — is untouched) and setting an
   explicit margin instead gives one consistent, smaller gap. */
.himadi-single-post-layout--case-study .blog-detail-description p + br,
.himadi-single-post-layout--case-study .blog-detail-description ul + br {
	display: none;
}

.himadi-single-post-layout--case-study .blog-detail-description p,
.himadi-single-post-layout--case-study .blog-detail-description ul {
	margin-bottom: 20px !important;
}

/* Every <li> here already starts with a literal "• " typed into the text
   itself (e.g. "<strong>• Flawless Academic Verification:</strong>") —
   on top of the browser's own list-style disc, each item was showing two
   dots. Removing the native marker leaves just the one already in the
   text. !important: style.css's "body .site-main .blog-detail-description
   ul li { list-style: disc }" outscores this on element-count even
   though this selector has the same number of classes. */
.himadi-single-post-layout--case-study .blog-detail-description li {
	list-style: none !important;
}

@media (max-width: 782px) {
	.himadi-single-post-layout {
		flex-direction: column;
	}

	.himadi-single-post-sidebar {
		flex-basis: auto;
		width: 100%;
	}
}

/* No per-section card/border here — plain white background with generous
   spacing between sections and a small colored underline accent below
   each heading, closer to the vendor demo's own plain (unboxed) sidebar
   than a bordered widget card. */
.himadi-post-sidebar-box {
	margin-bottom: 14px;
	font-size: 12.5px;
}

.himadi-post-sidebar-box h3 {
	margin: 0 0 6px;
	padding-bottom: 4px;
	font-size: 14px;
	font-weight: 700;
	border-bottom: 2px solid #2563eb;
	display: inline-block;
}

.himadi-post-sidebar-box ul {
	list-style: none;
	margin: 0;
	padding: 0;
}

.himadi-post-sidebar-box > ul > li {
	border-bottom: 1px solid #ececec;
	padding: 4px 0;
}

.himadi-post-sidebar-box > ul > li:first-child {
	padding-top: 0;
}

.himadi-post-sidebar-box > ul > li:last-child {
	border-bottom: none;
	padding-bottom: 0;
}

/* Categories list specifically: name left, post count right. */
.himadi-post-sidebar-categories > li {
	display: flex;
	align-items: baseline;
	justify-content: space-between;
	gap: 8px;
}

.himadi-post-sidebar-box a {
	color: #444;
	text-decoration: none;
	transition: color 150ms ease;
}

.himadi-post-sidebar-box a:hover {
	color: #2563eb;
}

.himadi-post-sidebar-count {
	color: #999;
	font-size: 11px;
	flex: 0 0 auto;
}

.himadi-post-sidebar-recent li {
	display: flex;
	align-items: flex-start;
	gap: 8px;
}

.himadi-post-sidebar-recent-thumb {
	flex: 0 0 34px;
}

.himadi-post-sidebar-recent-thumb img {
	display: block;
	width: 34px;
	height: 34px;
	object-fit: cover;
	border-radius: 6px;
}

.himadi-post-sidebar-recent-body {
	display: flex;
	flex-direction: column;
	gap: 1px;
	min-width: 0;
}

.himadi-post-sidebar-recent-title {
	font-size: 11px;
	line-height: 1.25;
	font-weight: 600;
	color: #1a1a1a !important;
}

.himadi-post-sidebar-recent-title:hover {
	color: #2563eb !important;
}

.himadi-post-sidebar-recent-readmore {
	font-size: 10px;
	font-weight: 700;
	letter-spacing: 0.05em;
	text-transform: uppercase;
	color: #2563eb !important;
}

.himadi-post-sidebar-recent-readmore:hover {
	text-decoration: underline;
}

.himadi-post-sidebar-tag-cloud {
	display: flex;
	flex-wrap: wrap;
	gap: 4px;
}

.himadi-post-sidebar-tag-cloud a {
	border: 1px solid #dbe4ff;
	background: #eef2ff;
	color: #37415c !important;
	border-radius: 4px;
	padding: 2px 6px;
	font-size: 11px;
	transition: background-color 150ms ease;
}

.himadi-post-sidebar-tag-cloud a:hover {
	background: #e0e7ff;
	text-decoration: none;
}

/* Blog listing: tmpcoder_archive() (vendor code) prints its own
   "<header class="page-header"><h1>Blog</h1></header>" above the post
   grid -- now redundant since himadi_render_hero() (added in archive.php)
   already shows the "Blog" title in the hero photo above it, leaving this
   as just an empty off-white block before the posts. */
body.blog .page-header {
	display: none;
}

