Use shared assets for fonts instead of hot-linking Google Fonts

Open Beginner friendly
#42,965 6 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-2 days
Newbie friendliness
68/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Active
Tech stack
markdown
Domain
documentation

Research direction

Open the MDN font-stretch page and locate its 10 direct Google Fonts URLs. Review the mdn/shared-assets repository for the required fonts and the expected shared path, then replace the hot-links with local references. Done means all affected font files are available through shared-assets and the page no longer points to fonts.gstatic.com.

Written by the indexing model from the issue text.

Description

Content:CSS goal: best practices
MDN URL

https://developer.mozilla.org/en-US/docs/Web/CSS/Reference/Properties/font-stretch

What information was incorrect, unhelpful, or incomplete?

There are 10 cases where font files are directly hot-linked from Google Fonts servers. Since these URLs are not a part of the official API, they could disappear one day:

https://fonts.gstatic.com/s/[…].woff2
What did you expect to see?

Needed fonts added and linked from mdn/shared-assets

/shared-assets/fonts/[…].woff2
Dominant language
Markdown
Stars
11k
Forks
23.3k
Avg merge
1d 16h
Merged PRs (30d)
311

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from mdn/content

All issues in mdn/content

Similar issues

More Documentation issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.