Dhub is a Markdown editor
for documentation and static sites

Dhub is for people and teams who manage Markdown-based static websites like documentation sites, knowledge bases, and blogs. It provides a user-friendly editing experience and streamlined GitHub workflow, saving you from wrestling with Markdown syntax, manual image uploads, and complex table editing.

Dhub is built specifically for managing Markdown for static websites. It combines a WYSIWYG editing experience with a seamless GitHub workflow, something you won't find in generic Markdown editors.

You don't need any technical knowledge to edit content. No Markdown required. You'll need some basic GitHub familiarity for the initial setup, but after that, anyone on your team can jump in and start editing.

Dhub connects through a GitHub app that you authorize to access your repository. Once connected, Dhub can pull your content, save changes, and create pull requests directly to your repo.

Dhub is framework-agnostic. You can use it with Next.js, Docusaurus, or even just plain Markdown files. When importing your project, you choose how you want special components (like callouts) formatted: either Docusaurus-style or Prose UI format.

Yes! You can add frontmatter fields and embed custom MDX components or code blocks. Just use the slash menu to insert frontmatter or embedded code wherever you need it.

Dhub needs permission to read, write, and create pull requests in your chosen repository. During setup, you'll review and approve exactly which repositories Dhub can access.

The Free plan covers personal, non-commercial projects with individual GitHub accounts and public repos. The Pro plan adds support for GitHub organizations and private repositories.

Not at all! Dhub is a WYSIWYG editor, so you work with formatted text just like in Google Docs or Word. No Markdown syntax required.

Nope! Your team can edit content and push changes directly to your repository—no GitHub account required. If you choose to use pull requests, someone with GitHub access will need to merge them. But if your team pushes directly to your branch, you're completely independent from GitHub's interface.