Repository navigation
Conversation
Naming Inter as the heading and body family makes Mintlify load it a second time through Google's CSS API (fonts.googleapis.com and fonts.gstatic.com), on top of the Inter the mint theme already bundles under /_next/static/media. With the block gone the export matches docs-mantis: the same typeface, served from our own host, and no visitor request to Google. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Deploying with
|
| Status | Name | Latest Commit | Updated (UTC) |
|---|---|---|---|
| ✅ Deployment successful! View logs |
docs-privacycommand | 86ca2e5 | Oct 09 2026, 06:14 AM |
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
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
Removes the
fontsblock (heading.familyandbody.family= Inter) fromdocs.json.Why
Mintlify treats a bare
familyvalue as a Google Fonts family and emits a<link>tofonts.googleapis.com/css2?family=Inter…plus preconnects tofonts.gstatic.com. The mint theme already bundles Inter under/_next/static/media/through Next.js font optimisation, so the live site loads the same typeface twice, and only the Google copy sends the visitor's IP off-site. docs-mantis has nofontsblock and renders the identical Inter from the bundled files.After this change the export carries no request to Google. The
style-srcandfont-srcallowances forfonts.googleapis.com/fonts.gstatic.comin the privacykey.org transform rule's Report-Only CSP can be removed once this is deployed.If a non-default face is ever wanted, Mintlify's
source+format: woff2keys point at a file committed in the repo and never touch Google.🤖 Generated with Claude Code