I’ve never used Victor Hugo. If you’re a beginner, I reckon you’re better off following the quick start and asking for help along the way. IMHO adding in webpack just makes things more complicated (and I don’t think it’s necessary now due to Hugo Pipes).
One of the mistakes you’re making is editing files in the site/layouts directory. Don’t do this! That’s the ‘theme’ of your site. You should only be fiddling with content and config.toml at this point. When you’re more familiar with Hugo, have a go at overriding a theme (or building your own). But for now, just get your site working both locally and on netlify.
Yes. I’m aware of working in Content, I was just copying over some existing html to get a quick preview. It would be easier for me to get rid of Victor, but just trying to learn some new tools. I appreciate your feedback though and I will consider the advantages of webpack over pipes.
I think the difference between the two is that typekit.net is already an external reference before build, while the css is getting bundled and served on a CDN. Was that what you meant?
If you do any SRI-fingerprinting via HUGO on your stylesheets, you have to DISABLE any “asset optimization” on these files in netlify. That’s normal. The fingerprint that Hugo does is a hash taken from the file-content HUGO is creating. So using Netlify’s asset optimization will change this content. Which makes the SRI-value invalid. Which leads to your stylesheets not loading.
So the rule is:
you do SRI on your stylesheets? Don’t enable optimization on styles on Netlify
you do SRI on your javascripts? Don’t enable optimization on javascripts on Netlify