The visual editor
for Docusaurus

Dhub lets you focus on content instead of wrestling with Markdown syntax. Tables, images, and formatting just work. Your whole team can contribute directly, including people without technical knowledge. You ship docs faster because there's less friction.

No. Once you connect a repo, anyone on your Dhub team can edit and push changes without a GitHub account, and their name still shows up in the commit history. If you choose to use pull requests, someone with GitHub access will need to merge them.

Drag and drop. Dhub saves images to your /static folder and generates the correct path. They get pushed to GitHub with your other changes.

Yes. Import your GitHub repo and start editing. No changes to your project structure required.

When Dhub encounters custom React components it doesn't recognize, it displays them as embedded MDX blocks. You can edit the JSX code directly within these blocks. This way, you can use any custom component while still benefiting from visual editing for standard content.

Yes. Dhub shows your entire project structure, including versioned documentation folders. You can edit any version of your docs, and changes are pushed to the appropriate location in your repository.

Dhub works with Docusaurus i18n out of the box. Your translated content folders show up in the file tree, and you can edit any language the same way.