.single-event .top .date {
	display: none;
}

.s-solutions-graphic .box.box-blue .logo img{
	max-width: 200px;
}

.single-job .single__sidebar .add-info:nth-of-type(2) img,
.single-post .single__sidebar .add-info:nth-of-type(2) img{
	max-height: 60px;
	object-fit: contain;
	object-position: left center;
}

.page-main.single .content_wrapper .single__sidebar .add-info .logo img{
  max-height: 60px;
  object-fit: contain;
  object-position: left center;
}

.page-main.single .back-band{
	margin-top: 36px;
}

/* ============================================================================
   Content-area email subscription prompt
   A reusable dark call-to-action band that wraps a Gravity Forms block.
   ----------------------------------------------------------------------------
   WHERE THIS GOES:  Appearance → Customize → Additional CSS

   Not a page-builder or code-block CSS field — those are usually sandboxed to
   their own container and cannot reach a sibling block. This file is fully
   self-contained: it declares its own custom properties and every selector is
   namespaced, so it can live site-wide without touching anything else.

   ----------------------------------------------------------------------------
   HOW TO USE — one class, on a Group block

   Add a Group block, then in the block sidebar:
       Advanced → Additional CSS class(es):  content-area-email-subscription-prompt
       Advanced → HTML anchor:               (optional, e.g. subscribe)
       Alignment:                            Full width

   Put these inside the Group, in any order:

       Paragraph      →  small accent line   (needs the __eyebrow class, optional)
       Heading H2–H4  →  the headline        (no class needed)
       Paragraph      →  supporting copy     (no class needed)
       Gravity Forms  →  the form            (no class needed)

   On the Gravity Forms block set: Form title OFF, Form description OFF, AJAX ON.

   ----------------------------------------------------------------------------
   CLASSES

   content-area-email-subscription-prompt             the Group block (required)
   content-area-email-subscription-prompt__eyebrow    small uppercase accent line
   content-area-email-subscription-prompt--light      white ground instead of dark

   Only the first is required. Headings and paragraphs are matched by element,
   so there is nothing else to remember or mistype.
   ========================================================================== */

.content-area-email-subscription-prompt {
  /* ---- Palette ---- */
  --email-prompt-bg:        #160142;   /* Midnight */
  --email-prompt-fg:        #FFFFFF;
  --email-prompt-copy:      rgba(255, 255, 255, .88);  /* 13.5:1 on Midnight */
  --email-prompt-accent:    #97FFC1;   /* Mint — 15.6:1 on Midnight */
  --email-prompt-invalid:   #FF766C;   /* Vermillion — 6.4:1 on Midnight */
  --email-prompt-error-fg:  #B3322A;   /* 5.9:1 on the error surface below */
  --email-prompt-error-bg:  #FFE8E7;
  --email-prompt-btn-hover: #FFFFFF;   /* see note on the hover rule */
  --email-prompt-btn-hover-fg: #0e0129;

  /* ---- Metrics ---- */
  --email-prompt-gutter:    56px;
  --email-prompt-pad-block: 72px;
  --email-prompt-measure:   640px;
  --email-prompt-h-size:    36px;
  --email-prompt-font: 'DM Sans', Verdana, -apple-system, BlinkMacSystemFont,
                       'Segoe UI', Roboto, sans-serif;
}

/* The class is doubled for specificity (0,2,0). Cheap insurance against a theme
   or block-supports rule setting a background on .wp-block-group at (0,1,0). */
.content-area-email-subscription-prompt.content-area-email-subscription-prompt {
  background: var(--email-prompt-bg);
  padding: var(--email-prompt-pad-block) var(--email-prompt-gutter);
  margin: 0;
}

.content-area-email-subscription-prompt > * {
  max-width: var(--email-prompt-measure);
  margin-left: auto;
  margin-right: auto;
  text-align: center;
}
.content-area-email-subscription-prompt > * { margin-top: 0; margin-bottom: 18px; }
.content-area-email-subscription-prompt > *:last-child { margin-bottom: 0; }

/* ---------- Headline ---------- */
/* Matched by element so no class is needed. H2 is the expected level; H3 and H4
   are accepted so the pattern can sit under an existing heading hierarchy. */
/* Descendant, not `>`: a Group with certain layout settings can put an inner
   container between the wrapper and its children, and the rule would silently
   stop matching.
   !important on colour only: the block editor writes an inline
   style="color:…" on headings and paragraphs (from block supports or a
   theme.json default), and an inline style beats any stylesheet rule that
   isn't !important. Everything else here is left overridable on purpose. */
.content-area-email-subscription-prompt h2,
.content-area-email-subscription-prompt h3,
.content-area-email-subscription-prompt h4 {
  font-family: var(--email-prompt-font);
  font-weight: 800;
  font-size: var(--email-prompt-h-size);
  line-height: 1.2;
  letter-spacing: -.8px;
  color: var(--email-prompt-fg) !important;
  max-width: 26ch;
  text-wrap: balance;
}

/* ---------- Supporting copy ---------- */
/* The :not() chain does two jobs: it keeps this rule off Gravity Forms' own
   paragraphs, and it excludes the eyebrow. Excluding the eyebrow matters —
   these two rules used to compete, and each :not() adds specificity, so this
   selector quietly grew to (0,4,1) and started beating the eyebrow rule, which
   then rendered as body copy. Mutually exclusive selectors can't have that
   argument. */
.content-area-email-subscription-prompt p:not(.content-area-email-subscription-prompt__eyebrow):not(:has(~ h2)):not(:has(~ h3)):not(:has(~ h4)):not(.gform_description):not(.gform_required_legend):not([class*="gfield"]) {
  font-family: var(--email-prompt-font);
  font-weight: 400;
  font-size: 17px;
  line-height: 1.55;
  color: var(--email-prompt-copy) !important;
  max-width: 56ch;
  text-wrap: pretty;
}

/* ---------- Optional eyebrow ---------- */
/* The one opt-in class. The base class is doubled here on purpose: the generic
   paragraph rule above is (0,2,1), and a single base class here would only be
   (0,2,0) — the generic rule would win and the eyebrow would render as body
   copy. Doubling makes this (0,3,0), which takes it, for any element type. */
/* Two ways to be an eyebrow. The explicit class is the documented one; the
   `:has(~ h2)` selectors catch a paragraph that sits BEFORE the heading, which
   is what an eyebrow always is. That means the class is optional in the normal
   layout, and a band with no eyebrow still renders its single paragraph as body
   copy — which `p:first-of-type` alone would have got wrong. */
.content-area-email-subscription-prompt p:has(~ h2),
.content-area-email-subscription-prompt p:has(~ h3),
.content-area-email-subscription-prompt p:has(~ h4),
.content-area-email-subscription-prompt .content-area-email-subscription-prompt__eyebrow.content-area-email-subscription-prompt__eyebrow {
  font-family: var(--email-prompt-font);
  font-weight: 700;
  font-size: 12px;
  line-height: 1.3;
  letter-spacing: 1.6px;
  text-transform: uppercase;
  color: var(--email-prompt-accent) !important;
  max-width: none;
}

/* ---------- Light variant ---------- */
/* Add content-area-email-subscription-prompt--light alongside the base class to
   put the pattern on a white ground instead. Only the tokens change. */
.content-area-email-subscription-prompt--light {
  --email-prompt-bg:     #FFFFFF;
  --email-prompt-fg:     #160142;
  --email-prompt-copy:   #3a3550;      /* 11.6:1 on white */
  --email-prompt-accent: #007A94;      /* DarkTeal — 4.99:1 on white.
                                          Brand Teal #0092B2 is only 3.65:1 and
                                          must not carry 12px text. */
  --email-prompt-invalid:      #B3322A;
  --email-prompt-btn-hover:    #0e0129;
  --email-prompt-btn-hover-fg: #FFFFFF;
}

/* ============================================================ GRAVITY FORMS */

/* Only the block margins are reset. `margin: 0` here would also wipe the `auto`
   side margins inherited from the `> *` centring rule above — which matters when
   the class is applied straight to the Gravity Forms block, making .gform_wrapper
   a direct child. That rendered the form left-aligned instead of centred. */
.content-area-email-subscription-prompt .gform_wrapper {
  margin-top: 0;
  margin-bottom: 0;
}

/* Belt and braces — GF versions nest these differently. The block's own
   "Form title / Form description: off" toggles are still the better fix. */
.content-area-email-subscription-prompt .gform_heading,
.content-area-email-subscription-prompt .gform_title,
.content-area-email-subscription-prompt .gform_description,
.content-area-email-subscription-prompt .gform_required_legend { display: none; }

/* GF's orbital theme lays fields on a 12-column grid. One row is all this
   needs, so override to flex — the gfield--width-* span classes then no-op. */
.content-area-email-subscription-prompt .gform_fields {
  display: flex;
  flex-wrap: wrap;
  gap: 12px;
  align-items: flex-start;
  justify-content: center;
  grid-template-columns: none;
}
.content-area-email-subscription-prompt .gfield {
  margin: 0;
  padding: 0;
  min-width: 0;
}
.content-area-email-subscription-prompt .gfield--type-email,
.content-area-email-subscription-prompt .gfield--type-text { flex: 0 1 300px; }
.content-area-email-subscription-prompt .gfield--type-submit { flex: 0 0 auto; }

/* The placeholder carries the label. Clip it rather than display:none —
   display:none would strip the accessible name for screen readers. */
.content-area-email-subscription-prompt .gfield_label {
  position: absolute;
  width: 1px; height: 1px;
  margin: -1px; padding: 0;
  overflow: hidden;
  clip: rect(0 0 0 0);
  white-space: nowrap;
  border: 0;
}

/* Invisible reCAPTCHA: the container must stay rendered for the widget to
   execute, so it is clipped rather than removed. position:absolute is doing real
   work — as a zero-width flex ITEM it still earned a 12px `gap`, which pushed the
   whole row 6px right of centre. Out of flow, it contributes nothing. The badge
   is position:fixed and unaffected. */
.content-area-email-subscription-prompt .gfield--type-captcha {
  position: absolute;
  width: 1px;
  height: 1px;
  margin: -1px;
  padding: 0;
  overflow: hidden;
  clip: rect(0 0 0 0);
  border: 0;
}

/* GF puts the submit EITHER inline (a Submit field inside .gform_fields) OR in
   .gform_footer — never both, depending on the form's "Submit Button Location"
   setting. So the footer is neutralised, never hidden: hiding it would make the
   button vanish for anyone whose form is set to "End of Form", which is a
   miserable thing to debug. */
.content-area-email-subscription-prompt .gform_footer {
  margin: 0;
  padding: 0;
}

/* Submit — the theme owns its resting state. Most themes set
   input[type=submit] with !important on background, colour, size and radius;
   fighting that produces a button matching neither the theme nor the page. */
.content-area-email-subscription-prompt input[type="submit"] { cursor: pointer; }

/* Themes commonly hover submits to a dark colour, which is invisible against a
   dark band. This is the one place !important is answered in kind, and the
   selector deliberately mirrors the shape themes use for GF submits —
   specificity (0,4,2) — because a shorter selector with !important still loses. */
.content-area-email-subscription-prompt .gform_wrapper form input[type="submit"][id*="gform_submit_button_"]:hover,
.content-area-email-subscription-prompt .gform_wrapper form input[type="submit"][id*="gform_submit_button_"]:focus-visible {
  background-color: var(--email-prompt-btn-hover) !important;
  border-color: var(--email-prompt-btn-hover) !important;
  color: var(--email-prompt-btn-hover-fg) !important;
}
.content-area-email-subscription-prompt input[type="submit"]:focus-visible {
  outline: 2px solid var(--email-prompt-btn-hover);
  outline-offset: 2px;
}

/* ---------- Validation ---------- */
/* The error summary keeps a light surface so its red text stays legible; only
   text sitting directly on the band's ground is inverted. */
.content-area-email-subscription-prompt .gform_validation_errors {
  margin: 0 auto 14px;
  padding: 12px 14px;
  max-width: 420px;
  border: 1px solid var(--email-prompt-invalid);
  border-left-width: 4px;
  border-radius: 6px;
  background: var(--email-prompt-error-bg);
  box-shadow: none;
  text-align: left;
}
.content-area-email-subscription-prompt .gform_validation_errors > h2,
.content-area-email-subscription-prompt .gform_submission_error {
  margin: 0;
  max-width: none;
  font: 700 15px/1.4 var(--email-prompt-font);
  letter-spacing: normal;
  color: var(--email-prompt-error-fg);
  text-align: left;
}
.content-area-email-subscription-prompt .gfield_validation_message,
.content-area-email-subscription-prompt .validation_message {
  margin: 6px 0 0;
  padding: 0;
  border: 0;
  background: none;
  font: 400 14px/1.45 var(--email-prompt-font);
  color: var(--email-prompt-invalid);
  text-align: left;
}

/* ---------- Confirmation ---------- */
.content-area-email-subscription-prompt .gform_confirmation_message {
  margin: 0;
  font: 500 17px/1.5 var(--email-prompt-font);
  color: var(--email-prompt-accent);
}

/* ================================================================== MOBILE */
@media (max-width: 900px) {
  .content-area-email-subscription-prompt {
    --email-prompt-gutter: 32px;
    --email-prompt-h-size: 30px;
  }
}
@media (max-width: 600px) {
  .content-area-email-subscription-prompt {
    --email-prompt-gutter: 20px;
    --email-prompt-pad-block: 56px;
    --email-prompt-h-size: 28px;
  }
  .content-area-email-subscription-prompt .gform_fields {
    flex-direction: column;
    align-items: stretch;
  }
  /* In a column flex container the flex-basis above is read as a HEIGHT —
     without this reset the email field becomes a 300px tall box. */
  .content-area-email-subscription-prompt .gfield--type-email,
  .content-area-email-subscription-prompt .gfield--type-text { flex: 0 0 auto; }
  .content-area-email-subscription-prompt .gfield--type-submit { width: 100%; }
  .content-area-email-subscription-prompt input[type="submit"] { width: 100%; }
}