fontsource.org valid

Documentation

For agents: Fontsource docs for self-hosting open-source web fonts via npm packages: installing, variable fonts, subsets, font-display, preloading and CDN usage.

open-source fontsself-hosting fontsvariable fontsfont-displaynpm font packages

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-21T14:34:36.563Z. Cached copy · Source on fontsource.org

# Documentation

- Getting Started

  - **Contents**
  - [Introduction](/docs/getting-started/introduction): Learn why and how to self-host open-source fonts with Fontsource.
  - [Installing Fonts](/docs/getting-started/install): Install Fontsource packages and import fonts into a bundled web application.
  - [Variable Fonts](/docs/getting-started/variable): Install, import, and configure variable font packages from Fontsource.
  - [Individual Subsets](/docs/getting-started/subsets): Import individual Fontsource language subsets and font variants.
  - [Font Display](/docs/getting-started/display): Configure the CSS font-display behavior used by Fontsource fonts.
  - [Preloading Fonts](/docs/getting-started/preload): Preload critical Fontsource font files without overloading initial page requests.
  - [CDN](/docs/getting-started/cdn): Load versioned Fontsource stylesheets and font files through the jsDelivr CDN.
  - [FAQ](/docs/getting-started/faq): Find answers to common Fontsource installation, bundler, and package questions.
  - [AI and LLMs](/docs/getting-started/ai-and-llms): Use Fontsource documentation with AI coding assistants and LLM tools.

  - **Icons**
  - [Material Icons](/docs/getting-started/material-icons): Install and use Material Icons font packages from Fontsource.
  - [Material Symbols](/docs/getting-started/material-symbols): Install and customize variable Material Symbols packages from Fontsource.

  - **Sass**
  - [Sass Introduction](/docs/getting-started/sass-introduction): Configure Dart Sass package imports for Fontsource font packages.
  - [Sass Import](/docs/getting-started/sass-import): Import Fontsource CSS stylesheets in Sass and SCSS with the @use rule.
  - [Faces Mixin](/docs/getting-started/faces-mixin): Generate customized @font-face rules with the Fontsource Sass Faces mixin.
  - [Generator Mixin](/docs/getting-started/generator-mixin): Generate advanced Fontsource CSS with fine-grained Sass configuration.

  - **Migration**
  - [Migrating to V5](/docs/getting-started/migrate-v5): Migrate Fontsource projects to v5 package names, imports, Sass, and metadata.
- Guides
  - [Framework Guides](/docs/guides): Guides for using Fontsource with frameworks, UI libraries, build tools, and integrations.

  - **Frameworks and Integrations**
  - [Angular](/docs/guides/angular): Install, import, and use Fontsource packages in an Angular application.
  - [Astro](https://docs.astro.build/en/guides/fonts/#using-fontsource)
  - [Chakra UI](https://chakra-ui.com/guides/theming-add-custom-font-to-vite)
  - [Fontsource for Flutter](https://pub.dev/packages/fontsource)
  - [Gatsby](https://www.gatsbyjs.com/docs/how-to/styling/using-web-fonts/#self-host-google-fonts-with-fontsource)
  - [Laravel](https://laravel.com/docs/13.x/vite#font-providers)
  - [Material UI](https://mui.com/material-ui/react-typography/#roboto-font)
  - [Next.js](/docs/guides/nextjs): Install and use Fontsource packages with the Next.js App Router or Pages Router
…

Related sites

Other listed sites in Developer tools. See the whole category →

Machine-readable: GET /v1/resolve?q=fontsource.org · GET /v1/domain/fontsource.org · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for fontsource.org:
1. POST https://agentwebmap.com/v1/sites/fontsource.org/claims and keep claim_id and claim_secret private.
2. Publish the proof: add the line "AgentWebMap ownership: <token>" (token from step 1) to https://fontsource.org/llms.txt, or use the DNS, meta-tag or well-known method the response describes.
3. POST https://agentwebmap.com/v1/sites/fontsource.org/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/fontsource.org).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.