This is a comprehensive guide for spinning up Hugo sites without the usual config headaches. It walks you through the Extended vs Standard edition trap (most themes need Extended for SCSS support), sets you up with YAML configs for CMS compatibility, and includes actual working examples for PaperMod integration, Tailwind CSS v4 setup, and Cloudflare Workers deployment. The author clearly got burned by the common pitfalls because there are warnings everywhere about Git submodules, baseURL misconfiguration, and TOML vs YAML issues. Covers both quick blog setups and more complex scenarios like headless CMS integration with Sveltia or Tina. If you're tired of Hugo's cryptic error messages, this will save you hours.
$ npx -y skills add jackspace/claudeskillz --skill hugo --agent claude-codeInstalls into .claude/skills of the current project.
Status: Production Ready Last Updated: 2025-11-04 Dependencies: None (Hugo is a standalone binary) Latest Versions: hugo@0.152.2+extended, PaperMod@latest, Sveltia CMS@latest
CRITICAL: Always install Hugo Extended edition (not Standard) unless you're certain you don't need SCSS/Sass support. Most themes require Extended.
# macOS
brew install hugo
# Linux (Ubuntu/Debian)
wget https://github.com/gohugoio/hugo/releases/download/v0.152.2/hugo_extended_0.152.2_linux-amd64.deb
sudo dpkg -i hugo_extended_0.152.2_linux-amd64.deb
# Verify Extended edition
hugo version # Should show "+extended"
Why this matters:
# Use YAML format (not TOML) for better CMS compatibility
hugo new site my-blog --format yaml
# Initialize Git
cd my-blog
git init
Sponsors