This is the ”how” companion to ”Deconstructing the ‘Neutral’ Web.” You understand the why—now let’s build a portfolio that respects privacy, equity, and sovereignty. This guide walks you through the steps, from auditing your stack to launching a compliant site.

1. Audit Your Stack: Know Your Dependencies 🔍

Before you build, investigate. Every external resource is a dependency.

• Fonts: Are they from Google Fonts or self-hosted?
• Libraries: Is jQuery, Font Awesome, or GSAP loaded from a CDN?
• Media: Are you using YouTube or Vimeo embeds?
• Analytics: Are you using Google Analytics?

💡 Pro Tip: Open your browser’s Developer Tools → Network tab. Reload your page. Every request to an external server (like fonts.googleapis.com) is a potential FIPPA compliance issue.

2. Self-Host Your Assets ✅

Bring your fonts, libraries, and media in-house.

Fonts:

1. Download your chosen font from Google Fonts (ensure licensing allows it).

2. Create a /fonts directory in your project.

3. Use @font-face to reference the local files.

   /* Self-hosted font example */@font-face {
     font-family: 'Roboto';
     src: url('/fonts/roboto-regular.woff2') format('woff2');
     font-weight: 400;
     font-style: normal;
   }
   body {
     font-family: 'Roboto', sans-serif;
   }
   

Libraries:

• Don’t use: <script src="<https://cdnjs.com/jquery.js>"></script>
• Do this: Download the library, add it to a /js folder, and use: <script src="/js/jquery.js"></script>

Videos: