Launch developer journal as a Hugo site

Summary

Converted the centralized developer journal into a responsive Hugo site with project and tag archives, RSS output, normalized entry metadata, clean production builds, and compatibility with the Hugo version used by Cloudflare Pages.

Decisions

• Keep the site deployment-agnostic and store generated journal entries under Hugo’s content directory
• Use custom Hugo layouts and local styling instead of adding an external theme dependency
• Use the backward-compatible Language.Lang template field for hosted builds

Learnings

• Hugo uses taxonomy.html for individual tag result pages and terms.html for the tag index
• Hosted build environments should pin the Hugo version or avoid APIs unavailable in older releases