Hugo
otsumami.hugo
Static site generator written in Go that renders Markdown content into a complete HTML site, with layouts, taxonomies, multilingual support and asset processing built in.
A Docker Compose file for Hugo alone, generated from the catalog and checked by the safety inspector. Sign in and use Kitchen Credits to activate it.
Uses the Medusa cart and payment-session path. This test control does not create an order or capture payment.
Hugo reads a directory of Markdown content with front matter, applies Go templates arranged by content type and section, and writes a finished static site that any web server can serve. Builds are fast enough that a site of thousands of pages regenerates in seconds, and a development server rebuilds and reloads on file change. Taxonomies, menus, pagination, image processing, bundling and minification are part of the binary rather than a plugin layer, so a site has no runtime dependencies once built. A first deployment mounts a site directory, runs the development server and confirms a content change appears in the browser.
You know it worked when
- The development server starts and serves the site in a browser.
- A change to a Markdown file appears in the browser without a manual rebuild.
- A production build writes a complete static site to the output directory.
- Generated links resolve correctly when the output is served from its intended base URL.
Known sharp edges
- Themes commonly require the extended build for SCSS compilation, and a standard build fails on those sites with an error naming the missing feature rather than the cause.
- Template errors surface only for the content that triggers them, so a page type never exercised locally can break a production build.
- Themes installed as Git submodules are absent from a plain directory copy, producing a site that builds successfully with no styling.
- The base URL is compiled into generated links, so serving the output from a different path than configured yields broken navigation.