/* ========================================================================================= * Bridge stylesheet: makes Elementor's native widget markup look like the original design. * * The pages are built from real Elementor components (see includes/elementor-widgets.php), * and each element carries the same Tailwind classes the original hand-written markup used. * Tailwind reaches anything on an element's own wrapper, but it can't reach the markup * Elementor generates *inside* a widget - `.elementor-heading-title`, `.elementor-button`, * `.elementor-counter-number`, and so on. Those internals are styled here. * * Two rules of thumb: * - Everything here is a DEFAULT. Elementor's own Style tab writes at * `.elementor-NNN .elementor-element.elementor-element-XXX` (0,3,0) specificity, which * outranks these selectors - so an admin restyling a widget in the panel always wins. * - Keep selectors anchored on an `eka-` class so nothing here leaks into widgets an admin * adds later from the standard Elementor panel. * * Loaded after elementor-frontend and the per-post CSS (see eka_enqueue_assets()). * ====================================================================================== */ /* ----------------------------------------------------------------------------------------- * Containers * * Elementor containers default to flex-column with 10px padding and a 20px gap. The ported * Tailwind classes already carry the site's own spacing and layout, so Elementor's defaults * are zeroed out through its custom properties. Only the properties are neutralised - no real * padding/gap declarations - which leaves Tailwind's `px-4` / `gap-12` free to apply. * -------------------------------------------------------------------------------------- */ /* * !important is deliberate here, not a specificity shortcut: Elementor regenerates each * container's `--display`/`--flex-direction`/`--padding-*`/`--gap*` as an inline