/* ============================================================
   Self-hosted faces.

   These used to come from fonts.googleapis.com and api.fontshare.com.
   Both CDNs serve their STYLESHEETS to any origin but reject the FONT
   FILES for origins they do not recognise, and font files are fetched
   in CORS mode where stylesheets are not. The symptom is the page
   loading with the right CSS and the wrong typeface, which is what
   happened the first time the site was shared over an ngrok domain:
   api.fontshare.com and fonts.googleapis.com returned 200, and every
   request to cdn.fontshare.com and fonts.gstatic.com failed.

   Self-hosting removes both third parties from the critical path. It
   also removes two DNS lookups and two TLS handshakes before the first
   glyph, which is the reason to do it even where the CDNs would have
   worked.

   Sora is variable: one file covers the whole weight axis, so it is
   declared once with a range rather than three times with a number.
   Satoshi ships static instances, so it takes one file per weight.
   Latin subset only. The site's one non-latin glyph is the arrow in
   "6.8 -> 5.7", which fell back to a system face on the CDN build too.
   ============================================================ */

@font-face {
  font-family: "Sora";
  src: url("assets/fonts/sora-var.woff2") format("woff2");
  font-weight: 100 800;
  font-style: normal;
  font-display: swap;
}

@font-face {
  font-family: "Satoshi";
  src: url("assets/fonts/satoshi-400.woff2") format("woff2");
  font-weight: 400;
  font-style: normal;
  font-display: swap;
}
@font-face {
  font-family: "Satoshi";
  src: url("assets/fonts/satoshi-500.woff2") format("woff2");
  font-weight: 500;
  font-style: normal;
  font-display: swap;
}
@font-face {
  font-family: "Satoshi";
  src: url("assets/fonts/satoshi-700.woff2") format("woff2");
  font-weight: 700;
  font-style: normal;
  font-display: swap;
}