Community: Hugo adapter (third-party plugin)

[PythonWoods-Dev]

Summary

Create a third-party adapter package (zenzic-hugo) that teaches Zenzic to understand Hugo documentation projects.

Important: This is an external plugin, not a core change

Zenzic's architecture supports third-party adapters via the zenzic.adapters entry-point group. Hugo support should be shipped as a separate Python package, not added to the core repository. See Writing an Adapter for the full guide.

Scope

The adapter package should:

• Parse hugo.toml / config.toml as plain text to extract baseURL, contentDir, and defaultContentLanguage (Pillar 2: no subprocesses)
• Implement the BaseAdapter protocol (~5 methods, see src/zenzic/core/adapters/_base.py)
• Handle Hugo front matter (slug, url, draft)
• Register via entry-point in its own pyproject.toml:

[project.entry-points."zenzic.adapters"]
hugo = "zenzic_hugo:HugoAdapter"

Reference

• Adapter protocol: BaseAdapter
• Example adapter: DocusaurusAdapter (~589 LOC)
• Guide: Writing an Adapter

Why external?

The core ships 4 adapters that the team dogfoods directly (MkDocs, Docusaurus, Zensical, Vanilla). Community-driven adapters live as independent packages — no Zenzic release required to add engine support.

[snakefood3232]

I'll implement the HugoAdapter that satisfies BaseAdapter by parsing hugo.toml/config.toml for baseURL and contentDir, then mapping content files to routes with proper front matter handling. I'll follow the existing adapter patterns (~200 LOC) and add comprehensive tests. Can have a PR ready in 1-2 days with full test coverage.

[snakefood3232]

I'll implement the HugoAdapter following the BaseAdapter protocol, parsing hugo.toml and handling front matter like slug/url/draft. I'd structure it similarly to the Docusaurus adapter with route mapping and config extraction. Can have a PR with tests ready in 24 hours — I've built several static site adapters for similar documentation toolchains.