GitBook and Doxbrix are both Markdown-based docs platforms, which makes migration straightforward — your content is already in a format Doxbrix understands. This...
GitBook and Doxbrix are both Markdown-based docs platforms, which makes migration straightforward — your content is already in a format Doxbrix understands. This...
GitBook and Doxbrix are both Markdown-based docs platforms, which makes migration straightforward — your content is already in a format Doxbrix understands. This guide moves your GitBook space into Doxbrix, preserving your structure and, if you want, your Git-backed workflow.
Who this is for
Teams on GitBook who want Doxbrix's AI features (Ask AI, quality scans, the agent), richer blocks, and integrated review workflows — while keeping a familiar Markdown, docs-as-code experience.
Why it's easy
GitBook stores content as Markdown with a SUMMARY.md table of contents. Doxbrix uses MDX with a docs.json manifest. The concepts map almost directly:
| GitBook | Doxbrix |
|---|---|
| Space | [Space](/organize/spaces-and-navigation) / project |
| `SUMMARY.md` | [`docs.json`](/cli/overview/docs-as-code) navigation |
| Markdown pages | [MDX pages](/write/blocks-and-components) |
| Hints (`{% hint %}`) | [Callouts](/write/blocks-and-components#callout-blocks) |
| Tabs (`{% tabs %}`) | [`<Tabs>`](/write/blocks-and-components#tab-blocks) |
| Code blocks | Fenced code blocks |
| Page groups | [Groups](/organize/spaces-and-navigation) |
Step 1 — Get your GitBook content
If your GitBook is Git-synced, you already have the Markdown in a repo. Otherwise, export it:
If GitBook is connected to GitHub/GitLab, clone that repo — it holds your Markdown and SUMMARY.md.
Otherwise, export your space from GitBook's settings to get the Markdown files.
Step 2 — Import into Doxbrix
GitBook is a first-class conversion target — dxb init --from gitbook reads a GitBook tree directly:
# Convert a GitBook tree into a new Doxbrix project
dxb init . --from gitbook
# Or import the content into an existing project
dxb import repo ./gitbook-contentDoxbrix reads your folder structure (and SUMMARY.md where present) to recreate spaces, groups, and pages, converting each Markdown file to an MDX draft. See Import files.
Step 3 — Convert GitBook syntax
GitBook uses Liquid-style tags ({% ... %}) that Doxbrix converts to blocks. Verify these after import:
{% hint style="info" %} becomes <Info>; warning becomes <Warning>, etc.
{% tabs %} blocks become <Tabs>/<Tab>.
GitBook code tabs become <CodeGroup>.
Page references become internal links; embeds become <Embed>.
Step 4 — Keep your Git workflow (optional)
If you liked GitBook's Git sync, you'll feel at home — Doxbrix has the same model:
- Connect your repo for two-way Git Sync so pushes publish automatically.
- Author locally with the CLI.
Your migration can preserve the exact docs-as-code experience you had, with more capable tooling. See Publish from GitHub.
Step 5 — Adopt richer blocks
GitBook's block set is limited compared to Doxbrix. Take advantage of what's now available:
- Turn procedures into
<Steps>. - Add
<Mermaid>diagrams. - Build API reference pages with interactive endpoints.
- Use
<CardGroup>for navigation.
Step 6 — Enable AI and publish
Scan imported pages and fix the weakest.
Turn on the site assistant — something GitBook can't match.
Brand your site and go live.