Project Setup Overview

foxynet

What’s in place

  • Hugo extended + Ananke: config/_default/hugo.toml points at the vendored Ananke theme (themes/gohugo-theme-ananke), keeps robots.txt and sitemap enabled, and sets blog permalinks like /blog/2024/05/my-post/.
  • Site params: config/_default/params.toml holds metadata (description, author, social handles) plus slots for SEO defaults and analytics IDs (Plausible/GA). Values are mostly placeholders until real links are added.
  • Navigation: config/_default/menus.toml defines Home, Blog, and About links; extend this when more pages land.
  • Content structure: The default archetype (archetypes/default.md) includes front matter for title, date, draft, description, summary, tags, and categories. Content lives under content/ with _index.md for the homepage and sample posts in content/blog/.

Build and deploy

  • Local dev: Run hugo server -D from the repo root to serve drafts and iterate locally.
  • CI: .github/workflows/hugo.yml checks pushes/PRs on main using the latest Hugo extended and runs hugo --gc --minify.
  • Amplify option: amplify.yml installs Hugo 0.152.2, builds with a local cache (.hugo_cache), and publishes public/. Use this for private-repo hosting or switch to GitHub Pages via the workflow.

Guardrails to keep

  • Follow coding/content standards in CODING_STANDARDS.md (front matter completeness, semantic HTML, tidy formatting).
  • Update PLAN.md when scope changes and keep AGENTS.md ownership notes in mind.
  • Before deploying, run hugo --gc --minify and ensure hugo server is clean locally.