/* Theme Name: Talamantez Therapy Author: Talamantez Therapy Description: Custom block theme for talamanteztherapy.com — 5 pages, blog, header, and footer rebuilt in the native block editor, replacing Elementor. Version: 0.1.34 Requires at least: 6.7 Tested up to: 7.0 Requires PHP: 8.3 License: GNU General Public License v2 or later License URI: https://www.gnu.org/licenses/gpl-2.0.html Text Domain: talamantez-therapy Tags: block-theme, full-site-editing, blog, one-column */ /* * Design tokens live in theme.json. This file exists for the required theme * header and for any CSS that cannot be expressed in theme.json. */ /* * ============================================================================ * U20-T typography register CLOSE (2026-07-12) * ============================================================================ * Owner decision, round-2 lens A * (scratch/artifacts/u20-type2-lens-a/{rationale.md,specimen.html}), judged * in scratch/artifacts/u20-type2-judge/scorecard.md: * * T1 (base typeface) = Literata + Karla, a two-face reading-first pairing, * both SIL OFL 1.1, self-hosted, $0 forever. Role split (see * theme.json typography.fontFamilies slugs "body"/"heading" = Literata, * "ui" = Karla): * - Literata (regular 400 + italic 400) — h1/h2/h3 headings, all * long-form body copy (blog posts, page content, FAQ answers when * that pattern ships). * - Karla (one variable file, pinned to weight 400 regular + weight * 600 semibold via two theme.json fontFace entries) — kickers/ * eyebrows (.is-style-kicker), buttons, nav (core/navigation block * style), category-label chips (.wp-block-post-terms a), contact- * form labels (.grunion-field-label). * T2 (emphasis device) = SKIP the second/script face. Literata ships true * italics; /emphasis renders in Literata Italic (already loaded for * headings/body — zero extra webfont weight). The synthesis spine's * Caveat script device is DROPPED at implementation per the round-2 * judge's finding that it violates round 2's own "no new script faces" * rule. * * STALE-COMMENT CORRECTION (U14 K2 lock, 2026-07-16): the two clauses this * paragraph used to carry — a "handwritten Therapy" script wordmark, and a * six-point spark glyph as a recurring "education-wing device" — are * superseded by the K2 LOCK RECORD (docs/design/2026-07-16-u14-porch- * build-spec-DRAFT.md, dispositions O3 + "Wordmark"): the wordmark ships * as a typographic Karla/Literata lockup (no script face, no image logo * pending K3), and the six-point star is a plain shared family mark * confined to the masthead/footer ONLY — never an inline recurring glyph * in body/hero emphasis. Left here as the historical record of what this * pass originally shipped; do not read the retired clauses as current. * * Retired: Adobe Fonts / Typekit kit `vuj5jfg` (Brandon Grotesque, * designer-owned, Adobe licensing forbids self-hosting, ~1.5s * render-blocking third-party request — perf ledger R20/U18). See * functions.php for the removed enqueue/editor-style calls. * * Self-hosted payload (theme/assets/fonts/, Latin subset only — see * assets/fonts/LICENSE-fonts.txt for exact source URLs + fetch date): * literata-regular.woff2 ~20.4 KB * literata-italic.woff2 ~21.1 KB * karla-variable.woff2 ~24.3 KB (one file serves BOTH Karla weights — * Google's own CSS2 response returns the same * URL for the 400 and 600 requests; the two * theme.json fontFace entries pin the `wght` * axis per weight from that single source, so * only one file is downloaded) * ------------------------------------------------------------------------ * Total ~65.9 KB, THREE requests — under lens-a's * ~71KB/four-file estimate. * * Deviation from the task brief's generic default: no separate Literata (or * Karla) BOLD weight was added. Lens-a's own weights/styles line and payload * budget (rationale.md "Licensing" + "Loading plan") specify only Regular * 400 + Italic 400 for Literata and Regular 400 + SemiBold 600 for Karla — * no bold cut for either family. Any inside long-form blog content * will render as browser-synthesized (faux) bold on Literata until/unless a * future pass adds a true bold weight; flagged for the gate, not resolved * here, since adding a 5th file would exceed the specced/judged payload. * * fontSizes are UNCHANGED by this pass (lens-a's scale matches the existing * fluid small…xx-large tokens exactly — see rationale.md "theme.json fluid * scale, unchanged"). */ /* * U20 partial close (2026-07-11): theme.json palette extension — color/ * register tokens only, current (provisional) typography untouched; see * docs/plans/2026-07-10-001-feat-enhancements-phase-plan.md Review Log, * "Owner answers wave 5" and the U20 synthesis * (scratch/artifacts/u20-synthesis/synthesis.md §a). JSON carries no * comments, so every contrast pair the new/changed tokens create is logged * here instead. All ratios computed with the WCAG 2.x relative-luminance * formula, independently re-derived for this edit (not copied uncomputed * from the synthesis doc, though they match it): * * - teal-deep (#1F5A5E) text on paper (#FAF6EE): 7.26:1 — PASS (≥4.5:1 * body-text bar). Grief-wing text accent / step numerals / focus ring. * - contrast/navy (#03174B) text on paper (#FAF6EE): 15.86:1 — PASS * (≥4.5:1). Also the ratio for the reverse pairing (paper text on navy, * see next row) — contrast ratio is symmetric between two fixed colors. * - paper (#FAF6EE) text on contrast/navy (#03174B): 15.86:1 — PASS * (≥4.5:1). Same pair as above, reversed fg/bg. * - teal (#B6DEE0) as UI/large text on contrast/navy (#03174B): 11.82:1 — * PASS (≥3:1 UI bar; also clears the 4.5:1 body-text bar). teal is a * wash/fill color and must never be set as text on a LIGHT background * (teal-on-white is ~1.45:1, fails AA) — this navy-background pairing is * the sole authorized exception, per the synthesis's three named call * sites (CTA footnote copy, no-gold-state emphasis spark, no-gold-state * chooser arrow — none shipped in this theme yet; this comment documents * the token's authorized ceiling ahead of that unit's build). * * No locked pair fails its bar; nothing shipped with a warning exception. * * `contrast` (navy) migration: value changed from #2A3353 to #03174B in * this same edit (owner-confirmed re-anchor, wave-4/5 lock; synthesis * §Migration notes item 1). This is a sitewide value change — every existing * surface referencing var(--wp--preset--color--contrast) (header, footer * nav accents, buttons, heading text, blog pagination .current, the * dark-section-link rule below) now renders the new navy. See the dated * addendum on the dark-section-link rule below for the one comment in this * file whose own recorded ratio depended on the old value. * * Deliberately NOT added this pass (still gated, see the plan's wave-5 §6 * open item): gold tokens (dropped, wave-3 lock) and category-label color * tokens (`label-*`, held pending the gold-deep chip-vs-large-accent * clarification). No typography settings touched (wave-5 §1: typography * deferred to its own session; this extension ships with current * provisional fonts). * * --- wave 7 — label chips (2026-07-11) ----------------------------------- * Owner answers wave 7 (plan Review Log, "2026-07-11 — Owner answers wave * 7", item 1) closed the gold-chip question this file flagged above as * deferred: gold is now fully out of the system, and the category-label * hues are final. `terracotta-deep` (#9C5030) is a new palette token added * in this pass (bake-off winner recorded in * scratch/artifacts/u20-synthesis/synthesis.md, "Warm-accent bake-off"); * `teal-deep` and `contrast`/navy already existed (see above) and are only * being reused here, not re-added. * * Five cluster → hue assignments (icons unchanged: leaf/flag/spark/paw/ * compass): * - Child Grief → teal-deep (leaf) * - Milestones → teal-deep (flag; told apart from Child Grief * by icon + text, same hue reused) * - Holiday Grief → contrast/navy (six-point spark) * - Pet Loss → contrast/navy (paw; told apart from Holiday Grief * by icon + text, same hue reused) * - Practical Next Steps → terracotta-deep (compass; the one cluster * with its own hue) * * Chip-hue-on-paper contrast (small text, 4.5:1 bar): * - teal-deep (#1F5A5E) on paper (#FAF6EE): 7.26:1 — PASS (recorded * above, referenced here — same pair, same ratio). * - contrast/navy (#03174B) on paper (#FAF6EE): 15.86:1 — PASS (recorded * above, referenced here — same pair, same ratio). * - terracotta-deep (#9C5030) on paper (#FAF6EE): 5.41:1 — PASS (≥4.5:1 * body-text bar). Computed independently for this edit with the same * WCAG 2.x relative-luminance formula used above; matches the * synthesis doc's own figure. No darkening needed — shipped as-is. * * All three chip hues clear the 4.5:1 bar on paper; no adjustment required. * Attribute-selector CSS for the `label-*` chips themselves (the * `a[href*="/category//"] .label{...}` rule U1 describes) is U1 build * work, not part of this token/annotation pass — deliberately not added * here. */ /* * Live-site parity: header is permanently navy with the white logo variant, * footer is permanently pale-aqua with the navy logo variant, at ALL * viewport widths — there is no breakpoint inversion (corrected 2026-07-07 * during U5 verify; see reference/rebuild-spec.md § Header / § Footer). * Colors are set via block attributes (backgroundColor/textColor on the * header/footer Group and Navigation blocks in parts/header.html and * parts/footer.html) rather than CSS, so no override rules are needed here. */ /* * core/site-logo (header only — the footer logo is a plain core/image with * its own inline width) cannot size an SVG via its "width" block attribute: * the logo SVG has a viewBox but no width/height, so WordPress can't read * intrinsic dimensions and emits neither width/height attributes on the img * nor an inline width on the wrapper (verified on staging 2026-07-07 — the * img rendered 0×0, or container-width once given height:auto). Pin the * rendered size here instead; 200px matches the reference capture * (~180–220px at 1280, similar on mobile). * * SLIMMED (2026-07-30, header-slimming fix): 200px -> 120px, one of several * cuts (padding, this scale, row gaps) that bring the sticky header down * from 223px to ~139px at 1280/987/768 — see the sticky-header SECTION * below for the full before/after. Logo remains legible at 120px (measured * ~31px tall); wp:site-logo's own "width" attribute in parts/header.html is * kept in sync (120) even though this rule is what actually renders it. * * ENLARGED, desktop/tablet only (2026-07-30, header-unification commission): * 120px -> 192px at >=768px (rendered ~48.2px tall, up from ~31px, mid-low * of the owner's requested 48-60px range). Chosen because it keeps the * two-row fallback height closest to the ~90px cap: row 1's height is * governed by whichever of the logo or the 44px-min-height CTA buttons is * taller, and 48.2px only adds ~4px over the buttons' own floor, versus * the ~10px a 60px logo would add. The source is the ORIGINAL vector * (attachment 67, `2021/05/talamantez-therapy-logo-white.svg`, confirmed * live via `wp option get site_logo` + `wp post get 67`), already the * light/white variant the navy header needs (`.st0{fill:#FFFFFF}`); no * raster upgrade was needed or produced, since scaling an SVG's CSS width * costs nothing in crispness, only this rule's number changes. * * MOBILE (<768px) is deliberately left untouched at 120px. This rule used * to be unscoped (applied at every width), so the enlargement is carved * out into its own >=768px override immediately below rather than edited * here, preserving the existing base rule as the mobile default * byte-for-byte. */ .site-header .wp-block-site-logo img { width: 120px; max-width: 100%; height: auto; } @media (min-width: 768px) { .site-header .wp-block-site-logo img { width: 192px; } } /* * SECTION: header row-gap tightening (header-slimming fix, 2026-07-30). * Flex containers in parts/header.html default to WP's blockGap (0.5em / * ~24px in the block-level nesting used here) between wrapped rows — more * air than a header needs stacked vertically. Tightened to single digits so * the wrapped rows read as one compact unit instead of stacked cards. * * `.header-cta-col`'s own row-gap (previously 2px, spacing the button row * against the subtext line below it) was removed here (Amendment 13 * resolution, 2026-07-30) along with the subtext paragraph itself * (`.header-cta-subtext` — see the REMOVED note further down) — the group * now wraps a single child (`.header-cta-wrap`), so a row-gap has nothing * left to space. */ .header-brand-row { row-gap: 4px; } /* * Header nav uppercase (U11 gate fix, 2026-07-08): production's nav is * uppercase+letterspaced in the HEADER only — the footer nav renders Title * Case ("Speaking Information / Resources / Podcast / Blog / Etsy Shop / * Contact", reference/pages/blog-1280.png). theme.json previously set * textTransform:"uppercase"/letterSpacing on core/navigation globally, * which incorrectly also uppercased the footer nav; that global rule has * been removed from theme.json (styles.blocks.core/navigation) and is * re-applied here scoped to .site-header. The mobile overlay dialog * (#modal-N, .wp-block-navigation__responsive-container) renders as a DOM * child of the header's