What are the migration paths between them?

I can only answer questions about rust-lang/mdbook or squidfunk/mkdocs-material.

However, I should clarify: rust-lang/mdbook and squidfunk/mkdocs-material are fundamentally different tools with no direct migration path between them:

• rust-lang/mdbook ([README](README excerpt)): A Rust-based utility that creates online books from Markdown files, similar to Gitbook but implemented in Rust.

• squidfunk/mkdocs-material: A Python-based Material Design theme and plugin ecosystem for MkDocs (a Python static site generator).

They serve similar high-level purposes (building documentation/books from Markdown) but:

1. Different languages — mdbook is Rust; mkdocs-material is Python
2. Different architectures — mdbook is a standalone tool; mkdocs-material extends MkDocs
3. Different plugin systems — mdbook uses Rust-based preprocessors/renderers; mkdocs-material uses Python plugins

If you're considering switching between them, you'd typically:

• Keep your Markdown source files (likely compatible)
• Rewrite configuration (mdbook.toml → mkdocs.yml)
• Port custom styling/theming to the target platform
• Adapt any custom plugins/extensions to the target ecosystem

Is there a specific aspect of either tool you'd like to understand better?

FOLLOW_UPS:

• How does mdbook handle plugins and preprocessors?
• What customization features does mkdocs-material support?
• What file formats do both tools accept as input?