You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Search for "migration" in the VitePress docs. See that there are no results.
Expected behavior
Searching for "migration" in the VitePress docs finds the VuePress guide and the VitePress 0.x guide.
System Info
n/a
Additional context
If these pages were meant to be retired, they could get a "not actively maintained" notice at the top. The fact that they don't turn up in search, and that I haven't found anything in the source saying "exclude these pages from search", makes me wonder if the VitePress docs' search is buggy, and whether that means my VitePress sites' search is buggy.
and that I haven't found anything in the source saying "exclude these pages from search",
Those files are intentionally removed from sitemap and have no direct link from any content or sidebar/navbar, that's why algolia's crawler can't find them.
Describe the bug
In Bing, DuckDuckGo, Ghostery Search, and Google, my top result for "migrate from vuepress to vitepress" is https://vitepress.dev/guide/migration-from-vuepress
I only used a search engine after searching the VuePress and VitePress docs and getting nothing.
Looking at the source, I see there's also https://vitepress.dev/guide/migration-from-vitepress-0
Reproduction
Search for "migration" in the VitePress docs. See that there are no results.
Expected behavior
Searching for "migration" in the VitePress docs finds the VuePress guide and the VitePress 0.x guide.
System Info
Additional context
If these pages were meant to be retired, they could get a "not actively maintained" notice at the top. The fact that they don't turn up in search, and that I haven't found anything in the source saying "exclude these pages from search", makes me wonder if the VitePress docs' search is buggy, and whether that means my VitePress sites' search is buggy.
Validations
The text was updated successfully, but these errors were encountered: