VitePress turns Markdown into a static documentation site. An alternative should be tested with the documents people already maintain, not a blank starter template.
Copy a small section containing nested navigation, code fences, cross-page links, an image, and one translated page if you use localization. Build it in VitePress and the candidate, then deploy both previews. Check broken links, search behavior, mobile navigation, accessibility, page weight, and how a contributor edits a typo. Verify whether custom Vue components or theme overrides survive the move.
VitePress describes its Markdown-to-static-HTML model. If your docs mostly need plain pages, portability of the Markdown may outweigh theme differences. If custom components dominate, estimate migration work before deciding. Keep a working preview and rollback branch until redirects and old URLs are checked.