mdBook -> Marque

This is the cleanest migration path Marque supports right now.

src/SUMMARY.md and navigation.mq want almost the same thing, so mdBook projects usually come across with less drama than most docs tools.

Run it

Auto-detect

marque migrate ./my-book

This creates ./my-book-marque.

Explicit target

marque migrate ./my-book ./my-book-marque --from mdbook

Pick the starter shell

marque migrate ./my-book ./my-book-marque --from mdbook --layout sidebar --theme rustique

What maps cleanly

Config

txt

book.toml          -> marque.toml
[book].title       -> title
[book].description -> description

Navigation

txt

src/SUMMARY.md     -> navigation.mq

Imported order and nesting come from the mdBook summary, not from the folder tree alone.

Pages and assets

txt

src/**/*.md        -> pages/**/*.mq
src/** assets      -> static/**

What Marque fixes during import

Local links

Internal markdown links are rewritten so .md targets become the matching Marque pages.

Review notes

The migrated site includes pages/migration-notes.mq with warnings and source-specific notes.

Default shell

The new site starts as a normal Marque project with copied layouts, themes, pages, and static assets.

What still needs manual work

Preprocessors

preprocessor.* sections in book.toml are not migrated automatically. If the old book relied on generated content, that logic still needs to be rebuilt.

Extra CSS and JS

output.html.additional-css and output.html.additional-js are called out in migration notes, but they are not mapped automatically into a Marque theme or layout runtime.

Theme fidelity

Expect content and structure to transfer cleanly. Expect the final look and feel to be a separate pass in themes and layouts.

Suggested clean-up pass

Run the migration and open the generated site with marque serve ..

Compare src/SUMMARY.md with the generated navigation.mq.

Open pages/migration-notes.mq and resolve every mdBook-specific note.

Rebuild the final styling in Marque themes and layouts instead of trying to force mdBook output settings to carry across.

If your book is mostly markdown chapters plus a normal summary file, this should feel pleasantly boring. That is the ideal outcome.