barodoc create my-docs

Copy your Markdown/MDX files from docs/ into docs/en/ (or your locale folder).

cp -r old-project/docs/* my-docs/docs/en/

Docusaurus uses sidebar_position and sidebar_label. In Barodoc, navigation order is controlled by barodoc.config.json:

---
- sidebar_position: 1
- sidebar_label: "Getting Started"
+ title: Getting Started
---

You can remove Docusaurus-specific frontmatter fields. Barodoc only requires title (or a # Heading).

Replace Docusaurus sidebars.js with barodoc.config.json navigation:

{
  "navigation": [
    {
      "group": "Getting Started",
      "pages": ["introduction", "quickstart"]
    }
  ]
}

Replace Docusaurus components with Barodoc equivalents:

Export your GitBook space as Markdown files. GitBook provides this in Space Settings → Export.

barodoc create my-docs

GitBook uses SUMMARY.md for navigation. In Barodoc, move your content into docs/en/ and define navigation in barodoc.config.json:

{
  "navigation": [
    {
      "group": "Overview",
      "pages": ["introduction", "quickstart"]
    },
    {
      "group": "Guides",
      "pages": ["guides/setup", "guides/deployment"]
    }
  ]
}

Delete SUMMARY.md — it’s no longer needed.

GitBook often stores images in .gitbook/assets/. Move them to public/ and update references:

- ![Screenshot](.gitbook/assets/screenshot.png)
+ ![Screenshot](/images/screenshot.png)

Your MDX files can be used largely as-is. Copy them into docs/en/.

The structure is very similar:

// mint.json → barodoc.config.json
{
-  "name": "My Docs",
-  "navigation": [
-    { "group": "Guides", "pages": ["quickstart"] }
-  ],
-  "colors": { "primary": "#0070f3" }
+  "name": "My Docs",
+  "navigation": [
+    { "group": "Guides", "pages": ["quickstart"] }
+  ],
+  "theme": { "colors": { "primary": "#0070f3" } }
}

Key differences:

• Colors are nested under theme.colors instead of top-level colors
• anchors → use topbar for external links
• tabs → use navigation groups

Most Mintlify components have direct equivalents: