Lint passes fail with image / font preconnect warnings — investigate #5

Closed
opened 2026-08-03 14:37:12 +00:00 by Mark · 1 comment
Owner

index.html has two preconnect links to Google Fonts (fonts.googleapis.com, fonts.gstatic.com) plus an external stylesheet. There's no documentation in the repo about whether Google Fonts is intentional or a generator leftover.

Questions to answer:

  1. Is the /public/ directory already self-hosting the fonts? If so, drop the external link.
  2. If external fonts are required, do we want to ship a CSP that allows only specific hosts?
  3. Should we add a <link rel="dns-prefetch"> for the scadforge CDN if the export pipeline needs it (currently unused)?

Acceptance: Either a doc-comment in index.html explaining the choice, or a static-font replacement.

Labels: documentation

`index.html` has two `preconnect` links to Google Fonts (`fonts.googleapis.com`, `fonts.gstatic.com`) plus an external stylesheet. There's no documentation in the repo about whether Google Fonts is intentional or a generator leftover. **Questions to answer:** 1. Is the `/public/` directory already self-hosting the fonts? If so, drop the external link. 2. If external fonts are required, do we want to ship a CSP that allows only specific hosts? 3. Should we add a `<link rel="dns-prefetch">` for the scadforge CDN if the export pipeline needs it (currently unused)? **Acceptance:** Either a doc-comment in `index.html` explaining the choice, or a static-font replacement. Labels: documentation
Author
Owner

Closed: documentation fix landed as d98f996. A doc-comment in index.html explains why fonts are loaded from Google Fonts (Inter, JetBrains Mono, Space Grotesk) rather than self-hosted, answering all three questions in the issue body.

Closed: documentation fix landed as `d98f996`. A doc-comment in index.html explains why fonts are loaded from Google Fonts (Inter, JetBrains Mono, Space Grotesk) rather than self-hosted, answering all three questions in the issue body.
Mark closed this issue 2026-08-04 04:12:31 +00:00
Sign in to join this conversation.
No description provided.