/*
Theme Name:   EXADRY
Theme URI:    https://www.exadry.ro
Description:  Standalone theme for exadry.ro. Began as a child of Divi 3.0 and
              absorbed everything it inherited — templates, stylesheets, the
              generated CSS blocks, the WooCommerce content wrapper and
              custom.js — until the parent could be removed. The builder
              modules on the 13 page-builder pages are rendered by the Divi
              Builder plugin, which is a separate thing and stays. See
              docs/divi-removal-analysis.md.
Author:       EXADRY
Version:      2.0.0
Text Domain:  exadry
*/

/* Deliberately empty, and that is not the same as unused.
 *
 * Everything that styles this site is enqueued from functions.php: the four
 * stylesheets absorbed from Divi (css/divi-*.css) and the five blocks Divi
 * generated at runtime (css/generated/), one of which is 7.5 KB of this site's
 * own hand-written CSS that used to live inside a Divi option.
 *
 * This file is enqueued LAST in that chain, so anything added here overrides
 * all of it. That is the point: new work goes here, inherited work stays where
 * it came from, and the boundary between the two stays legible.
 *
 * Do not paste the absorbed CSS into this file to "tidy up". Restyling the
 * site is a redesign, not a migration step. */

/* ---------------------------------------------------------------------------
 * Divi Builder 4.5.3 compatibility
 * ---------------------------------------------------------------------------
 *
 * The absorbed CSS was written by Divi 3.0 against Divi 3.0's markup. The
 * builder *plugin* is 4.5.3 and renders the same modules with slightly
 * different HTML, so a handful of inherited rules aim at elements that no
 * longer exist. These are the only two, and they were found by measurement,
 * not by reading: every selector in the absorbed stylesheets was tested
 * against the live production DOM and against the dropped-Divi staging DOM,
 * and the two sets were diffed. 214 selectors match on production; 5 stop
 * matching here, and 3 of those 5 are covered by the plugin's own per-page
 * generated CSS.
 *
 * Repeat that measurement if the builder plugin is ever updated — this block
 * is version-specific and there is no reason to think 4.5.4 breaks the same
 * two rules and no others.
 *
 * Scoped as tightly as the originals so nothing else can be caught by them. */

/* 4.5.3 wraps text-module content in an extra .et_pb_text_inner div, so Divi's
 * `.et_pb_text > :last-child { padding-bottom: 0 }` now lands on that wrapper
 * instead of on the last real element. Without this the last heading or
 * paragraph of every text module keeps the 10px bottom padding that
 * divi-base.css puts on all headings — visible as extra space under the first
 * h1 on the homepage. */
.et_pb_text_inner > :last-child {
	padding-bottom: 0;
}

/* 4.5.3 drops the `et_pb_module` class from button anchors, so Divi's
 * `.et_pb_promo_button, .et_pb_module.et_pb_button` rule misses them and an
 * <a> falls back to display:inline — losing its padding box and rendering
 * 205px wide instead of 196.6px. `.et_pb_promo_button` still matches on its
 * own, so only the plain-button half is restored here.
 *
 * Divi's rule also carried `color: inherit`. That is deliberately NOT copied:
 * the buttons already compute the correct colour here (#2ea3f2, measured
 * against production), so re-adding it could only change something that is
 * currently right. Restore the one declaration that is actually missing. */
.et_pb_button {
	display: inline-block;
}