Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/jamdesk/jamdesk-cli/llms.txt

Use this file to discover all available pages before exploring further.

jamdesk migrate converts an existing Mintlify project to Jamdesk in a single command. Run it from inside your Mintlify docs directory and it will detect mint.json, convert your configuration and components, let you choose a theme, and copy everything into a new jamdesk-docs directory ready to develop against.

Usage

cd /path/to/mintlify-docs
jamdesk migrate

What gets converted

  • Configmint.json is converted to docs.json, including navbar, navigation structure, footer, SEO settings, and appearance options.
  • Components — Deprecated Mintlify components are updated to their Jamdesk equivalents (for example, <CardGroup> becomes <Columns>).
  • Inline components — Components that use useState or useEffect are extracted into /snippets as 'use client' .tsx files.
  • Video embedsiframe video embeds are normalized to the Jamdesk format.

Flags

FlagDescription
--yes, -ySkip all confirmation prompts
--theme <theme>Pre-select a theme: jam, nebula, or pulsar
--verbosePrint detailed output during the migration

Full migration workflow

1

Navigate to your Mintlify docs directory

Change into the root of your existing Mintlify project — the directory that contains mint.json.
cd /path/to/mintlify-docs
2

Run the migration command

Execute jamdesk migrate. The CLI detects mint.json, converts your configuration to docs.json, and converts components.
jamdesk migrate
3

Pick a theme

When prompted, choose one of the three available Jamdesk themes: jam, nebula, or pulsar. You can also pre-select a theme with the --theme flag to skip this prompt.
4

Start the dev server

Change into the newly created jamdesk-docs directory and start the local dev server to preview your migrated docs.
cd jamdesk-docs
jamdesk dev
Use jamdesk migrate --yes in CI or scripted environments to skip all confirmation prompts and run the migration non-interactively.
For the full list of what is converted and any manual steps required after migration, see the migration guide or visit jamdesk.com/docs/migration.

Build docs developers (and LLMs) love