Tools that make authoring Hugo sites nicer — for editors, theme authors, and the people who maintain both.

Hugo is a great static-site generator with a sharp edge for editors: front-matter is YAML/TOML/JSON, content is Markdown with shortcodes, data lives in CSV/JSON, themes pull params from any of three different files. CMS layers usually solve one slice and lose the rest. hugo-tools is the home of projects that try to fix that.

A native desktop app (macOS / Windows / Linux) built with Tauri 2 + React that covers the whole site — content, menus, data, theme files, media, git, live preview — behind schema-driven forms. Format-preservation is non-negotiable: edits keep your TOML / YAML / JSON byte-for-byte intact when they don't need to change.

A Python tool that streams a mysqldump of a WordPress site and emits a Hugo or Jekyll content tree on the other side: posts and pages with proper front matter, [caption] / [gallery] / FinalTiles shortcodes resolved to first-class gallery directives, Elementor content rendered to plain HTML, optional theme scaffolding (PHP → Liquid for Jekyll, PHP → html/template for Hugo). Distributed as a GHCR container so you can run it without cloning or building.

• hugo-studio-plugins — a Hugo-powered marketplace of community plugins for the editor (custom tabs, field renderers, data-format handlers, shortcode pickers). Each plugin is just an entry in a Hugo content tree; the editor browses the marketplace's JSON feed.
• Individual plugins — small repos under this org that demonstrate the plugin API and serve as scaffolds for new ones.

The editor and the marketplace each have their own surface area, their own release cadence, and their own contributors. Splitting them across repos under one org keeps the boundaries clean while making it easy to find the whole stack from one place.

• Use it. Download Hugo Studio from the latest release and point it at one of your sites.
• Author a theme schema. Drop a .hugoeditor/theme-schema.json into your theme so editors get a real form for your params instead of inferred fields.
• File a bug or a feature request. Issue templates live in each repo; for cross-cutting ideas the Discussions on the editor repo are the catch-all for now.
• Build a plugin. When the API lands (v1.11), watch this space — we'll publish the plugin SDK and a starter template here.

Each project picks its own license; the editor is MIT. Hugo itself is a separate project under Apache-2.0.