A Fumadocs editor for your whole team.

Fumadocs keeps your docs as MDX files in a repo, so every docs change means writing MDX and going through Git. Dhub puts a hosted visual editor on top of that repo. Writers edit callouts, cards, tabs, tables 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.

Fumadocs Editor is an open-source editor from the author of Fumadocs. Its Studio runs on your own machine and edits the files in your local clone, which suits a developer who already has the repo and commits with Git. Dhub is hosted: teammates open the docs in a browser with nothing to install, edit the same page together, create and move pages, rearrange the sidebar, and push or open pull requests without a GitHub account.

Yes. Import your GitHub repo and Dhub detects the Fumadocs project, including one that sits in a folder of a larger repo. You can start editing pages right away, with no changes to your project structure. One feature takes a one-time setup: to edit the sidebar visually, you add a short adapter that builds the Fumadocs page tree from 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.

Nothing, unless you want the visual sidebar editor. Dhub leaves your meta.json files as they are, and your sidebar keeps working from them. The visual sidebar editor keeps the whole structure in one navigation.json file instead, and a short adapter turns that file into the Fumadocs page tree. Once the adapter is in place, the sidebar follows navigation.json. See the adapter.

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

Callouts, cards and tabs are edited visually. Other components, whether they come from Fumadocs UI or from your own code, are displayed as embedded MDX blocks. You can edit the JSX code directly within these blocks, and the content around them is still edited visually. One thing to set up: Fumadocs does not register Tabs by default and Dhub writes no import lines, so add Tabs to your MDX components before writers use them. See the setup guide.