/** * Nominee (headings) and Kobe1.1 (body/UI text) - Figma brand fonts, ClickUp 86eyv0pqj. * editor-friendly-ok * * Config investigated: Blocksy Pro's own Custom Fonts / Typography panel stores its * font registration in wp_options via the Customizer UI, which this repo's git-based * PR -> CI deploy pipeline cannot reach or version (there is no WP-Admin step in this * workflow). Every other Nominee/Kobe1.1 reference already shipped in this theme * (23 files across header, footer, checkout, cart, search, health-hub, etc.) is a * plain CSS custom property already wired for this exact @font-face registration * approach - this file follows that established, already-shipped pattern rather than * introducing a new one. The @font-face blocks below target no block-editor content * at all (they only register font resources); the bare body/h1-h6 fallback rules * further down DO target block content as a last-resort default (see that block's * own comment), using the wp--preset--* var-with-fallback pattern so the Styles * panel can still override per-block - editor and frontend stay in sync because * both read the same preset var, not because this file has no selectors at all. * The family names registered here ("Nominee", "Kobe1.1") are the literal strings * every existing --*-heading-font / --*-body-font custom property already falls * back to, matching the wp--preset--* pattern those properties already use. * * Source: ClickUp ASSETS doc 13256g-159478. Kobe1.1-Bold.{woff,woff2} taken as-is * from the ASSETS zip's WEB/ folder. * * Nominee, updated 18 Sep 2026 (ClickUp 86eyv0pqj): the client supplied his own * MyFonts webfont kit for Nominee Heavy Extended (Build ID 3867246, 2020-12-16, * foundry TypeUnion) - emailed 17 Sep, bounced at our MTA, then delivered by Drive * link in #c-bonza-dog and archived on the task as * Nominee-HeavyExtended-MyFonts-WebfontKit-3867246.zip. Its webFonts/ folder's * font.woff2 / font.woff are self-hosted here as Nominee-HeavyExtended.{woff2,woff}, * replacing the woff2 this repo had converted locally from the ASSETS desktop TTF. * That swap is the point: a foundry-issued webfont build covered by the site * owner's own MyFonts licence, not a conversion we performed ourselves - the exact * category of problem the Kobe1.1 EULA question below is still open on. * Measured before swapping: same typeface (version 1.000, PS name * Nominee-HeavyExtended, usWeightClass 900) and identical character coverage * (439 codepoints in both, German umlauts included), so nothing renders * differently; only the provenance and the bytes change (2048 upm local * conversion -> 2000 upm MyFonts build, 42,352 -> 28,308 bytes for the woff2). * The kit ships a MyFonts licence notice naming the build and restricting all * parties other than the site owner; it is reproduced verbatim above the * @font-face rule below and must travel with this CSS. * * Kobe1.1's bundled EULA (VJ-TYPE, Dec 2024) restricts webfont conversion in a way * whose exact scope is ambiguous (see the task doc); this deploy proceeds on an * explicit decision by the site owner to ship it now rather than wait on written * clarification from VJ-TYPE. * * Regular (400) cut, added 17 Sep 2026 - closes PR #740's documented deviation. * PR #740 had no Regular file and registered the Bold file at 400 as a stand-in. * On 16 Sep the client forwarded Black Studio's list of font URLs (ticket #3810, * forwarded by the client contact on record), which are the current live theme's own paths: * https://www.bonza.dog/wp-content/themes/bonza/bs/fonts/kobe/Kobe-Regular.{woff2,woff} * Those two files are self-hosted here as Kobe1.1-Regular.{woff2,woff}. Their * internal name tables confirm they are the same family this theme already asks * for, not a lookalike: family "Kobe1.1", subfamily "Regular", version 1.031, * unique ID "1.031;ViJe;Kobe1.1-Regular" - same foundry code (ViJe) and same * version as the ASSETS Kobe1.1-Bold file already shipped here. Body text now * renders in the real Regular weight instead of a Bold stand-in. * * Licensing is unchanged by this: same VJ-TYPE family, same open question. The * client's links carried no EULA, invoice or licence tier, and the name-table * match also confirms production's own live copy is this same VJ-TYPE font - * previously recorded as a plausible inference, now measured. */ /** * @license * MyFonts Webfont Build ID 3867246, 2020-12-16T11:57:38-0500 * * The fonts listed in this notice are subject to the End User License * Agreement(s) entered into by the website owner. All other parties are * explicitly restricted from using the Licensed Webfonts(s). * * You may obtain a valid license at the URLs below. * * Webfont: Nominee Heavy Extended by TypeUnion * URL: https://www.myfonts.com/collections/typeunion-foundry * * (c) 2026 MyFonts Inc. */ /* editor-friendly-ok - @font-face registers a font resource, it styles no block. woff2 first, woff second: the browser takes the first source it can activate, so modern engines never download the larger woff (MDN, @font-face/src). */ @font-face { font-family: "Nominee"; src: url("../fonts/nominee/Nominee-HeavyExtended.woff2") format("woff2"), url("../fonts/nominee/Nominee-HeavyExtended.woff") format("woff"); font-weight: 900; font-style: normal; font-display: swap; } /* editor-friendly-ok - @font-face registers a font resource, it styles no block. Inter 400 / 500 / 900 (86eyy8hud). Figma uses Inter Regular on the Biotics timeline numerals (18.06px), Medium on the "DVM" credential and Black on the PDP feeding-calculator stepper. Source: Inter v4.1 official release, https://github.com/rsms/inter/releases/tag/v4.1 (Inter-4.1.zip, web/Inter-*.woff2), SIL Open Font License 1.1 (custom/fonts/inter/OFL.txt). Latin subset made with fontTools pyftsubset (same ranges as the existing Inter-ExtraBold.woff2, plus layout features kept); the 800 face is registered in footer.css. */ @font-face { font-family: "Inter"; src: url("../fonts/inter/Inter-Regular.woff2") format("woff2"); font-weight: 400; font-style: normal; font-display: swap; } @font-face { font-family: "Inter"; src: url("../fonts/inter/Inter-Medium.woff2") format("woff2"); font-weight: 500; font-style: normal; font-display: swap; } @font-face { font-family: "Inter"; src: url("../fonts/inter/Inter-Black.woff2") format("woff2"); font-weight: 900; font-style: normal; font-display: swap; } @font-face { font-family: "Kobe1.1"; src: url("../fonts/kobe1.1/Kobe1.1-Bold.woff2") format("woff2"), url("../fonts/kobe1.1/Kobe1.1-Bold.woff") format("woff"); font-weight: 700; font-style: normal; font-display: swap; } /* editor-friendly-ok - @font-face registers a font resource, it does not style any block, so the preset-var pattern does not apply here. The real Regular (400) cut, sourced 17 Sep 2026. Replaces the Bold-file stand-in that shipped in PR #740 as a documented deviation - see docblock. */ @font-face { font-family: "Kobe1.1"; src: url("../fonts/kobe1.1/Kobe1.1-Regular.woff2") format("woff2"), url("../fonts/kobe1.1/Kobe1.1-Regular.woff") format("woff"); font-weight: 400; font-style: normal; font-display: swap; } /* editor-friendly-ok. Figma's wishlist PRODUCT CARD price text (node #29323:47306, CU-86eyuup3c) is drawn in "Archivo Black", not Nominee or Kobe1.1. The audit of round 2's fixes (9 Sep 2026) found round 2's own attempt to approximate this by bumping font-weight to 900 on Kobe1.1 was a no-op, fixed properly here in round 3: Kobe1.1 only has 700/400 @font-face cuts registered above (Bold and, since 17 Sep 2026, a real Regular), so requesting 900 just falls back to 700 with no visual change, and no browser synthesizes bold on top of an already-bold face. Unlike Kobe1.1 (whose EULA is ambiguous on webfont conversion, see the docblock above), Archivo Black is SIL Open Font License, freely available via Google Fonts - the same route already used for footer.css's Inter eyebrow (CU-86eyv2c1y). Sourced the Regular (its only weight; the family name IS the weight) latin-subset .woff2 from Google Fonts, self-hosted at custom/fonts/archivo-black/. Registered as the "archivo-black" preset slug in homepage/homepage.php's wp_theme_json_data_theme filter, matching the Inter/Nominee/Kobe pattern; sites/bonza/custom/css/ wishlist-offcanvas.css's .ct-wishlist-card-price now reads var(--wp--preset--font-family--archivo-black, "Archivo Black", ...). */ @font-face { font-family: "Archivo Black"; src: url("../fonts/archivo-black/ArchivoBlack-Regular.woff2") format("woff2"); font-weight: 400; font-style: normal; font-display: swap; } /* editor-friendly-ok - global default for text outside the ~24 components that * already declare Nominee/Kobe1.1 by name; those only needed the @font-face * rules above. Closes the remaining gap for plain body/heading tags with no * component-specific rule. Same var(--wp--preset--font-family--*, literal) * fallback pattern the rest of the theme already uses, so the block editor's * Styles panel can still override per-block. * * !important on both rules: verified live on bonza-retheme.blz.au this pass - * without it, Blocksy's own parent-theme rule (main.min.css, "body, h1..h6 { * font-family: var(--theme-font-family) }") is equal specificity and loads * later in the cascade, so it wins the tie without !important here. * * Note the real mechanism, corrected after an audit caught an earlier wrong * claim here: !important is resolved BEFORE specificity, so these two rules * now win against every non-!important heading/body rule site-wide, not just * Blocksy's - including higher-specificity rules like #customer_login h2 on * the login page. That is the intended, brand-correct outcome (those elements * should render in Nominee/Kobe1.1 too), not a side effect to guard against - * but it means "higher specificity wins regardless of load order" is false; * !important is what actually wins here, for every non-!important competitor. */ body { font-family: var( --wp--preset--font-family--bhp-body, "Kobe1.1", var( --theme-font-family, sans-serif ) ) !important; } h1, h2, h3:not(.bhp-transparency-card h3), /* 86eyy8hud: Transparency-card h4s use the body font (Kobe1.1 substitute), not this heading font -- :not() keeps them out of this !important rule's match list so homepage.css's higher-specificity, non-!important rule wins cleanly instead of needing a second !important. */ h4:not(.bhp-transparency-card h4), h5, h6 { font-family: var( --wp--preset--font-family--bhp-heading, "Nominee", var( --theme-font-family, sans-serif ) ) !important; /* --theme-headings-font-family tier removed: defined nowhere in any deployed stylesheet (hover-type-contract.md typography section) -- this sitewide h1-h6 rule is the highest-impact place this dead tier existed, since it silently reached every heading on the site if the first two tiers ever both failed. */ }