Integrate fathom analytics

[hola-soy-milk]

Closes #200

[vercel[bot]]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Updated
docs	✅ Ready (Inspect)	Visit Preview	Dec 19, 2022 at 4:51PM (UTC)

[github-actions[bot]]

4 total issues, 0 errors, and 4 warnings found for docs.suborbital.dev

Details

WARNING WCAG2AA.Principle1.Guideline1_3.1_3_1.H48 ```html

Skip to main content ``` This element has "position: fixed". This may require scrolling in two dimensions, which is considered a failure of this Success Criterion. ---
WARNING WCAG2AA.Principle1.Guideline1_4.1_4_3_F24.F24.FGColour ```html / ``` Check that this element has an inherited background colour or image to complement the corresponding inline foreground colour. ---
WARNING WCAG2AA.Principle1.Guideline1_4.1_4_3_F24.F24.FGColour ```html / ``` Check that this element has an inherited background colour or image to complement the corresponding inline foreground colour. ---

---

📝 docs | :octocat: repo | 🙋🏽‍♀️ issues | 🏪 marketplace | A11yWatch

[github-actions[bot]]

4 total issues, 0 errors, and 4 warnings found for docs.suborbital.dev

Details

WARNING WCAG2AA.Principle1.Guideline1_3.1_3_1.H48 ```html

Skip to main content ``` This element has "position: fixed". This may require scrolling in two dimensions, which is considered a failure of this Success Criterion. ---
WARNING WCAG2AA.Principle1.Guideline1_4.1_4_3_F24.F24.FGColour ```html / ``` Check that this element has an inherited background colour or image to complement the corresponding inline foreground colour. ---
WARNING WCAG2AA.Principle1.Guideline1_4.1_4_3_F24.F24.FGColour ```html / ``` Check that this element has an inherited background colour or image to complement the corresponding inline foreground colour. ---

---

📝 docs | :octocat: repo | 🙋🏽‍♀️ issues | 🏪 marketplace | A11yWatch

[callahad]

Would've expected the package-lock.json to get updated, too?

[hola-soy-milk]

Hold up, good catch. I just noticed we have both a package-lock and a yarn-lock.

[callahad]

haha, awesome. Otherwise LGTM

[github-actions[bot]]

4 total issues, 0 errors, and 4 warnings found for docs.suborbital.dev

Details

WARNING WCAG2AA.Principle1.Guideline1_3.1_3_1.H48 ```html

Skip to main content ``` This element has "position: fixed". This may require scrolling in two dimensions, which is considered a failure of this Success Criterion. ---
WARNING WCAG2AA.Principle1.Guideline1_4.1_4_3_F24.F24.FGColour ```html / ``` Check that this element has an inherited background colour or image to complement the corresponding inline foreground colour. ---
WARNING WCAG2AA.Principle1.Guideline1_4.1_4_3_F24.F24.FGColour ```html / ``` Check that this element has an inherited background colour or image to complement the corresponding inline foreground colour. ---

---

📝 docs | :octocat: repo | 🙋🏽‍♀️ issues | 🏪 marketplace | A11yWatch

[hola-soy-milk]

Ok, so I thought we had to install via yarn, but it turns out npm install did the trick.

Do we maybe want to see about eliminating one of the two? Having one single source of truth when it comes to dependencies might be a best bet here.

I get nervous about having both a yarn.lock and a package-lock

[hola-soy-milk]

For reference: The website repo has both checked in but refers to yarn in the README

[callahad]

Yeah. Website should canonically be Yarn. Docs should canonically be NPM.

After merging this PR we should drop the mention of Yarn in the Docs README (and in the docs themselves, probably. folks using yarn know how to use yarn).

We should probably switch the website over to npm from Yarn, too, though that'll also require updating the vercel config (ideally via a PR to the suborbital/fleet repo)

[hola-soy-milk]

I'm +1 on this. Just integrating fathom into Network which uses npm and the consistency advocate in me is eager.

In the meantime, is this good to go?