Hugo Module Mounts

Mount multiple directories into Hugo's content tree via module.mounts configuration.

3|1|Updated Feb 8, 2026
One-click install
npx skills add https://github.com/therealbill/mynet --skill hugo-module-mounts
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Hugo Module Mounts
Source: https://github.com/therealbill/mynet/tree/main/hugo-repo/skills/hugo-module-mounts
Command: npx skills add https://github.com/therealbill/mynet --skill hugo-module-mounts

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Hugo sites often need content from multiple repositories or subdirectories. This skill provides a pattern to mount multiple directories into Hugo's content tree, creating a unified, symlink-free filesystem view for a single site.

Core Features & Use Cases

  • Multi-directory content aggregation using Hugo's module mounts ([[module.mounts]]).
  • Replaces default mounts by mapping standard directories (content, static, layouts, data, assets, i18n, archetypes) and custom mounts.
  • Examples: monorepos with per-plugin/docs, per-service/docs, or tools/docs, resulting in a cohesive site without duplicating files.

Quick Start

Create or update hugo.toml with module.mounts entries that map source directories to targets, ensure parent sections have _index.md, and start the Hugo server to verify a unified multi-directory site.

Frequently Asked Questions about Hugo Module Mounts

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

FAQPage Schema
How do I combine documentation from multiple directories into a single Hugo site?

To combine documentation into a single Hugo site, use Hugo module mounts to map multiple source directories into the content tree, creating a unified, symlink-free filesystem view for your site.

What is the best way to aggregate scattered docs in a monorepo using Hugo?

The best way to aggregate scattered docs in a monorepo is configuring Hugo module mounts to map per-plugin or per-service documentation directories into a cohesive site with consistent navigation.

Does Hugo module mounts replace default directory mappings for content and static files?

Yes, using module mounts replaces default mappings by explicitly defining targets for standard directories like content, static, layouts, data, assets, i18n, and archetypes.

How do I set up Hugo module mounts for multi-directory content aggregation?

To set up multi-directory content aggregation, update hugo.toml with [[module.mounts]] entries mapping source directories to targets, ensure parent sections have an _index.md file, and start the Hugo server to verify.

Why do my mounted documentation sections not appear in Hugo site navigation?

Mounted documentation sections may not appear if parent sections lack an _index.md file; ensuring these index files exist satisfies standard section requirements and enables consistent site navigation.

Can I use Hugo module mounts without duplicating files across repositories?

Yes, Hugo module mounts create a unified site view without duplicating files, allowing you to aggregate content from multiple repositories or subdirectories into a single cohesive documentation site.