<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Typography on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/typography/</link>
    <description>Recent content in Typography on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 08 Jun 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/typography/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Self-Hosted Font &amp; Icon Libraries: Fontsource vs Iconify API vs Material Design Icons</title>
      <link>https://www.pistack.xyz/posts/2026-06-08-self-hosted-font-icon-libraries-fontsource-iconify-material-design/</link>
      <pubDate>Mon, 08 Jun 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-06-08-self-hosted-font-icon-libraries-fontsource-iconify-material-design/</guid>
      <description>&lt;h2 id=&#34;introduction&#34;&gt;Introduction&lt;/h2&gt;&#xA;&lt;p&gt;Every modern website depends on external font and icon resources. Google Fonts serves over 50 billion font requests per month, and icon libraries like Font Awesome power the visual language of millions of interfaces. But relying on third-party CDNs comes with privacy implications, performance dependencies, and availability risks. When Google Fonts experiences an outage (as it has multiple times), thousands of websites render with fallback system fonts.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
