hugo-docs

Coordinate Hugo documentation content and trigger website rebuilds via repository_dispatch.

25|7|Updated Mar 4, 2019
One-click install
npx skills add https://github.com/smart-swimmingpool/pool-controller --skill hugo-docs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hugo-docs
Source: https://github.com/smart-swimmingpool/pool-controller/tree/main/.opencode/skills/hugo-docs
Command: npx skills add https://github.com/smart-swimmingpool/pool-controller --skill hugo-docs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Hugo-based docs for pool-controller can become fragmented across EN/DE variants, versioning, and deployment steps. This Skill provides a centralized workflow to keep docs aligned, trigger builds, and publish to the website.

Core Features & Use Cases

  • DOC structure management: maintain docs/ in Hugo frontmatter conventions, bilingual pages, and menu integration.
  • Deployment orchestration: trigger repository_dispatch to smart-swimmingpool/website to rebuild and publish to smart-swimmingpool.com.
  • Version and i18n compliance: ensures consistent versioning strings and English/German variants are up-to-date for end users.

Quick Start

Follow the documented process to align docs/ with Hugo conventions and trigger the website deployment.

Frequently Asked Questions about hugo-docs

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate Hugo documentation deployment for bilingual EN/DE website variants?

Automate Hugo documentation deployment by coordinating content in docs/ and triggering website rebuilds via repository_dispatch. This ensures EN/DE language variants, menus, and versioning stay aligned and publish correctly.

What frontmatter conventions are required for Hugo docs pages to publish correctly?

Hugo docs frontmatter must include type: docs, menu, and weight fields to satisfy publishing conventions. Maintaining these fields ensures pages integrate properly with menus and version management workflows.

How does a two-repo publish flow work for Hugo documentation websites?

A two-repo publish flow triggers a repository_dispatch from the docs repository to the website repository, causing the website repo to rebuild and deploy updated Hugo content automatically.

Can I manage Hugo documentation versioning and i18n compliance across multiple language variants?

Yes, you can manage Hugo documentation versioning and i18n compliance by coordinating English and German variants within docs/. This ensures consistent version strings and up-to-date localized content for end users.

What is the best way to maintain Hugo docs structure across menus and version updates?

The best way to maintain Hugo docs structure is centralizing content coordination in docs/ while enforcing frontmatter conventions and menu integration. This triggers automated rebuilds and keeps versioning consistent.

Why are my Hugo documentation pages not appearing in the website menu after deployment?

Hugo documentation pages may not appear in the menu if frontmatter lacks required type: docs, menu, or weight fields. Ensuring these conventions are met allows proper menu integration during deployment.