b8202f53 Use 'w' units instead of 'x' for responsive images in showcase
git-subtree-dir: themes/gohugoioTheme
git-subtree-split: b8202f539d57b5e8e2c740cfde3d5f5e5f66e3b6
The advice in this page is actually the opposite. Relative URLs output the wrong URL for theme assets on the Hugo website.
See relevant advice in the repository's [README](https://github.com/gohugoio/hugoThemes#common-permalink-issues)
I hadn't noticed this page (if I had noticed I would have sent a PR earlier because the advice offered here is plain wrong).
The reason I am merging this PR right away is due to [this](https://github.com/gohugoio/hugoThemes/issues/504#issuecomment-443253163) comment by a confused theme author.
If you feel that this could be improved feel free to reword and amend as you see fit but the bottom line is that for themes that are going to be published on Hugo Themes authors should create absolute paths in their templates.
cc: @bep @digitalcraftsman @kaushalmodi
PurgeCSS removes unused CSS from the output. This PR only uses PurgeCSS on the base utility classes to avoid unexpected issues where JS or content-based classes get removed.
* Swap src for assets directory
Assets directory is the default for Hugo Pipes
* Use "Typefaces" package
This method is cleaner because we can pull in our fonts with a require statement https://github.com/KyleAMathews/typefaces
* Use Hugo Pipes method of calling resources
* Update dependencies
* [wip] Revamp Webpack
* Tweak Webpack for Tachyons
* Use simple build scripts
* Update dependencies
* Fix content that referenced files that don't exist
* Add all scripts
* Improve styles/js preload and cache
* Add to whitelist
* Add fonts to headers for preload
* Move preloads to header file
* Update styles
* Improve manifest usage
The manifest partial was in the site but not included in head
* Update readme
* Remove extra check on asset resources
* Call assets directly in header file
Bjørn Erik Pedersen