Docusaurus finally has an editor.

Docusaurus has no editor of its own, so every docs change means writing Markdown and going through Git. Dhub puts a visual editor on top of your existing repo. Writers edit tables, admonitions, tabs and images as blocks on the page, reviewers see each change highlighted instead of reading an MDX diff, and everything still lands in GitHub as ordinary commits and pull requests.

Yes. Import your GitHub repo and start editing pages right away, with no setup and no changes to your project structure. One feature takes a one-time setup: to edit the sidebar visually, you add a short sidebars.js adapter that reads the navigation.json file Dhub saves. Read the setup guide.

Yes, and some teams use Dhub for exactly that. When an agent pushes a branch or opens a pull request, open it in Dhub and every change is highlighted on the page, so a person can read the changed page instead of working through an MDX diff. Fix anything in place and push to the same pull request. Branches, pull requests and review are part of the Pro plan.

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.

We connected Dhub, CloudCannon, TinaCMS, Decap CMS and GitCMS to the same Docusaurus repo and ran them through the same checklist. The short version: Dhub needs no setup to start editing, edits admonitions and tabs in place, and is the only one with a visual navigation editor, which takes a one-time sidebars.js adapter. TinaCMS and Decap are open source, and CloudCannon also hosts your site. Read the full comparison.

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

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.