/* Vintage Threads and Loops — child theme overrides.
Kept minimal by design: layout/spacing/typography/color live in Divi's own
section/row/column/module settings wherever possible. This file only holds
what Divi's UI cannot express natively (documented per rule below). */
/* The page's dark ground (#26241f) is set per-section via Divi's own background
control, but the element itself is outside Divi's builder scope. On a
browser window taller than the page's content, the default light theme body
color would show through below the last section. Same fix already used
elsewhere in this project for this exact class of bug. */
body { background-color: #26241f; }
/* Divi's Image module stretches its own outer wrapper (.et_pb_image_N) to a
flex-stretched parent height, but the inner .et_pb_image_wrap span has no
height of its own (height:auto), so it shrinks to the ![]()
's native
aspect-ratio instead of passing the outer wrapper's height down — breaking
the percentage-height chain the ![]()
's own height:100% needs to resolve
against, so object-fit:cover never gets a real box to cover. No native Divi
control reaches either of these inner elements. Used on the Home hero photo. */
.hero-photo .et_pb_image_wrap { height: 100%; }
.hero-photo img { width: 100%; height: 100%; object-fit: cover; }
/* Home gallery mosaic caption text-shadow (design changelog, 2026-09-04
accessibility pass). Perceptual polish only — the actual contrast fix is
the caption scrim gradient itself (set natively via the module's gradient
background). No confirmed Divi 5 JSON path for text-shadow on a Text
module's body font (only the Heading module's title/dropCap groups are
documented), so applied here instead of risking a silently-blank attempt. */
.mosaic-caption-text.mosaic-caption-text { text-shadow: 0 1px 2px rgba(20,18,15,.6); }
/* Privacy Policy: the "Contact" section's mailto link is a plain inside
a Text module's rich content, not a styled divi/link module — with no
Divi styling of its own it falls through to Divi's default anchor color
(the stock accent blue, #2ea3f2), the same trap documented project-wide
in the global README's Lessons Learned for un-styled Divi elements. */
body .policy-link.policy-link a { color: #b98a4b; }
body .policy-link.policy-link a:hover { color: #d3a465; }
/* Same underlying bug as the hero photo above, different shape: The Work's
piece photos use object-fit:contain with an intentional max-height (the
design deliberately lets tall/narrow images "pillarbox" rather than crop).
module.decoration.sizing (width/height/maxHeight) never reaches the actual
![]()
tag here either — without this, the image renders at its raw
intrinsic pixel size instead of scaling to the column, which is what read
as "not centered" (it's actually just tiny and left-aligned, not centered
*or* off-center). Plain width/max-height on the img is enough here — no
percentage-height chain to bridge, since width:100% resolves against the
column's width directly rather than an ancestor's height. */
body .piece-photo.piece-photo .et_pb_image_wrap {
width: 100% !important;
}
body .piece-photo.piece-photo img {
display: block !important;
width: 100% !important;
height: auto !important;
max-height: 760px !important;
object-fit: contain !important;
}
/* Tablet/phone-specific padding, as a documented exception to "native controls
only": extensively verified (isolated test pages, sync-field fixes, REST vs
wp-cli updates, and a genuine save through the live Divi Visual Builder) that
Divi silently drops tablet/phone breakpoint values for spacing.padding once a
page reaches this one's real-world size/complexity — the desktop value keeps
rendering at every width instead. Everything else (column stacking, font
sizes, flex layout) reliably respects its breakpoint values; only this
property category doesn't at this scale, so it's the one exception here.
Values below match exactly what was authored (and silently ignored) in the
page's own Divi JSON — see the site's own row/section decoration.spacing.
Selectors are deliberately `body .foo.foo` rather than plain `.foo`: Divi's
own generated rule for some rows/sections is a 2-class selector
(`.et_pb_row_N.et_pb_row`) that ALSO carries `!important` on every padding
property — found on the-work's CTA row. Two `!important` rules resolve by
specificity first, and a single custom class (0,1,0) doesn't beat Divi's
2-class rule (0,2,0). Doubling the class alone only ties it (0,2,0 vs
0,2,0), which then falls back to source order — and Divi's inline