The production site is built from Hugo source under docs/. The legacy root site remains untouched as a rollback reference while the migration settles.

Hugo preview

Requires Hugo Extended v0.164.x:

hugo server --source docs --bind 127.0.0.1 --port 4173 --disableFastRender
# open http://127.0.0.1:4173

Production-equivalent strict build:

hugo --source docs --destination public --gc --minify --panicOnWarning \
  --baseURL "https://mop.vapor-sea.space/"
test -s docs/public/index.html

docs/public/ is generated and ignored.

Migration layout

docs/content/_index.md — single-page narrative source
docs/content/{installation,workflow,development,deployment,architecture,troubleshooting}/ — standalone documentation sections
docs/layouts/ — project-owned Hugo templates and partials
docs/layouts/_default/{single,list}.html — documentation page shells
docs/layouts/shortcodes/ — workflow, integration, outcome, and product-shot components
docs/assets/css/site.css — black/gold Vapor Sea design system
docs/assets/js/site.js — header/reveal/review behavior
docs/assets/images/screenshots/ — six reviewed workflow captures; Hugo generates responsive WebP derivatives
design/2026-08-20-hugo-site-publishing-design.md — architecture, migration, and cutover design
index.html, styles.css, script.js, assets/ — temporary production rollback site

The accepted installation scope is source development plus the existing Kubernetes/operator path. Do not advertise Docker Compose until vapor-sea/mop provides and tests it.

Publishing target

master/docs → Gitea Action → publish branch → git-sync/nginx/Caddy

.gitea/workflows/hugo-publish.yml builds Hugo after relevant pushes to master and publishes generated root files to the machine-owned publish branch. Production git-sync follows publish; do not edit generated files there manually. The six screenshot-backed workflow sections are live at the public URL.

Source application: https://git.r3r4um.online/vapor-sea/mop

Public URL: https://mop.vapor-sea.space/