Swap this site with existing live site

[JasonYao]

make sure that this won't mess up existing MX records for email delivery, or the current builds for resume/ other builds.

It actually might, since we'd in theory be pointing it to 2 different hosts. got to think through this a bit, and either bite the bullet and migrate other repos off of github (ideally not because laziness and vendor lock-in to netlify), or see if there's an alternative possible

[JasonYao]

Some thoughts:

Goals

• Get new hugo-based site up on the domain jasonyao.com
• Not break existing artifact deploys like resume and weekly planner that utilize github pages
• Not have to transfer domain from cloudflare
• Ideally be able to use a CMS backend, e.g. netlify's git gateway and CMS backend out of the box

Thoughts

Current approach

• Github as webhost
• Cloudflare as domain registrar, CDN, and TLS cert provider
• No CMS backend

What's wrong with the current approach?

• Honestly, not much. It's not like it's been an issue the past however many years using this setup, and while there are new features such as a live CMS, or instant reverts from netlify that are nice, it's still up in the air for whether the extra work is worth it over just deploying on GitHub Pages and calling it a day
  • And while some features like netlify's git gateway + CMS are nice, it's highly unlikely that there'd be other users besides me that actually create content for this blog. YAGNI for sure here, even though it sounds nice on the surface.

Path forward

• Keep to existing approach for now, and if the lack of forms, lambdas, CMS, or whatever else becomes an issue, then we can revisit migrating from GitHub Pages, but no need to change for now.

[JasonYao]

Current status

• Swapped, though some bugginess still exists that needs to be looked into

Bugs

• [x] Occasionally the site will load with unstylized assets, and other times it will load just fine

  

• [x] The /resume/ path doesn't work for some reason, even though I can see the generated index.html file just fine

• [x] 404 page doesn't show up, even though it's generated correctly

[JasonYao]

Issue with the weird unstylized assets on firefox is related to this issue mentioned here: https://github.com/envygeeks/jekyll-assets/issues/582#issuecomment-564347020

In theory FF's bug is fixed, but since we're still seeing it now 5 years later, i'm going to give the workaround a try, and use sha-384 instead of the SHA-256/512 ones

[JasonYao]

manual SHA generation can be done with https://www.srihash.org/, and docs for doing this in hugo can be found at https://gohugo.io/hugo-pipes/fingerprint/

[JasonYao]

Nice, swapping all SHA integrity hashes to SHA-384 now causes everything to work as expected (changeset in https://github.com/JasonYao/JasonYao.github.io/commit/9d9baface42329e668953071fece4b1f6e85710e)

[JasonYao]

For the /resume path not showing up, I think I figured it out- it's because my github repo is called resume, so because of that path, it delegates to the repo, but that repo doesn't have an index.html file.

[JasonYao]

Some solutions:

1. Add as part of CD the ability to push the resume/index.html file to the publishing branch in the resume repo
2. Rename the route from resume to something else (work, business, cv, etc.)
3. Option 1 but be lazy and just upload the resume/index.html as a one-time thing for now, and add in to CD later

~For now, I'll go with option 1~ Chose option 3 since it's now working to get other stuff working, and making an issue to wire into CD

[JasonYao]

Resume route now fixed with https://github.com/JasonYao/resume/commit/f5a3b27206fcc1b6a9abd93f25d50d842a8a3523