Brian Coords

I haven't used GSAP + Understrap specifically, but can you share some of the code imports to see how your importing it. I also saw this: > The NPM files...

Also it should strip out the `'.git'` folder

And I've been messing with this: ```js const pkg = require('../../package.json') ... copyDir('./', `./dist/${pkg.name}-${pkg.version}`); ``` which would put your dist version in a subfolder like this: `dist/understrap-child-1.1.0/` or something similar....

I think this is feasible (assuming it passes testing). We'll put it on the roadmap to test.

This is one of those cases where pagespeed insights leads to design patterns that aren't actually ideal in the real world. @danemorgan makes a good point that `swap` looks funky...

Hitting this discussion again for the next release. A few thoughts: - For the Bootstrap 5 version, how about switching away from Font Awesome completely and moving to [Bootstrap Icons](https://icons.getbootstrap.com)?...

Adding a note here that there's been a lot of comments basically saying that the [sass-embedded](https://github.com/understrap/understrap/issues/1598) package doesn't work in all environments. So this may end up being a 'suggestion'...

I haven't tested this out yet, but in theory this _should_ be fine. Other plugins and child themes can still load jQuery if they need it- the [starter child theme](https://github.com/understrap/understrap-child/blob/main/functions.php)...

The more I think about this, the more I think it's a good thing: - Understrap still defaults to BS4, so most users won't be affected. - The child starter...

We should probably sync these up. I see no reason not to use v3 for all of them.