docs: remove empty fonts config causing malformed Google Fonts requests - #458
Open
ketanyekale wants to merge 1 commit into
Open
docs: remove empty fonts config causing malformed Google Fonts requests#458ketanyekale wants to merge 1 commit into
ketanyekale wants to merge 1 commit into
Conversation
fonts.heading.family and fonts.body.family were empty strings, which made Mintlify request https://fonts.googleapis.com/css2?family=:ital,... with no family name on every page load. Google returns an error page, which Chrome reports as CORB-blocked / failed stylesheet. The site already renders with Mintlify's default font stack, so removing the block changes nothing visually and drops two guaranteed-failing requests per page. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Deletes the
fontsblock fromdocs.json:Why
The empty
familystrings make Mintlify build a Google Fonts URL with no font name —css2?family=:ital,wght@0,400;…— on every page load. Google returns an error page, and Chrome DevTools flags it as CORB-blocked response + failed stylesheet (2 failing requests per page view, visible in the Issues panel on production).The site already renders with Mintlify's default font stack (the custom-font request has never succeeded), so removing the block changes nothing visually — it just eliminates the guaranteed-failing requests. If a custom font was ever intended, it can be re-added with a real family name.
Unrelated to the version-selector Error 500 investigation (#457) — this is independent cleanup found while debugging it.
🤖 Generated with Claude Code