-
Notifications
You must be signed in to change notification settings - Fork 14.2k
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
Improve PageFind search results #47137
Comments
/triage accepted |
/area web-development |
/area web-development /priority important-soon |
Ideally, the search should also understand the same aliases as kubectl (svc -> service,....). Google handles some of the aliases but not all of them By the way, starting with entity types (pod, ingress, service...) and making sure the first result is the page presenting may be a great start |
I think that's a great idea but could be its own feature request @TPXP |
We're not staffing this, so: People accessing our docs from behind state censorship may have other search options available, other than our built-in search. |
We now have PageFind search serving users who cannot access the Google Programmable Search, such as those behind the firewall in China. There have been reports that the search results are not well ranked so we'd like to improve them.
To properly assess the quality of the search results, we should find a way to measure their quality against some kind of baseline, such as what is provided by our Google Programmable Search engine. It may be best to, say, start with the 20 most common searches and then grade how suitable the results are. Grading the results over a broad range of search terms will ensure we're not optimizing things for just one or two particular use-cases.
This work should be done by someone who is familiar with the Kubernetes docs and knows what results would be best served for a particular query. Once we see where things are now, we can tune the PageFind results to see if we can improve their score to an acceptable level.
The text was updated successfully, but these errors were encountered: