-
Notifications
You must be signed in to change notification settings - Fork 497
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 boost site-search/autocomplete #49
Comments
One solution to boost is to use Google Analytics and some scripting. A cron job could download all the relative popularity of pages, by URI, and then when we build the |
If you want to play along, here's a Here's the same file but with not just a string but with a popularity: https://www.peterbe.com/stumptown-renderer/issue-49/with-popularity/titles.json |
I have a working solution for this. It's early stages but it seems very promising. |
We don't have a search yet but I have a prototype for an autocomplete widget that can be used to navigate by typing in parts of the title. A flaw with this is that when the search input is small, there's no good way to decide which page to show first. For example "fo" should probably should probably present JavaScript/Reference/Global_Objects/Array/forEach ahead of Web/API/MediaKeyStatusMap/forEach because the latter is so much more popular.
The text was updated successfully, but these errors were encountered: