Renaming a file in a docs project is rarely just a file-system operation — every navigation entry, internal link, and snippet import that references the old path breaks the moment the file moves.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 rename handles all of that in one step: it moves the file to its new location and rewrites every reference across your project automatically, so nothing is left pointing at a path that no longer exists.
Usage
| Argument / Flag | Description |
|---|---|
<from> | Current path of the MDX file, relative to the project root (e.g., docs/old-name.mdx) |
<to> | New path for the file, relative to the project root (e.g., docs/new-name.mdx) |
--verbose | Print each file updated as references are rewritten |
Example
What Gets Updated
When you runjamdesk rename, the following are automatically rewritten to use the new path:
- docs.json navigation — any
pagesentry that referenced the old filename is updated to the new one - Internal links — Markdown and MDX links (e.g.,
[text](/docs/old-name)) throughout your content are rewritten - Snippet imports —
importstatements in MDX files that pull from the renamed file are updated to the new path
Run
jamdesk rename from your project root — the directory where docs.json lives. The command uses docs.json to locate your project structure and determine which files need updating.