hugo-architectlisted

# Hugo Architecture Targets **Hugo Extended 0.161** (Go-templated static-site generator). Theme styling integrates with [ui-ux-architect](../../frontend/ui-ux-architect/SKILL.md); Go template syntax overlaps with [go-architect](../../languages/go-architect/SKILL.md); deploy pipelines follow [ci-cd-architect](../../infra/ci-cd-architect/SKILL.md). 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 reposi