docs: fix the Montserrat font URL so headings actually use it - #1503
docs: fix the Montserrat font URL so headings actually use it#1503masiarek wants to merge 1 commit into
Conversation
The Google Fonts link in head_custom.html is malformed and returns HTTP 400, so the font never loads: family=Montserrat,wght@0,100..900;1,100..900 -> 400 family=Montserrat:ital,wght@0,100..900;1,100..900 -> 200 The ital axis needs a colon before it, not a comma. Google's css2 syntax is family=<Name>:<axis-list>@<values>, so the original reads "Montserrat" with a stray "wght@..." rather than an axis spec, and the API rejects it. Effect: _sass/custom/custom.scss sets h1-h6 to 'Montserrat', Verdana, sans-serif, so headings have been falling back to Verdana this whole time. (Body text is Verdana by design -- the `*` rule -- so only headings change.) Also means every page load has been making a render-blocking request to a URL that can only fail. Worth noting this does not make the site faster: it replaces a failed request with a successful one, so the font now actually downloads. The point is correctness, not performance. One character. Verified by building locally and re-requesting the emitted URL: now 200, and it serves Montserrat with weights 100-900 in normal and italic, with font-display: swap.
✅ Deploy Preview for bettervoting ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
Warning Review limit reached
Next review available in: 38 minutes You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
1 participant
The Google Fonts link in
_includes/head_custom.htmlis malformed and returns HTTP 400, so Montserrat never loads.The
italaxis needs a colon before it, not a comma. Google'scss2syntax isfamily=<Name>:<axis-list>@<values>, so the current URL reads as the familyMontserratfollowed by a straywght@…, and the API rejects the whole request.What it affects
_sass/custom/custom.scsssets:So headings have been falling back to Verdana. Body text is Verdana by design, so nothing else changes — this only restores the intended heading typeface.
Secondary effect: every page load has been making a render-blocking request to a URL that can only 400.
Not a performance fix
Worth being straight about this — it replaces a failing request with a successful one, so the font now actually downloads. Pages will look the way they were designed to; they won't load faster.
Verified
Built the site locally and re-requested the emitted URL: 200, serving Montserrat at weights 100–900 in normal and italic, with
font-display: swap.Optional follow-up, not included
Since only
h1–h6use Montserrat and they're allfont-weight: bold, the italic axis and the full 100–900 range aren't strictly needed —family=Montserrat:wght@700would be a smaller download. I've kept this PR to the one-character correctness fix rather than changing what gets requested; happy to follow up if you'd like the trim.