hugo-architectlisted
Install: claude install-skill ralvarez-ai/ralvaskills
# Hugo Architecture
Targets **Hugo Extended 0.161** (Go-templated static-site generator). Cross-skill ties in [§12](#12-cross-skill-ties). Concrete skeletons in [RECIPES.md](RECIPES.md); pinned versions in [STACK.md](STACK.md).
## 1. Project layout & content organization
- **Standard top-level folders** — `content/`, `layouts/`, `assets/`, `static/`, `data/`, `i18n/`, `archetypes/`, `themes/` (if not module-mounted), `hugo.toml`. Skeleton in [RECIPES § Project tree](RECIPES.md#project-tree).
- **`content/` mirrors the URL structure.** Section folders (`content/posts/`, `content/docs/`) become URL prefixes; taxonomies are inferred from front matter, not folder names.
- **`assets/` for processed files; `static/` for pass-through.** Anything that needs fingerprinting, minification, transpilation, or image processing belongs in `assets/` and goes through Hugo Pipes. Truly static files (`robots.txt`, `favicon.ico`, prebuilt PDFs) go in `static/`.
- **`data/` for structured site data** — JSON/YAML/TOML files queryable via `site.Data.<file>`. Use for author lists, sponsor logos, redirect maps; do **not** use for content (that belongs in `content/`).
- **`archetypes/` define `hugo new` templates** — one per content section, with sensible front-matter defaults.
- **One repository per site by default.** Multi-site monorepos are an exception; reach for them only when ownership and deploy targets align.
## 2. Front matter conventions
- **TOML front matter** is the default (`+++` del