-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
How to use the search function, there is no documentation yet #1078
Comments
You need to apply for Algolia Docsearch, if it gets approved you need to configure crawler etc. there and add your Algolia config in vitepress/docs/.vitepress/config.ts Lines 34 to 38 in bc47197
|
thank you!I'll give it a try. |
@brc-dd could you maybe help out how to set up crawler? i cant manage to run it to have index for algolia |
I'm sorry I don't have time to do this crawler yet, you can look at the user manual on the official website or some libraries that use crawler, such as Vite or Vue3 |
@sishen654 maybe Im wrong but I read and heard from my friend who did it, crawler is available for some pro acc, for open source you need to file for it via this form https://www.algolia.com/for-open-source/ then they set up crawler for your page, I did it, when I will have some update will write here :) |
@Szymon-dziewonski Yeah, when your docsearch account is approved, you'll get access to an admin console where you can configure the crawler. These are their recommended templates: https://docsearch.algolia.com/docs/templates/ . You can customize them accordingly if you're getting some weird results. (I'm not managing VitePress' crawler, so I can't tell for sure what is the exact config we are using.) |
Search is essential for vitepress. Not every projects get supported by agolia docsearch. It would be great for vitepress to have its own. |
Yes What about the private repos? I could use standard algolia, just Have no idea how to setup crawler/push data from VP? |
Describe the bug
none
Reproduction
none
Expected behavior
none
System Info
Additional context
No response
Validations
The text was updated successfully, but these errors were encountered: