Prosefly
All frameworks

Prosefly × Hugo

Write together. Keep your Hugo site.

Edit ordinary Hugo Markdown with your team, keep its frontmatter format, and publish back to the same content paths.

Connect your websiteRead the quickstart
Example repository contentHugo
  • hugo.toml
  • content/posts/first-post/index.md
  • static/images/cover.jpg

Selected content file

+++
title = "A new chapter"
date = 2026-10-08
draft = false
+++

# A new chapter

Every release starts with a first draft.
An illustrative file layout, not a live workspace.

Your files. A shared place to write.

Find your content directory

A scan recognizes supported Hugo configuration and its content directory, including nested sections and page-bundle Markdown files.

Keep your frontmatter format

Edit supported properties without converting existing YAML, TOML, or JSON frontmatter to a different format. Nested unsupported properties remain available in Source.

Preserve your site structure

Publication keeps the file path and page-bundle structure. Your Hugo theme and existing build continue to render the website.

From your repository to your workspace.

  1. 01

    Connect the Hugo repository

    Authorize GitHub and connect the repository containing your Hugo configuration and Markdown content.

  2. 02

    Confirm the content scope

    Review the discovered Content Collection. Use explicit Prosefly configuration when your project needs a more specific content directory.

  3. 03

    Write, review, and publish

    Edit ordinary Markdown visually. Open shortcodes in Source, then review and publish through Git.

What to know before you connect

Hugo support covers Markdown, not MDX. Documents with shortcodes or Go template expressions open in Source. Prosefly does not edit Hugo menus or run its build. Module mounts, language-specific directories, and environment overlays are not resolved automatically. The Hugo draft property is separate from a Prosefly draft.

Published content stays in your Git repository.

Drafts stay in Prosefly until you publish. Review your changes, then create a commit or pull request. Your existing website build handles deployment.

Understand content ownership

Keep going

Set up your workspace, understand publication, or explore the tools behind your website.

Explore another framework