Statamic Google Fonts Laravel Package

Product Decisions This Supports

• Compliance-driven feature work (GDPR/DSGVO, CCPA-adjacent): This Statamic addon self-hosts Google Fonts, removing third-party requests to fonts.googleapis.com / fonts.gstatic.com. It directly closes a legal-review finding that commonly blocks launch for EU-facing sites — a decision that is otherwise resolved by a legal opinion, a cookie-consent change, or an engineering project.
• Build vs. buy for typography delivery: The alternative is a bespoke font pipeline (download, subset, version, generate @font-face CSS, cache-bust, wire into the CP for editors). This package buys that for the cost of a Composer dependency and a config file — strongly favours buy unless you already own a design-system font pipeline.
• Editor experience / design autonomy: Designers keep picking from the Google Fonts library in the Control Panel rather than filing a ticket for each new typeface. This reduces the design-to-publish cycle and keeps typography a marketing decision rather than an engineering one.
• Roadmap input: If the roadmap includes privacy hardening, Core Web Vitals work, or a design-system refresh, this is a low-cost enabler for all three. The 2.1.3 patch specifically improves URL resolution when fonts are served from the same host — relevant to multi-domain, staging, and local-development setups, and reduces "fonts work in production but not in staging" support load.
• Use cases where it pays off fastest: marketing/brochure sites, public-sector and healthcare properties, EU-headquartered brands, agency-built Statamic sites handed to non-technical editors, and any project where legal has already flagged Google Fonts.

When to Consider This Package

Adopt when:

• The stack is Statamic (this is a Statamic addon, not a general Laravel package) and a legal/privacy review has flagged Google Fonts CDN usage, or you expect one to.
• Editors or designers need self-service access to the Google Fonts library without engineering involvement.
• You want a supported, maintained wrapper rather than hand-rolling font downloads and @font-face generation.
• You are on a current Statamic major and can absorb a routine patch upgrade — 2.1.3 is a patch-level URL-behaviour fix with no breaking changes, no migrations, and no config changes implied.

Look elsewhere when:

• The application is Laravel but not Statamic — use a general font self-hosting approach (e.g. spatie/laravel-google-fonts) or a build-time asset pipeline instead.
• Performance budgets demand aggressive subsetting, variable-font tuning, preloading, or critical-CSS inlining at build time — a runtime CP-driven downloader is the wrong layer for that; own it in Vite/your asset pipeline.
• You need fonts served from a CDN or a dedicated asset domain with fine-grained cache control.
• You require enterprise support SLAs or vendor indemnification — this is a small, single-maintainer open-source addon; budget a fallback plan (checked-in static .woff2 files) in case maintenance lags.
• Your font set is fixed and small — a one-off manual self-host may be less surface area than a dependency.

How to Pitch It (Stakeholders)

For executives: This is a small, cheap fix for a recurring legal risk. Serving Google Fonts from Google's servers exposes visitor IPs and has drawn fines and warning letters in the EU. This addon downloads the fonts once and serves them from our own domain, so we keep the design freedom of Google Fonts without the third-party transfer. Cost is a Composer dependency and a short config change; the alternative is custom engineering plus ongoing maintenance, or a legal workaround that degrades the design. Recommendation: adopt on Statamic properties with EU traffic, and treat it as a compliance control rather than a feature.

For engineering: A maintained Statamic addon that pulls Google Fonts locally, generates the @font-face CSS, and exposes font selection in the Control Panel. Low integration surface: install, publish config, choose fonts, done. 2.1.3 is a patch — it refines URL behaviour when fonts are served from the same host, which tightens multi-domain, staging, and local-dev behaviour. No breaking changes, no migrations, no action beyond a routine version bump and a smoke test of typography on staging.

For design/marketing: You keep the Google Fonts library and the CP picker; nothing about your workflow changes except that fonts are served from our domain. Note the one real trade-off — fonts are no longer automatically updated or optimised by Google, so adding or changing a typeface means a save in the CP rather than an implicit CDN update.