Carried into the draft
- Markdown and MDX pages
- Directory paths and README landing pages
- Local images and downloadable assets
- Navigation from MkDocs, Docsify, GitBook-style SUMMARY files, or folders
- MkDocs include files carried as shared content
Markdown migration
Move from Markdown without hiding what changed.
Start from an ordinary Markdown folder or repository. Staleless keeps the portable content and reports framework behavior that cannot travel as Markdown.
A report before a commitment
See what moves. Review what cannot.
The import starts from a Markdown folder. It counts pages and assets, names changed paths, groups conversion notes by cause, and produces navigation for a person to review.
Named for a person
- Theme-specific components and shortcodes
- Build plugins that transform content at runtime
- Absolute links tied to the previous hostname
- Navigation inferred from a folder without an explicit config file
The migration
Four steps, with the old site still available.
- 01Export
Provide the docs folder or repository with its navigation files and local assets.
- 02Inspect
Run the import report first. Nothing overwrites an existing page silently.
- 03Review
Read the conversion notes, navigation proposal, changed paths, and missing assets.
- 04Launch
Preview, crawl, add redirects, then move the domain only when the result is verified.
Verification checklist
The upload finishing is not the migration finishing.
Keep the source export and the old site until readers, search engines, assets, and redirects all reach the intended answers.
- 01Run the dry report before writing anything.
- 02Compare page, image, and shared-content counts.
- 03Review changed paths and create redirects for public URLs.
- 04Crawl the preview and compare search results with the old site.
Bring a real export
See the migration report before you decide.
Other sources