Updated hosting guides

tips & tricks
1

We have significantly updated the following hosting guides:

With these new instructions, build caching is now available for all of these providers, matching the capability already present for Netlify. This is a big win for any project that processes images.

Each setup has been thoroughly tested to exercise the following features/capabilities:

  • Import components from a Hugo module.
  • Import a theme as a Git submodule and render a shortcode from it.
  • Import a content file named hugö.md to verify that the Git core.quotepath setting is false.[1]
  • Extract the Git author date from the imported content.
  • Verify that the embedded link and image render hooks are enabled and functioning properly.
  • Perform vendor prefixing of CSS rules using the postcss, postcss-cli, and autoprefixer Node.js packages.
  • Transpile modern JavaScript syntax to a safe, cross-browser equivalent using the @babel/core, @babel/cli, and @babel/preset-env Node.js packages.[2]
  • Transpile Sass to CSS using Dart Sass.
  • Process CSS files using the tailwindcss and @tailwindcss/cli Node.js packages.
  • Decode and resize an AVIF image, then encode to all supported image formats.
  • Decode and resize a WebP image, then encode to all supported image formats.
  • Test Hugo’s build cache for image processing.

Please let me know if you run into any problems.

  1. See issue #9810. ↩︎

  2. For most modern projects, using Hugo’s built-in js.Build function is preferred over Babel, as it handles bundling and transpilation natively without requiring external Node.js dependencies. ↩︎

2

Thank you!