/*
Theme Name: Idia
Theme URI: 
Author: Tobi Adeyinka
Author URI: 
Description: Idia is a block theme built on the belief that craft speaks for itself. Minimal, fast, and typography-led, it gives studios and product teams a clean foundation to build on — fully editable in the WordPress Site Editor.
Requires at least: 7.0
Tested up to: 7.0
Requires PHP: 7.3
Version: 1.7
License: GNU General Public License v3 or later
License URI: https://www.gnu.org/licenses/gpl-2.0.html
Text Domain: idia
Tags: blog, portfolio, entertainment, grid-layout, one-column, two-columns, three-columns, four-columns, block-patterns, block-styles, custom-logo, custom-menu, editor-style, featured-images, full-site-editing, full-width-template, rtl-language-support, style-variations, template-editing, theme-options, translation-ready, wide-blocks

Idia WordPress Theme, (C) 2026 Mike McAlister.
Idia is distributed under the terms of the GNU GPL.
*/

/* CSS Reset
---------------------------------------------------------------------------- */

*,
*::before,
*::after {
	box-sizing: inherit;
}

html {
	box-sizing: border-box;
	-moz-osx-font-smoothing: grayscale;
	-webkit-font-smoothing: antialiased;
}

b,
strong {
	font-weight: var(--wp--custom--font-weight--semi-bold);
}

ol,
ul {
	padding: 0;
}

ol:where(:not([class*="wp-block"])),
ol:where(.wp-block-list),
ul:where(:not([class*="wp-block"])),
ul:where(.wp-block-list) {
	padding-inline-start: var(--wp--preset--spacing--24);
}

div[class*="wp-block-"] figcaption {
	color: var(--wp--preset--color--secondary);
	font-size: var(--wp--preset--font-size--x-small);
	margin-bottom: 0;
	margin-top: 20px;
	text-align: center;
}

img,
figure {
	max-width: 100%;
	height: auto;
}

/* Temporary fix for text-decoration-thickness in Firefox */
@-moz-document url-prefix() {
	a {
		text-decoration-thickness: .1rem !important;
	}
}

/* Standardize form styling
--------------------------------------------- */

input,
button,
textarea,
select {
	font: inherit;
}

input[type="button"],
input[type="email"],
input[type="search"],
input[type="submit"],
input[type="text"],
textarea {
	-webkit-appearance: none;
	appearance: none;
}

input:not([type="submit"]):not([type="radio"]),
select,
textarea,
.wp-block-post-comments-form input:not([type="submit"]):not([type="checkbox"]):not([type="radio"]),
.wp-block-post-comments-form textarea {
	color: var(--wp--preset--color--main);
	border-radius: 5px;
	border: solid 1px color-mix(in srgb, var(--wp--preset--color--tertiary) 100%, var(--wp--preset--color--main) 20%);
	padding: .5em 1em;
	font-size: var(--wp--preset--font-size--small);
	background-color: #fff;
	box-shadow: 
		0 1px 2px rgba(0, 0, 0, 0.02),
		0 0.5px 1px rgba(0, 0, 0, 0.04);
}

input:focus-visible,
textarea:focus-visible,
select:focus-visible {
	outline-color: var(--wp--preset--color--main);
	outline-offset: 1px;
}

input[type="checkbox"],
input[type="image"],
input[type="radio"] {
	width: auto;
}

select {
	-webkit-appearance: none;
	appearance: none;
	background: var(--wp--preset--color--base) url(data:image/svg+xml;base64,PHN2ZyB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciIHZpZXdCb3g9IjAgMCAyNCAyNCIgZmlsbD0ibm9uZSIgc3Ryb2tlPSJibGFjayIgc3Ryb2tlLXdpZHRoPSIyIiBzdHJva2UtbGluZWNhcD0icm91bmQiIHN0cm9rZS1saW5lam9pbj0icm91bmQiIGNsYXNzPSJmZWF0aGVyIGZlYXRoZXItY2hldnJvbi1kb3duIj48cG9seWxpbmUgcG9pbnRzPSI2IDkgMTIgMTUgMTggOSI+PC9wb2x5bGluZT48L3N2Zz4=) no-repeat;
    background-size: 16px;
    background-position: calc(100% - 12px) 50%;
	padding-right: 2.2em;
}

label {
	width: 100%;
	display: block;
}

::placeholder {
	color: var(--wp--preset--color--secondary);
	font-size: var(--wp--preset--font-size--small);
	opacity: 0.75;
}

/* Helper styles
---------------------------------------------------------------------------- */

a.more-link {
	display: block;
}

/* Inline code */
*:not(.wp-block-code) > code {
	background-color: var(--wp--preset--color--tertiary);
	padding: 3px 5px;
	position: relative;
	border-radius: 3px;
}

.wp-block-categories {
	position: relative;
}

/* Remove margin on term description on archive pages */
.wp-block-term-description p:last-child {
	margin-bottom: 0;
}

/* Remove last separator on post list */
.remove-border-and-padding .wp-block-post-template li:last-child .wp-block-separator {
	display: none;
}

/* Hide post meta div if no tags assigned */
.single .wp-block-group:has(> .post-meta:empty) {
	display: none;
}

.wp-block-group:empty:has(+ .comment-respond) {
	display: none;
}

.row-logos > figure {
	flex-shrink: 1 !important;
}

/* Mobile helper classes */

@media (max-width: 781px) {
	.idia-hide-on-mobile {
		display: none;
	}

	.idia-unstick-mobile {
		position: static;
	}

	header:has(>.idia-unstick-mobile) {
		position: static;
	}
}

/* Table
--------------------------------------------- */

.wp-block-table table {
	background: var(--wp--preset--color--base);
	border-radius: 5px;
	border: solid 1px var(--wp--preset--color--border-light);
	font-size: var(--wp--preset--font-size--x-small);
}
.wp-block-table.is-style-stripes {
	border-bottom: none;
}

.wp-block-table.is-style-stripes tbody tr:nth-child(odd) {
	background-color: var(--wp--preset--color--tertiary);
}

.wp-block-table td, 
.wp-block-table th,
.wp-block-table thead {
	border: none;
	border-bottom: solid 1px color-mix(in srgb, var(--wp--preset--color--border-light) 50%, var(--wp--preset--color--base) 5%);
}

.wp-block-table th,
.wp-block-table tfoot {
	text-align: left;
	background-color: color-mix(in srgb, var(--wp--preset--color--tertiary) 75%, var(--wp--preset--color--base) 5%);
}

.wp-block-table td, 
.wp-block-table th {
	padding: .8em 1em;
}

.wp-block-table tfoot {
	border-top: solid 1px var(--wp--preset--color--border-light);
}

.wp-block-table tfoot td {
	border-bottom: none;
}

/* Retheme — breakpoint overrides
---------------------------------------------------------------------------- */
/* theme.json cannot express media queries, so the scale shifts live here.
   Two selectors are required, for two different reasons:

   - `html body` (0,0,2) for properties that are ONLY ever consumed directly
     as `var(--wp--custom--X)` — currently --rail, --section-inset,
     --section-inset-sm and --radius--*. WordPress prints global-styles custom
     properties on body, and a `:root` override loses to them regardless of
     stylesheet order, so `html body` is required for these.

   - `:root` for anything a theme.json PRESET points at. This covers
     --wp--custom--font-size--* AND --wp--custom--gap--* / --padding--*,
     because theme.json maps all sixteen spacing presets onto those customs
     (spacing--80 -> padding--xl, spacing--160 -> padding--big, and so on).
     Same mechanism as the font-size case described below.

     These spacing customs lived under `html body` until 2026-08-03 on the
     assumption that they were only consumed directly. They are not — the
     preset indirection means an `html body` override is invisible, so the
     ENTIRE responsive spacing scale was silently frozen at its desktop
     value. Measured before the fix: --wp--custom--padding--xl read 60/40/40
     on body at 991/767/479 while --wp--preset--spacing--80 stayed 80px at
     every width, and the homepage hero's top padding sat at a flat 160px
     against a 196/120/80/140 reference curve. Do not move them back.

   - `:root` for --wp--custom--font-size--*. Font-size presets
     (--wp--preset--font-size--xx-large etc.) are themselves defined as
     indirections to these custom properties (e.g.
     `xx-large: var(--wp--custom--font-size--h-1)`), and WordPress prints
     those presets on `:root`. A preset resolves its `var()` against the
     cascade at the element where the preset itself was declared — `:root`
     — not against whatever element consumes the preset. An `html body`
     override of the custom property is invisible to a preset already
     resolved on `:root`, because `:root` sits above `html body` and never
     sees it. Confirmed by measurement 2026-08-03: with the override on
     `html body`, `--wp--custom--font-size--h-1` read 42px at 479px while
     `--wp--preset--font-size--xx-large` (and h1's computed font-size)
     stayed 96px at every width. Moving these ten properties to `:root`
     fixes it without touching values. Only values that change at a
     breakpoint are declared. */

@media (max-width: 991px) {
	:root {
		--wp--custom--font-size--lead: 20px;
		--wp--custom--font-size--h-3: 36px;
		--wp--custom--font-size--h-2: 56px;
		--wp--custom--font-size--h-1: 60px;
		--wp--custom--font-size--stat: 60px;
		--wp--custom--font-size--display: 80px;

		--wp--custom--gap--32: 28px;
		--wp--custom--gap--36: 32px;
		--wp--custom--gap--40: 38px;
		/* Marquee content gap only — 50px desktop drops to 20px here and
		   stays 20px through the smaller breakpoints (no further reference
		   override below 991px). */
		--wp--custom--gap--50: 20px;

		--wp--custom--padding--4-x: 36px;
		--wp--custom--padding--x: 52px;
		--wp--custom--padding--xl: 60px;
		--wp--custom--padding--xxl: 80px;
		--wp--custom--padding--big: 120px;
		--wp--custom--padding--hero-top: 120px;
		--wp--custom--padding--hero-bottom: 36px;
	}

	html body {
		--wp--custom--radius--32: 24px;

		/* Marquee content left padding only — does not track --rail (32 → 20).
		   Measured curve: 32 / 40 / 20 / 20 across the four breakpoints; the
		   991px step is the one point where it moves opposite to --rail. */
		--wp--custom--marquee--content-left: 40px;
		/* Edge gradient width: 120px at 1440, 60px from 991px down. */
		--wp--custom--marquee--gradient-width: 60px;
	}
}

@media (max-width: 767px) {
	:root {
		--wp--custom--font-size--lead: 18px;
		--wp--custom--font-size--h-3: 32px;
		--wp--custom--font-size--h-2: 48px;
		/* H1 is 96 / 60 / 60 / 42 across the four breakpoints — it never
		   grows as the screen shrinks. This is a deliberate divergence from
		   the reference, which declares
		   --font-size--heading--h1-heading: 96px once in :root and never
		   overrides it in any media query — i.e. the reference renders h1 at
		   96px at every width, including 479px. This theme steps it down
		   instead, so h1 continues to shrink alongside h2 rather than
		   dominating narrow viewports. A previous version of this comment
		   claimed the reference used 64px at this breakpoint; that was wrong
		   — there is no breakpoint override in the reference at all. */
		--wp--custom--font-size--h-1: 60px;
		--wp--custom--font-size--stat: 40px;
		--wp--custom--font-size--display: 40px;

		--wp--custom--gap--32: 32px;
		--wp--custom--gap--36: 28px;
		--wp--custom--gap--40: 36px;
		--wp--custom--gap--44: 36px;
		/* Marquee logo row/track gap only — flat 64px through 991px, 16px at
		   <=767px and below (no separate 479px rule in the reference). */
		--wp--custom--gap--64: 16px;

		--wp--custom--padding--1-x: 18px;
		--wp--custom--padding--2-x: 24px;
		--wp--custom--padding--36: 24px;
		--wp--custom--padding--4-x: 32px;
		--wp--custom--padding--48: 36px;
		--wp--custom--padding--x: 48px;
		--wp--custom--padding--xl: 40px;
		--wp--custom--padding--xxl: 60px;
		--wp--custom--padding--big: 100px;
		--wp--custom--padding--hero-top: 80px;
		--wp--custom--padding--hero-bottom: 24px;
	}

	html body {
		--wp--custom--radius--24: 16px;
		--wp--custom--radius--32: 16px;

		--wp--custom--rail: 20px;

		--wp--custom--marquee--content-left: 20px;
		/* Gradient width stays 60px here — no separate 767px value; the
		   991px override above already applies at this width too. */
	}
}

@media (max-width: 479px) {
	:root {
		--wp--custom--font-size--intro: 16px;
		--wp--custom--font-size--large-body: 18px;
		--wp--custom--font-size--lead: 16px;
		--wp--custom--font-size--h-5: 20px;
		--wp--custom--font-size--h-4: 24px;
		--wp--custom--font-size--h-3: 28px;
		--wp--custom--font-size--h-2: 36px;
		--wp--custom--font-size--h-1: 42px;
		--wp--custom--font-size--stat: 28px;
		--wp--custom--font-size--display: 40px;

		--wp--custom--gap--24: 16px;
		--wp--custom--gap--32: 24px;
		--wp--custom--gap--36: 28px;
		--wp--custom--gap--40: 32px;
		--wp--custom--gap--44: 32px;

		--wp--custom--padding--5-x: 16px;
		--wp--custom--padding--1-x: 16px;
		--wp--custom--padding--2-x: 18px;
		/* padding-36 increases relative to the ≤767px value (24px → 36px) —
		   reproduced as given, per spec. */
		--wp--custom--padding--36: 36px;
		--wp--custom--padding--4-x: 28px;
		--wp--custom--padding--48: 32px;
		--wp--custom--padding--x: 24px;
		--wp--custom--padding--xl: 40px;
		/* padding-xxl increases relative to the ≤767px value (60px → 80px) —
		   reproduced as given, per spec. */
		--wp--custom--padding--xxl: 80px;
		--wp--custom--padding--big: 80px;
		/* hero-top increases relative to the ≤767px value (80px → 140px).
		   Reproduced from the reference, which does the same — the hero needs
		   more breathing room above the headline once the nav stacks on the
		   narrowest screens. Non-monotonic on purpose, like padding--xxl
		   above. Do not "correct" it. */
		--wp--custom--padding--hero-top: 140px;
	}

	html body {
		--wp--custom--radius--12: 4px;
		--wp--custom--radius--24: 16px;
		--wp--custom--radius--32: 16px;
	}
}

/* Retheme — utilities
---------------------------------------------------------------------------- */

/* Section surfaces — exactly two types. Page-level sections get no class and
   sit on the rail; card sections tuck in from the page edge on purpose.
   Also selectable in the editor as a core/group block style — see
   register_block_styles() in functions.php — which applies
   `is-style-surface-card` / `is-style-surface-card-tight`. Both class forms
   are supported so patterns can use either the utility class directly or the
   editor's Styles panel.

   margin-inline is !important: WordPress's own root-padding-aware alignment
   CSS sets margins on the same properties for these elements —
   `.has-global-padding > .alignfull` (a higher-specificity compound
   selector) for full-bleed children, and `.is-layout-constrained > *`
   (itself !important, for auto-centering) for non-aligned children of a
   constrained layout. Both beat a plain class rule, so the card surface
   would silently render with zero inset without !important here. Confirmed
   via computed-style inspection on idia/home-hero-card, the first pattern
   to apply this class to a top-level section.

   Structural exception to §8.1 — the .alignfull variant: a full-width card
   surface escapes root padding (align:full's -rail margin), then returns by
   the inset. */

.is-surface-card,
.is-style-surface-card {
	margin-inline: var(--wp--custom--section-inset) !important;
	border-radius: var(--wp--custom--radius--24);
	overflow: hidden;
}

.alignfull.is-surface-card,
.alignfull.is-style-surface-card {
	margin-inline: calc(var(--wp--custom--section-inset) - var(--wp--custom--rail)) !important;
}

.is-surface-card--tight,
.is-style-surface-card-tight {
	margin-inline: var(--wp--custom--section-inset-sm) !important;
	border-radius: var(--wp--custom--radius--24);
	overflow: hidden;
}

.alignfull.is-surface-card--tight,
.alignfull.is-style-surface-card-tight {
	margin-inline: calc(var(--wp--custom--section-inset-sm) - var(--wp--custom--rail)) !important;
}

/* Footer card inner padding — horizontal only. --wp--custom--rail is a
   custom property, not a spacing preset, so it cannot be written as
   var:preset|spacing|... in the block's JSON padding attribute (see
   patterns/footer-rounded-dark.php, "Footer" group). No preset on the
   spacing scale reproduces the rail's 32/32/20/20 step — every preset here
   maps to its own --wp--custom--gap--* custom property, and none of those
   step to 20px at <=767px the way --rail does. Mirrors hero-card.css's
   .idia-hero-card > .wp-block-cover__inner-container rule exactly: same
   property, same token, same reasoning. Vertical padding stays on the block
   attribute (spacing|80) since that curve is unaffected and stays
   Site-Editor-editable. */
.idia-footer__card {
	padding-left: var(--wp--custom--rail);
	padding-right: var(--wp--custom--rail);
}

/* Measure utilities — max-width only, left-anchored. Also selectable in the
   editor as core/group block styles (`is-style-measure-*`); both forms
   supported for the same reason as the surface classes above. */

.is-measure-hero, .is-style-measure-hero { max-width: var(--wp--custom--measure--hero); }
.is-measure-hero-home, .is-style-measure-hero-home { max-width: var(--wp--custom--measure--hero-home); }
.is-measure-hero-intro, .is-style-measure-hero-intro { max-width: var(--wp--custom--measure--hero-intro); }
.is-measure-hero-intro-home, .is-style-measure-hero-intro-home { max-width: var(--wp--custom--measure--hero-intro-home); }
.is-measure-hero-meta, .is-style-measure-hero-meta { max-width: var(--wp--custom--measure--hero-meta); }
.is-measure-section-title, .is-style-measure-section-title { max-width: var(--wp--custom--measure--section-title); }
.is-measure-section-title-narrow, .is-style-measure-section-title-narrow { max-width: var(--wp--custom--measure--section-title-narrow); }
.is-measure-prose, .is-style-measure-prose { max-width: var(--wp--custom--measure--prose); }
.is-measure-centred, .is-style-measure-centred { max-width: var(--wp--custom--measure--centred); }
.is-measure-aside, .is-style-measure-aside { max-width: var(--wp--custom--measure--aside); }
.is-measure-aside-narrow, .is-style-measure-aside-narrow { max-width: var(--wp--custom--measure--aside-narrow); }
.is-measure-caption, .is-style-measure-caption { max-width: var(--wp--custom--measure--caption); }
.is-measure-footer-left, .is-style-measure-footer-left { max-width: var(--wp--custom--measure--footer-left); }
.is-measure-footer-links, .is-style-measure-footer-links { max-width: var(--wp--custom--measure--footer-links); }
.is-measure-card, .is-style-measure-card { max-width: var(--wp--custom--measure--card); }
.is-measure-testimonial, .is-style-measure-testimonial { max-width: var(--wp--custom--measure--testimonial); }
.is-measure-pricing-title, .is-style-measure-pricing-title { max-width: var(--wp--custom--measure--pricing-title); }
.is-measure-work-intro, .is-style-measure-work-intro { max-width: var(--wp--custom--measure--work-intro); }

/* The only centred text block in the system. */
.is-measure-centred,
.is-style-measure-centred {
	margin-inline: auto;
	text-align: center;
}

/* Eyebrow label — mono family, small, medium weight, uppercase. Its own
   style, never a shrunken heading. */

.is-style-eyebrow {
	font-family: var(--wp--preset--font-family--mono);
	font-size: var(--wp--preset--font-size--s);
	font-weight: var(--wp--custom--font-weight--medium);
	text-transform: uppercase;
}

/* Nav item badge — small numeric count tucked above a nav link (e.g. a
   live project count next to "Work"). Registered as a core/paragraph
   block style so it stays editable, but not wired to a specific nav item
   yet: the live nav only has placeholder links (Home, Sample Page,
   Contact), and AGENTS.md prohibits inventing the destination or the
   count. Once a real "Work" item exists in the site's navigation, add a
   paragraph with this style directly after it inside header-nav-inner.php,
   wrapped so it sits visually above-right of the link (position: relative
   on the wrapping list item, this class marginless-absolute or -12px
   margin-top depending on the final markup shape). */

.is-style-nav-badge {
	display: inline-block;
	margin-top: calc(-1 * var(--wp--custom--gap--12));
	padding: var(--wp--custom--gap--4) var(--wp--custom--gap--8);
	border-radius: var(--wp--custom--radius--pill);
	background-color: var(--wp--preset--color--primary);
	color: var(--wp--preset--color--base);
	font-size: var(--wp--preset--font-size--x-small);
	line-height: 1;
}

/* House hover — the one gesture: pill radius to 16 on hover/focus-within.
   No colour shift, scale, or shadow stacked on top. */

.has-house-hover {
	border-radius: var(--wp--custom--radius--pill);
	transition: border-radius var(--wp--custom--transition);
}

.has-house-hover:hover,
.has-house-hover:focus-within {
	border-radius: var(--wp--custom--radius--16);
}

@media (prefers-reduced-motion: reduce) {
	.has-house-hover {
		transition: none;
	}
}

/* Focus ring */

a:focus-visible,
button:focus-visible,
input:focus-visible,
textarea:focus-visible,
select:focus-visible,
.wp-block-button__link:focus-visible {
	outline: 2px solid var(--wp--preset--color--primary);
	outline-offset: 2px;
}

/* Footer nav columns (Company/Resources/Product) — deliberate 2-up grid at
   mobile, not a content-driven flex-wrap, so the layout doesn't depend on
   link label lengths staying short. Without this, core's columns block
   force-stacks all three to 100% width below 781px (its own built-in
   default, not a bug in this theme), giving 12 stacked links in a row.
   Every !important here overrides that same core behaviour: WordPress
   prints per-block layout CSS — the generic `.is-layout-flex{display:flex}`
   rule, a `.wp-container-core-columns-is-layout-*{flex-wrap:nowrap}` rule,
   and inline flex-basis block-support styles — after theme stylesheets, the
   same category of override already used in header.css for the nav's grid
   centering. There is no `layout` attribute here to remove instead, since
   core's stacking is triggered by its own media query, not by ours. */
@media (max-width: 767px) {
	.idia-footer__nav-columns {
		display: grid !important;
		grid-template-columns: 1fr 1fr;
		column-gap: var(--wp--preset--spacing--16);
		row-gap: var(--wp--preset--spacing--24);
	}

	.idia-footer__nav-columns > .wp-block-column {
		width: auto !important;
		flex-basis: auto !important;
	}
}

/* ---- Entrance-reveal starting states: neutralised in the Site Editor ----
   Every scroll/load-triggered entrance on this site (hero, CTA, and the nine
   sections added for the remaining-sections animation pass — marquee,
   gallery, counter, service, work, pricing, faq, testimonial, blogs) ships
   its phase-1 CSS state (opacity:0, a translate, sometimes a blur) directly
   in that section's own stylesheet, and add_editor_style() loads every
   section stylesheet unconditionally (AGENTS.md §12a) so patterns render
   truthfully in Appearance -> Editor. But none of the GSAP reveal scripts
   that animate OUT of that state are ever enqueued inside the block editor
   iframe — they are all conditionally loaded on the front end only, via
   the_content/wp_enqueue_scripts. Left alone, every one of those elements
   would render invisible, blurred, or off-position on the editor canvas
   forever, with nothing to bring them back — verified live via
   get_block_editor_settings(): the CSS payload includes every reveal
   selector below, and there is no reveal script anywhere in the editor's
   own dependency graph to un-hide them.

   WordPress wraps every add_editor_style() stylesheet in .editor-styles-
   wrapper inside the canvas iframe, so scoping this override to that class
   confines it entirely to the editor — the front end (where the real GSAP
   tweens do the same job) is completely unaffected. One rule per class list
   covers every current and future entrance reveal on the site: if a new
   section adds its own reveal starting-state, add its selector here too. */
.editor-styles-wrapper .idia-hero-card__badge,
.editor-styles-wrapper .idia-hero-card__text > .wp-block-heading,
.editor-styles-wrapper .idia-hero-card__text > p,
.editor-styles-wrapper .idia-hero-card__meta,
.editor-styles-wrapper .idia-hero-card__actions,
.editor-styles-wrapper .wp-block-cover__image-background,
.editor-styles-wrapper .idia-cta-badge,
.editor-styles-wrapper .idia-cta-badge ~ .wp-block-heading,
.editor-styles-wrapper .idia-cta-button,
.editor-styles-wrapper .idia-marquee__intro,
.editor-styles-wrapper .idia-gallery__title-left h2,
.editor-styles-wrapper .idia-counter__stat,
.editor-styles-wrapper .idia-service__title-left,
.editor-styles-wrapper .idia-service__title-right,
.editor-styles-wrapper .idia-work__title-block,
.editor-styles-wrapper .idia-work__card,
.editor-styles-wrapper .idia-pricing__container > .wp-block-group > .is-measure-pricing-title,
.editor-styles-wrapper .idia-pricing__tab-menu,
.editor-styles-wrapper .idia-pricing__card,
.editor-styles-wrapper .idia-faq__title-block,
.editor-styles-wrapper .idia-faq__item-wrap,
.editor-styles-wrapper .idia-testimonial__title-block > .is-measure-testimonial,
.editor-styles-wrapper .idia-testimonial__title-block > .is-measure-aside-narrow,
.editor-styles-wrapper .idia-blogs__title-row > .is-measure-aside,
.editor-styles-wrapper .idia-blogs__single-card {
	opacity: 1 !important;
	transform: none !important;
	filter: none !important;
}