/* ---- Prime1 additions: Services / Contact blocks (hand-written — main.css above this line is a compiled Tailwind build with no live build step, so new component classes are added here directly instead of as Tailwind utilities). ---- */
.scroll-mt-24{scroll-margin-top:6rem}
.service-card{border-radius:1rem;border:1px solid rgba(24,22,21,.1);background:#fff;padding:2rem 1.75rem;transition:box-shadow .15s cubic-bezier(.4,0,.2,1),transform .15s cubic-bezier(.4,0,.2,1)}
.service-card:hover{box-shadow:0 20px 45px -24px rgba(0,0,0,.25);transform:translateY(-2px)}
.service-icon{display:inline-flex;align-items:center;justify-content:center;height:3.25rem;width:3.25rem;border-radius:9999px;background:rgba(184,134,11,.1);color:#B8860B}
.contact-grid{grid-template-columns:1fr}
@media (min-width:1024px){.contact-grid{grid-template-columns:0.9fr 1.1fr}}
.contact-info-item{display:flex;align-items:flex-start;gap:.65rem;font-size:.875rem;line-height:1.5rem;color:#5B5551}
.form-field{display:flex;flex-direction:column;gap:.4rem}
.form-label{font-size:.75rem;font-weight:600;letter-spacing:.02em;color:#181615}
.form-control{width:100%;border-radius:.75rem;border:1px solid rgba(24,22,21,.15);background:#fff;padding:.7rem .9rem;font-size:.875rem;font-family:Poppins,ui-sans-serif,system-ui,sans-serif;color:#181615;transition:border-color .15s ease,box-shadow .15s ease}
.form-control:focus{outline:none;border-color:#B8860B;box-shadow:0 0 0 3px rgba(184,134,11,.15)}
textarea.form-control{resize:vertical;min-height:6.5rem}
.form-alert{border-radius:.75rem;padding:.9rem 1.1rem;font-size:.875rem;margin-bottom:1.25rem}
.form-alert-success{background:rgba(34,139,34,.08);color:#1f7a1f;border:1px solid rgba(34,139,34,.25)}
.form-alert-error{background:rgba(184,11,11,.06);color:#a31414;border:1px solid rgba(184,11,11,.2)}
.map-frame{position:relative;width:100%;padding-top:60%;border-radius:1rem;overflow:hidden;border:1px solid rgba(24,22,21,.1)}
.map-frame iframe{position:absolute;inset:0;width:100%;height:100%;border:0}

/* Real content styling for the .prime1-prose wrapper used around every ACF wysiwyg
   field on the site (Overview/Architecture/Interiors body copy, About, Rich Text
   layout, etc.) — until now this class carried no rules of its own, so any heading,
   list, or link a client typed into a wysiwyg field rendered in the browser's bare
   defaults instead of matching the site's type system. */
.prime1-prose p{margin:0 0 1.1em}
.prime1-prose p:last-child{margin-bottom:0}
.prime1-prose h2,.prime1-prose h3,.prime1-prose h4{font-family:"Playfair Display",ui-serif,Georgia,serif;color:#181615;font-weight:600;line-height:1.3}
.prime1-prose h2{font-size:1.375rem;margin:1.75em 0 .6em}
.prime1-prose h3{font-size:1.15rem;margin:1.6em 0 .55em}
.prime1-prose h4{font-size:1rem;margin:1.4em 0 .5em}
.prime1-prose h2:first-child,.prime1-prose h3:first-child,.prime1-prose h4:first-child{margin-top:0}
.prime1-prose ul,.prime1-prose ol{margin:0 0 1.1em;padding-left:1.25em;display:flex;flex-direction:column;gap:.45em}
.prime1-prose ul{list-style:disc}
.prime1-prose ol{list-style:decimal}
.prime1-prose li{padding-left:.15em}
.prime1-prose a{color:#B8860B;text-decoration:underline;text-underline-offset:2px}
.prime1-prose a:hover{color:#9a7009}
.prime1-prose strong{font-weight:600;color:#181615}
.prime1-prose blockquote{margin:0 0 1.1em;padding-left:1em;border-left:2px solid rgba(184,134,11,.4);color:#5B5551;font-style:italic}

/* Blog listing (page-blog.php) card + WordPress core the_posts_pagination()
   markup — pagination renders a bare <nav class="navigation pagination"> with
   plain <a class="page-numbers"> links by default, so it needs its own rules
   here (same reasoning as the other hand-written additions in this file) to
   match the site's gold/pill design language instead of showing unstyled
   browser-default link text. */
.card-blog{overflow:hidden;border-radius:1rem;background:#fff;box-shadow:0 10px 35px -18px rgba(0,0,0,.25);display:flex;flex-direction:column}
.card-blog .card-blog-excerpt{display:-webkit-box;-webkit-line-clamp:3;-webkit-box-orient:vertical;overflow:hidden}
/* Targets the .nav-links wrapper div core always renders inside
   get_the_posts_pagination()'s <nav>, regardless of the 'class' arg passed —
   so this styles the_posts_pagination() output on both page-blog.php AND
   archive-project.php's existing (previously unstyled) call the same way. */
.nav-links{display:flex;flex-wrap:wrap;align-items:center;justify-content:center;gap:.5rem}
.nav-links .page-numbers{display:inline-flex;align-items:center;justify-content:center;min-width:2.75rem;height:2.75rem;padding:0 .5rem;border-radius:9999px;border:1px solid rgba(24,22,21,.12);font-size:.8125rem;font-weight:600;color:#181615;background:#fff;transition:background-color .15s ease,color .15s ease,border-color .15s ease}
.nav-links a.page-numbers:hover{background:#B8860B;border-color:#B8860B;color:#fff}
.nav-links .page-numbers.current{background:#B8860B;border-color:#B8860B;color:#fff}
.nav-links .page-numbers.dots{border-color:transparent;background:transparent}
.nav-links .page-numbers.prev,.nav-links .page-numbers.next{padding:0 1.1rem}
.sr-only{position:absolute;width:1px;height:1px;padding:0;margin:-1px;overflow:hidden;clip:rect(0,0,0,0);white-space:nowrap;border:0}

/* Tailwind-utility backfills for page-blog.php / single.php (the blog
   listing + single-post templates): main.css is a frozen compiled Tailwind
   build containing only the classes the ORIGINAL site templates used, so any
   utility class not already present there — even a completely standard one
   like pt-6 or max-w-3xl — silently produces no CSS at all (the element just
   falls back to whatever size/spacing it inherits, which is how the blog
   post body text first shipped far too large: text-[15px] is an
   arbitrary-value class that was never in the compiled build, so it had zero
   effect and the paragraph text rendered at the page's large ambient
   font-size instead). These are the plain-utility equivalents that were
   missing, added here exactly like Tailwind would generate them. */
.pt-6{padding-top:1.5rem}
.h-52{height:13rem}
.h-72{height:18rem}
.opacity-60{opacity:.6}
.max-w-3xl{max-width:48rem}
.\!py-2\.5{padding-top:.625rem!important;padding-bottom:.625rem!important}
.\!px-4{padding-left:1rem!important;padding-right:1rem!important}
@media (min-width:640px){.sm\:h-96{height:24rem}}

/* Same missing-utility issue as above, found while adding the "Watch Video"
   modal (template-parts/hero-full.php): bg-black/92 was already used by the
   single-project.php gallery lightbox, but was never in the compiled build
   either, so that lightbox's dark backdrop has silently been rendering with
   NO background at all — this backfill fixes both it and the new modal. */
.bg-black\/92{background-color:rgba(0,0,0,.92)}
.aspect-video{aspect-ratio:16/9}

/* Home/Landing's single-viewport hero (page-home.php, page-landing.php) sets
   BOTH <body> and its wrapping <section> to an explicit h-[100dvh] — by
   design, so the hero never scrolls. WordPress prints its own 32px admin
   toolbar (46px on narrow/mobile widths) for logged-in users and pushes the
   whole document down for it via `html{margin-top:32px!important}`. That
   pushes this already-100dvh-tall hero an extra 32-46px past the real
   viewport, and because <body> also has overflow-hidden (deliberately, so
   the hero can't scroll), the overflow is silently clipped with no
   scrollbar — clipping exactly the bottom-anchored elements first: the
   "Developed by GENMAG" credit and the floating "Let's Talk" card. WordPress
   adds the "admin-bar" class to <body> whenever that toolbar is showing, so
   scoping the hero's height to subtract it there keeps the whole hero (and
   everything anchored to its edges) inside the real visible viewport
   whether or not a visitor is logged in. */
body.admin-bar.h-\[100dvh\],
body.admin-bar .h-\[100dvh\]{height:calc(100dvh - 32px)}
@media (max-width:782px){
	body.admin-bar.h-\[100dvh\],
	body.admin-bar .h-\[100dvh\]{height:calc(100dvh - 46px)}
}

/* Contact Form 7 ("Prime1 Contact Form", template-parts/render/contact.php)
   renders its own wrapper spans and classes around each field and its own
   response banner — these rules make that default CF7 markup match the
   .form-field/.form-control/.form-alert look this theme already used for
   the form it replaced, instead of showing CF7's own unstyled defaults. */
.wpcf7-form-control-wrap{display:block}
.wpcf7-not-valid-tip{display:block;margin-top:.35rem;font-size:.75rem;color:#a31414}
.form-control.wpcf7-not-valid{border-color:#a31414}
.wpcf7-response-output{border-radius:.75rem;padding:.9rem 1.1rem;font-size:.875rem;margin:0 0 1.25rem;border:1px solid transparent}
.wpcf7-mail-sent-ok{background:rgba(34,139,34,.08);color:#1f7a1f;border-color:rgba(34,139,34,.25)}
.wpcf7-validation-errors,.wpcf7-mail-sent-ng,.wpcf7-spam-blocked,.wpcf7-aborted{background:rgba(184,11,11,.06);color:#a31414;border-color:rgba(184,11,11,.2)}
/* [submit] renders a plain <input type="submit">, which can't hold the old
   button's inline SVG arrow — this reproduces the same arrow glyph via a
   background-image on a generated ::after box instead. */
.wpcf7-submit.btn-primary::after{content:"";display:inline-block;width:14px;height:14px;margin-left:.5rem;vertical-align:-2px;background-repeat:no-repeat;background-position:center;background-size:contain;background-image:url("data:image/svg+xml,%3Csvg xmlns='http://www.w3.org/2000/svg' viewBox='0 0 24 24' fill='none' stroke='white' stroke-width='2.2'%3E%3Cpath stroke-linecap='round' stroke-linejoin='round' d='M9 5l7 7-7 7'/%3E%3C/svg%3E")}
/* The old button was w-full sm:w-auto (full-width on mobile, shrink-to-fit
   from the sm breakpoint up). CF7's [submit ... class:sm:w-auto] tag option
   strips the colon out of any class value it's given, corrupting that
   Tailwind class into "smw-auto" — so this reproduces the sm:w-auto half
   directly instead of relying on a CF7 class option for it. */
@media (min-width:640px){.wpcf7-submit.btn-primary{width:auto}}

